Applying the Lab-EMR Interoperability Profile Jan Flowers Technical Program Manager International Training and Education Center on Health University of Washington, Seattle, WA, USA firstname.lastname@example.org
Applying the Lab-EMR Interoperability Profile • National HIV EMR (iSante) since 2006 (65 sites, ~60k patients in EMR) • OpenELIS as national lab system in 2010 (15 sites) • Partners In Health OpenMRS
Lab Profile – Simplified Use Cases(in 3 implementation phases) • Order Transmission on Paper • Results Transmission • Order Transmission on Paper • Identification of Patient in EMR • Result Transmission • Order Transmission • Identification of Patient in EMR • Identification of transmitted order • Result Transmission Order (Paper) ElectronicMedical Record Lab Information System Demographic Query Demographic Response Test Result
Facility Level Patient Identification • PIX – Patient Identifier Cross-reference • PDQ – Patient Demographics Query • Patient search from LIS to EMR • Current Work • Results Interface from LIS to EMR • Lab Order Entry from EMR to LIS
What Else Can We Do With Patient Identification? • Back to demographics – Useful for other HIS systems within the current facility! • SCMS EDT pharmacy tool • Now we have one patient record used in multiple places: • EMR LIS Pharmacy
More Patient Identification • Biometrics and Fingerprinting • Now = verificationof patient, enrollmentof patient, and identity management • Facility level “Master Patient Index” (MPI/FPI) • All different processes • Noticed patterns in the process same as other domains • Vital Registration • National health insurance (verify, enroll, status changes)
We Have An Architecture! • These functions are useful across multiple systems and across different levels • We have the start of an eHealth architecture: • Well defined components • Well defined business rules • Standards based interoparability that implements the business rules with the components
What does this all mean? • We have the start of an eHealth architecture: • Well defined components • Well defined business rules • Standards based interoparability that implements the business rules with the components One approach to interoperability!
Now what? • Organized collection of information at facility-level to make an architecture? Next – talk about what to do with that data: reporting from the facility-level.