This wiki has undergone a migration to Confluence found Here
Difference between revisions of "USLab Order FHIR Profile Proposal"
Jump to navigation
Jump to search
(→Plans) |
|||
| Line 28: | Line 28: | ||
* Incorporate the name of the Resource being profiled | * Incorporate the name of the Resource being profiled | ||
--> | --> | ||
| − | + | USLabOrder | |
==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.--> | ||
| − | * [[ | + | * [[http://hl7.org/implement/standards/fhir/diagnosticorder.html|DiagnosticOrder]] |
====Constraints to be Applied==== | ====Constraints to be Applied==== | ||
<!--Describe how the current resource will be constrained.--> | <!--Describe how the current resource will be constrained.--> | ||
| − | * | + | * US Realm |
| − | * | + | * Based upon existing developing S&I and HL7 v2 Laboratory Orders Interface Guide |
| + | * Based upon existing Laboratory stuff ( get reference from PSS ) | ||
| + | * Binding to LOINC codes for orders | ||
| + | * Binding to LOINC codes for "Ask at Order" entry questions | ||
| + | * Binding to SNOMED CT for Specimen type, source, 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.--> | ||
| − | * | + | * US Profile |
| − | * | + | * 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.) --> | <!-- 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 NIST LOI tool (URL) for a list of test cases. | ||
===Scope of coverage=== | ===Scope of coverage=== | ||
| Line 57: | Line 66: | ||
Scope should consider numerous aspects of breadth of scope, including: | Scope should consider numerous aspects of breadth of scope, including: | ||
| − | * Subject: Human | + | * Subject: Human clinical specimens ( Animal carcasses for rabies testing ) |
| − | * Disciplines: | + | * Disciplines: Clinical, Public Health |
| − | * Delivery environment | + | * Delivery environment: ? restricted to ambulatory care ? |
| − | |||
As a rule, Profiles should encompass all of these aspects. | As a rule, Profiles should encompass all of these aspects. | ||
Revision as of 09:08, 24 September 2014
This page documents a Pending FHIR Resource Proposal
PutProposedProfileNameHere
USLabOrder
Profile Details
Parent Resource
- [[1]]
Constraints to be Applied
- US Realm
- Based upon existing developing S&I and HL7 v2 Laboratory Orders Interface Guide
- Based upon existing Laboratory stuff ( get reference from PSS )
- Binding to LOINC codes for orders
- Binding to LOINC codes for "Ask at Order" entry questions
- Binding to SNOMED CT for Specimen type, source, 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
- Unknown
Example Scenarios
- Refer to NIST LOI tool (URL) for a list of test cases.
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
- TODO
Plans
Timelines
December 1 2014
Balloting Requirements
Choose one:
- Ballot with next FHIR DSTU or Normative Edition
Desired Ballot Date
Jan 2014
