Lifecycle Modeling Tasks 2014
Capture Process Use Store Dispose Lifecycle of a /Information Set: AHIMA: The cycle of gathering, recording, processing, sharing, transmitting, retrieving, storing and deleting information ARMA: The major milestones of a record s existence, subject to changing requirements: creation, classification, use, retention, and disposition. Information Governance: Organization-wide framework for managing information throughout its lifecycle and for supporting the organization s strategy, operations, regulatory, legal, risk, and environmental requirements
Information Management Functions Occur Throughout Life of Information Functions Create Dispose Capture Process Use Store Dispose
Information Mgmt Functions - Healthcare Capture Process Use Store Dispose Create Enter Dictate Write Receive Interface Classify Validate Analyze QC/QA Complete Interface Integrate Code Examine Analytics/BI Release Discover Hold Retain Export Transmit Exchange Store Preserve Archive Delete Deprecate Destroy Perm Store Discover Perm Archive Transition
IHE Volume 1 (ITI TF-1) Integration Profiles Lifecycle for XDS (pg 108) --Cannot identify original standard in which this is derived--: Document Availability status Approved Deprecated Document Relationship Replacement Addendum Transformation Transformation-Replacement
IHE Volume 1 (ITI TF-1) Integration Profiles XDS Lifecycle con t Document Query XDS Document types XDS Stable Document (metadata) metadata about an already created document available for retrieval. XDS On-Demand Document (metadata) metadata describing the characteristics of a set of on-demand content and a unique identifier which can be used to create a document which collects the latest, most recent available information at the time of retrieval.
Share content that is already collected, no focus on what is actually collected
Capture, Use, Store and Dispose, some Process HL7 Electronic Health Technical Committee EHR Lifecycle Model Release 1, Draft Standard for Trial Use, 27 January 2008
The Data Management category provides Action-Verbs for the complete range of data handling actions by a system. The category has one parent, Manage (Data), and five (5) children with subsets: Capture, Maintain, Render, Determine, and Manage-Data-Visibility. ISO/HL7 EHRS-FM R2
More robust then AHIMA, though process still minimal EHRS-FM R2 (Used for Infrastructure Lifecycle Event Metadata on FHIR) 2014
Capture, Use, Store, and Dispose are represented Process appears to be missing ISO TS 21089: 2004 Trusted end-to-end information flows
Retention, Stewardship CAPTURE Origination Create Enter Dictate Write Receive Verification Amendment Disclosure, Transmittal Access/Use Archival Loss or Destruction APP1- Originator Translation Receipt Convergence APP2- Receiver De- Identification APP3- Receiver
Accountability, Transparency, Integrity, Protection, Compliance, Availability, Retention, Disposition Originate/Retain Amend Retention, Stewardship Transmit (May need to be 2? Original, amendment (s) and/or most recent) Place Legal Hold on Remove Legal Hold on Deprecate/Retract Restore Attest (Complete and Accurate) Verify Content Disclose View/Access Archive Destroy APP1- Originator Capture: Create,,, Dictate, Write, Receive, Interface Process: Classify, validate, analyze, QC/QA, Complete, Interface, Integrate APP2- Receiver Translate Receive/Retain Encrypt Decrypt Output/Report Extract Merge Unmerge Link Unlink Use: Code, Examine, Analytics/BI, Release, Discover, Hole, retain, Export, Transmit, Exchange Store: Store, Preserve, Archive Dispose: Delete, Deprecate, Destroy, Perm Store, Discover, Perm Archive, Transition APP3- Receiver De-Identify Pseudonymize Re-identify