Difference between revisions of "DiagnosticReport FHIR Resource Proposal"
| Line 76: | Line 76: | ||
==Expected implementations== | ==Expected implementations== | ||
| − | Can be expected to be implemented by diagnostic laboratories and consumed by EHR/PHR/EMR systems. Note the relationship to the Observation resource to record the observation result/s, and to the | + | Can be expected to be implemented by diagnostic laboratories and consumed by EHR/PHR/EMR systems. Note the relationship to the Observation resource to record the observation result/s, and to the DiagnosticOrder resource to manage the workflow aspects. |
<!-- For resources not deemed "key", what interest is there by implementers in using this particular resource. (Should ideally have multiple independent implementations) --> | <!-- For resources not deemed "key", what interest is there by implementers in using this particular resource. (Should ideally have multiple independent implementations) --> | ||
Revision as of 20:08, 23 June 2013
This page documents a Pending FHIR Resource Proposal
Contents
DiagnosticReport
Owning committee name
Interested Work Groups
- Anatomic Pathology
- Clinical Genomics
- Imaging Integration
- Public Health and Emergency Response
FHIR Resource Development Project Insight ID
952
Scope of coverage
The findings and interpretation of diagnostic tests performed on patients and/or specimens. The report includes clinical context such as requesting and provider information, and some mix of atomic results, images, textual and coded interpretation, and formatted representation of diagnostic reports.
RIM scope
ActClass = OBS and children MoodCode = EVN
<note - need to refine to differentiate from observations>
Resource appropriateness
Diagnostic reporting is central to the business of healthcare. The basic process of healthcare is the diagnosis and treatment of patients. The diagnostic report is the primary means of communicating diagnostic results to providers, in domains such as laboratory, radiology, pathology, etc.
Expected implementations
Can be expected to be implemented by diagnostic laboratories and consumed by EHR/PHR/EMR systems. Note the relationship to the Observation resource to record the observation result/s, and to the DiagnosticOrder resource to manage the workflow aspects.
??
Content sources
- HL7 v3 Laboratory Standard - Normative
- HL7 v2.x
- HL7 Radiology Report standards (for instance the DR Structured Report in C-CDA)
Resource Relationships
- Order
- OrderResponse
- DiagnosticOrder
- Specimen
- Substance
- Supply
- ImagingStudy
Timelines
- Vote by WG (Ready for ballot): July 2013
- Ballot: September 2013
gForge Users
- Patrick Loyd
- Lorraine Constable
