Difference between revisions of "DiagnosticReport FHIR Resource Proposal"
| Line 14: | Line 14: | ||
=DiagnosticReport= | =DiagnosticReport= | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Owning committee name== | ==Owning committee name== | ||
Revision as of 17:52, 1 April 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.
The Diagnostic Report is not intended to support:
- Cumulative Result presentation
- Genetic Sequencing and related 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
??
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
- Specimen
- Substance
- Supply
Timelines
- Vote by WG (Ready for ballot): July 2013
- Ballot: September 2013
gForge Users
- Patrick Loyd
- Lorraine Constable
