This wiki has undergone a migration to Confluence found Here
Difference between revisions of "USLab Result FHIR Profile Proposal"
Jump to navigation
Jump to search
Hbuitendijk (talk | contribs) m (Hbuitendijk moved page USLab Report FHIR Profile Proposal to USLab Result FHIR Profile Proposal) |
|||
| Line 35: | Line 35: | ||
<!--Put a link to the resource/datatype (or group of resources) that will be profiled here.--> | <!--Put a link to the resource/datatype (or group of resources) that will be profiled here.--> | ||
* [[http://hl7.org/implement/standards/fhir/diagnosticreport.html| DiagnosticReport ]] | * [[http://hl7.org/implement/standards/fhir/diagnosticreport.html| DiagnosticReport ]] | ||
| + | * As well as resource referenced by this resource: | ||
| + | ** [[http://hl7.org/implement/standards/fhir/observation.html| Observation ]] | ||
| + | ** [[http://hl7.org/implement/standards/fhir/patient.html| Patient ]] | ||
| + | ** [[http://hl7.org/implement/standards/fhir/specimen.html| Specimen ]] | ||
| + | ** [[http://hl7.org/implement/standards/fhir/organization.html| Organization ]] | ||
| + | ** [[http://hl7.org/implement/standards/fhir/diagnosticorder.html| DiagnosticOrder ]] | ||
| + | ** [[http://hl7.org/implement/standards/fhir/media.html| Media ]] | ||
| + | |||
| + | NOTES These will be shared by the proposed profile USLabOrders as well | ||
| + | |||
====Constraints to be Applied==== | ====Constraints to be Applied==== | ||
<!--Describe how the current resource will be constrained.--> | <!--Describe how the current resource will be constrained.--> | ||
| − | + | ||
| − | * | + | * 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 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 SNOMED CT for Coded Results, Specimen type, source, collection procedure. | ||
* Binding to UCUM for units of measure | * Binding to UCUM for units of measure | ||
| − | * | + | * Introduction, conventions, scope, notes and various other sections under Implementation |
| − | |||
| Line 74: | Line 80: | ||
As a rule, Profiles should encompass all of these aspects. | As a rule, Profiles should encompass all of these aspects. | ||
--> | --> | ||
| + | |||
| + | * 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) | ||
| + | ** Based upon existing developing HL7 v2 Electronic Reporting of Laboratory Results To Public Healt Guide (ELR) | ||
| + | * Based upon V3 Lab Normative Standard | ||
| + | |||
==Ownership== | ==Ownership== | ||
Revision as of 19:30, 2 October 2014
This page documents a Pending FHIR Resource Proposal
PutProposedProfileNameHere
USLabResults
Profile Details
Parent Resource
- [DiagnosticReport ]
- As well as resource referenced by this resource:
- [Observation ]
- [Patient ]
- [Specimen ]
- [Organization ]
- [DiagnosticOrder ]
- [Media ]
NOTES 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
- 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.
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)
- Based upon existing developing HL7 v2 Electronic Reporting of Laboratory Results To Public Healt Guide (ELR)
- Based upon V3 Lab Normative Standard
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
