This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "USLab Result FHIR Profile Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Profile Proposal}}")
 
Line 27: Line 27:
 
* Be consistent with other similar Profiles
 
* Be consistent with other similar Profiles
 
* Incorporate the name of the Resource being profiled
 
* Incorporate the name of the Resource being profiled
−
-->
+
-->USLabResults
  
 
==Profile Details==
 
==Profile Details==
Line 34: Line 34:
  
 
<!--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.-->
−
* [[ParentResourceAddress|ResourceName]]
+
* [[http://hl7.org/implement/standards/fhir/diagnosticreport.html| DiagnosticReport ]]
  
 
====Constraints to be Applied====
 
====Constraints to be Applied====
  
 
<!--Describe how the current resource will be constrained.-->
 
<!--Describe how the current resource will be constrained.-->
−
* Constraint 1
+
* US Realm
−
* Constraint 2
+
* 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====
 
====Extensions to be Applied====
  
 
<!--Describe how the current resource will be extended.-->
 
<!--Describe how the current resource will be extended.-->
−
* Extension 1
+
* US Profile (existing)
−
* Extension 2
+
* Unknown
  
 
===Example Scenarios===
 
===Example Scenarios===
  
−
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this Profile.  They should demonstrate the full scope of the Profile and allow exercising of the Profiles capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
+
* Refer to LRI IG [[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=279| HL7 Version 2.5.1 Implementation Guide: Orders and Observations; Interoperable Laboratory Result Reporting to EHR, Release ]] and ELR IG [[http://www.hl7.org/implement/standards/product_brief.cfm?product_id=329| 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 [[http://hl7v2-lab-testing.nist.gov/mu-lab/Lab| 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===
 
===Scope of coverage===
Line 69: Line 79:
  
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. -->
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. -->
−
[[YourCommitteeName]]
+
* Orders and Observations (OO)
  
 
===Contributing or Reviewing Work Groups===
 
===Contributing or Reviewing Work Groups===
  
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the Profile (optional) -->
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the Profile (optional) -->
−
* Work Group Name
+
* Public Health and Emergency Response (PHER)
−
* or link
 
−
* or "None"
 
  
 
===Expected implementations===
 
===Expected implementations===
  
 
<!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
<!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent implementations. -->
−
 
+
*TBD
 
===gForge Users===
 
===gForge Users===
  
 
<!-- Identify the userids who will require commit access to gForge to maintain the Profile.  (Ensure all users have registered for gForge.) -->
 
<!-- Identify the userids who will require commit access to gForge to maintain the Profile.  (Ensure all users have registered for gForge.) -->
 +
*Eric Haas
 +
*Rob Hausam
 +
*Hans Buitendijk
  
 +
===FHIR Profile Development Project Insight ID===
  
−
===FHIR Profile Development Project Insight ID===
 
  
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 +
* Number 1113  OO FHIR Lab Result Profile
  
 
==Plans==
 
==Plans==
Line 95: Line 107:
  
 
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting -->
−
*TargetDateForInternalReview
+
* December 1 2014
  
 
===Balloting Requirements===
 
===Balloting Requirements===
Line 103: Line 115:
 
Choose one:
 
Choose one:
 
*Ballot with next FHIR DSTU or Normative Edition
 
*Ballot with next FHIR DSTU or Normative Edition
−
*or Ballot independently as DSTU
+
 
−
*or Realm specific ballot
 
−
*or No Ballot
 
  
 
<!-- Indicate the desired ballot date.-->
 
<!-- Indicate the desired ballot date.-->
 
Desired Ballot Date
 
Desired Ballot Date
−
*PutDesiredBallotDateHere
+
*January 2014

Revision as of 22:43, 25 September 2014

OpenHotTopic.GIF

This page documents a Pending FHIR Resource Proposal



PutProposedProfileNameHere

USLabResults

Profile Details

Parent Resource

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

Scope of coverage

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
Retrieved from "https://wiki.hl7.org/w/index.php?title=USLab_Result_FHIR_Profile_Proposal&oldid=91184"