Difference between revisions of "ObservationDefinition FHIR Resource Proposal"
| Line 93: | Line 93: | ||
* Define administrative gender as CDE | * Define administrative gender as CDE | ||
* Define a LOINC lab test as a master file definition | * Define a LOINC lab test as a master file definition | ||
| + | * An application wanting to display a list of observation types to create for a patient. | ||
| + | |||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources 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 resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
Revision as of 20:22, 6 May 2014
This page documents a Pending FHIR Resource Proposal
Contents
- 1 ObservationDefinition
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
ObservationDefinition
Owning committee name
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
???
Scope of coverage
ObservationDefinition will represent a type of data element that can potentially be captured, shared, analyzed or displayed. It will cover all potential data elements that could be used in FHIR or any other healthcare exchange standard (CDA, v2, OpenEHR, CDISC standards, etc.). It will be used in the definition of data models and exchange/analysis standards to describe the data elements intended to be used. It will apply across all potential geographies, disciplines and healthcare settings.
RIM scope
Observation with mood code of DEF, though it involves representing *all* data elements as observation values - i.e. "everything's an OBX", including things like "primary practitioner's phone number" . . .
Resource appropriateness
Observation Master Files have been a core component of HL7 v2 almost since its inception. Common Data Elements have been a core part of healthcare, particularly on the clinical research side (NLM, NCI, etc.) for many years. The ISO 11179 specification defines exactly what CDEs are. They are typically stored and accessed in registries as independent entities.
Expected implementations
- ONC Structured Data Capture project. Possibly also by FDA, conversion from CDISC Share, etc.
- Implementations of any v2 system looking to expose Observation master file content as a subscribable FHIR registry
Content sources
- ISO 11169
- HL7 v2
Example Scenarios
- Define administrative gender as CDE
- Define a LOINC lab test as a master file definition
- An application wanting to display a list of observation types to create for a patient.
Resource Relationships
- Observations may reference an ObservationDefinition (likely by an extension) to indicate what definition they're aligning with
- Questionnaire questions may reference an ObservationDefinition (by extension) to indicate what data element they're capturing
- Profile structure elements and extension definitions may reference an ObservationDefinition to indicate what standard data element they correspond to
Timelines
For inclusion in DSTU ballot
gForge Users
N/A (necessary ids already have access)
