USLab Result FHIR Profile Proposal

PutProposedProfileNameHere

USLabResults

Profile Details

Parent Resource

• [DiagnosticReport ]

Constraints to be Applied

• US Realm
• Based upon existing regulatory requirements for Laboratories and Electronic Health Record Systems (EHR-S) for reporting clinical laboratory results
  • Based upon existing developing S&I and HL7 v2 Laboratory Results Interface Guide (LRI)
  • Based upon existing developing HL7 v2 Electronic Reporting of Laboratory Results To Public Healt Guide (ELR)
• Based upon V3 Lab Normative Standard
• Binding to LOINC codes for orders and observations including "Ask at Order" entry questions
• Binding to SNOMED CT for Coded Results, Specimen type, source, collection procedure.
• Binding to UCUM for units of measure
• Various constraints upon Cardinality,type and "must support" based upon above mentioned guides
• Invarients applied as needed to constrain conditional usage.

Extensions to be Applied

• US Profile (existing)
• Unknown

Example Scenarios

• Refer to LRI IG [HL7 Version 2.5.1 Implementation Guide: Orders and Observations; Interoperable Laboratory Result Reporting to EHR, Release ] and ELR IG [HL7 Version 2.5.1 Implementation Guide: Electronic Laboratory Reporting to Public Health, Release 2 (US Realm)] for roles, sequence diagrams and use cases.
• Refer to NIST tool [Results Interface (LRI) LIS/EHR HL7 V2 Validation Tool - Meaningful Use 2014 Edition Certification Testing] for a list of example test cases.

Ownership

Owning committee name

• Orders and Observations (OO)

Contributing or Reviewing Work Groups

• Public Health and Emergency Response (PHER)

Expected implementations

• TBD

gForge Users

• Eric Haas
• Rob Hausam
• Hans Buitendijk

FHIR Profile Development Project Insight ID

• Number 1113 OO FHIR Lab Result Profile

Plans

Timelines

• December 1 2014

Balloting Requirements

Choose one:

• Ballot with next FHIR DSTU or Normative Edition

Desired Ballot Date

• January 2014