including multiple electronic and released to the requestor as allowed manual systems. HIPAA 6. Ability to assemble information A2.Single or multiple groups of A2.1 and A2.2 from disparate electronic systems, documents within the electronic both internal and external to the medical record can be viewed by or actual or virtual location(s) of the released to the requestor as allowed organization. by HIPAA 7. Ability to access information or multiple groups of and A2.Single A2.1 A2.2 created with legacy hardware and documents within the electronic software systems. In case of medical record can be viewed by or impending system obsolescence, released to the requestor as allowed information with organizational by value should be migrated to currently supported hardware and/or converted into a format. 8. Ability to maintain metadata To be developed (TBD) TBD services across all participating systems assigning structural and descriptive characteristics to information including data provenance information, e.g., authors and dates of creation, modification, sending, receipt, access, etc. 9. Ability to manage both vendor TBD TBD relationships and employee turnover to maintain the workforce capabilities on the most current methods to access information. 10. To ensure levels of TBD TBD redundancy, failover, contingencies and risk management practices to minimize risks of non-availability of information due to a disaster, system malfunction, or data corruption. 11. A3. A log of all requests and accounting of disclosures is kept as an audit trail and can be referenced as needed. 12. A4. Full chart management functionality (i.e. Record Lifecycle Management) to verify the identification of location of the source of the release, completeness of the documents being released, and destination for the release or review
including multiple electronic and manual systems. released to the requestor as allowed HIPAA 6. Ability to assemble information from disparate electronic systems, both internal and external to the actual or virtual location(s) of the organization. A2.Single or multiple groups of documents within the electronic medical record can be viewed by or released to the requestor as allowed by HIPAA A2.1 and A2.2 7. Ability to access information created with legacy hardware and software systems. In case of impending system obsolescence, information with organizational value should be migrated to currently supported hardware and/or converted into a format. A2.Single or multiple groups of documents within the electronic medical record can be viewed by or released to the requestor as allowed by A2.1 and A2.2 8. Ability to maintain metadata services across all participating systems assigning structural and descriptive characteristics to information including data provenance information, e.g., authors and dates of creation, modification, sending, receipt, access, etc. To be developed (TBD) TBD 9. Ability to manage both vendor relationships and employee turnover to maintain the workforce capabilities on the most current methods to access information. TBD TBD 10. To ensure levels of redundancy, failover, contingencies and risk management practices to minimize risks of non-availability of information due to a disaster, system malfunction, or data corruption. TBD TBD 11. A3. A log of all requests and accounting of disclosures is kept as an audit trail and can be referenced as needed. 12. A4. Full chart management functionality (i.e. Record Lifecycle Management) to verify the identification of location of the source of the release, completeness of the documents being released, and destination for the release or review
IHE_ITIWhitePaper-HITStdsforHIMPratices_051115.docx