Page tree
Skip to end of metadata
Go to start of metadata



Profile Details

Parent Resource

NOTE: These will be shared by the proposed profile USLabOrders as well

Constraints to be Applied

  • Various constraints upon Cardinality,type and Invarients and "must support" based upon implementation guides referenced below in Scope of Coverage and Example Scenarios.
  • 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
  • Introduction, conventions, scope, notes and various other sections under Implementation

Extensions to be Applied

  • US Profile (existing)
  • Unknown

Example Scenarios

Scope of coverage

  • US Realm
  • Ambulatory Care
  • Reporting of reportable laboratory results to public health.
  • 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) (see above link)
    • Based upon existing developing HL7 v2 Electronic Reporting of Laboratory Results To Public Health Guide (ELR)(see above link)
  • Based upon V3 Lab Normative Standard


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



  • December 1 2014

Balloting Requirements

Choose one:

  • Ballot with next FHIR DSTU or Normative Edition

Desired Ballot Date

  • January 2015