This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR for Orders"
Jump to navigation
Jump to search
Line 58: | Line 58: | ||
# description - | # description - | ||
# container Condition | # container Condition | ||
+ | # specimenProcessingStep | ||
** do we need to deal with Recursive containers and / or Storage equipment | ** do we need to deal with Recursive containers and / or Storage equipment | ||
** datatype on position? | ** datatype on position? |
Revision as of 16:04, 8 May 2013
Contents
Introduction
This is the project page for the development of FHIR resources in the OO domain. Project #952
Scope
Resources under development by OO:
- Device
- Substance
- Supply
- Observation
- DiagnosticReport
- Specimen
- DiagnosticOrder (not yet approved, need resource proposal)
Resources under development by Core Team:
- Order
- OrderResponse
Resources
Resource | Resource Proposal | Status | Next Ballot | Who |
---|---|---|---|---|
Device | Device Resource Proposal | Development | SEP13 | TBD |
Substance | Substance Resource Proposal | Development | SEP13 | TBD |
Supply | Supply Resource Proposal | Development | SEP13 | Patrick |
Specimen | Specimen Resource Proposal | Development | SEP13 | Lorraine |
Observation | Observation Resource Proposal | Development | SEP13 | Patrick |
DiagnosticReport | Diagnostic Report Resource Proposal | Updates from Ballot Reconciliation | SEP13 | Patrick |
Next Steps
- Device - Resource is created, need to review requirements and current v3 device models
- Substance - Resource is created, need to review requirements and current v3 substance models
- Supply - Resource has not yet been created, need to review requirements and current v3 substance models
- Observation - Resource is create, need to discuss Observation vs. DiagnosticReport and what makes them different resources
- DiagnosticReport - Resource has been balloted, Most changes applied from ballot reconciliation, 2 still open to apply
- Table 0078 concepts
- Resource boundaries between observation and diagnosticreport
- Specimen - Resource is created (just a shell with only an identifier), need to review requirements and current v3 models and ongoing specimen DAM project
- Review Order resource
- Review OrderResponse resource
Resource Development Notes
Specimen
- Review of Specimen DAM for content
- Specimen Attributes not added to Specimen Resource
- used a resource reference to Parent specimen rather than track the Parent Identifier
- formCode - consider this as pre-coordinated in specimen type
- isDerived as this can be determined by the existence of a parent specimen
- description -
- container Condition
- specimenProcessingStep
- do we need to deal with Recursive containers and / or Storage equipment
- datatype on position?
- container may fail the 80/20
Documents
- Review Notes (Jan 2013) on Lab FHIR Models: LabReportDiscussion