This wiki has undergone a migration to Confluence found Here
Difference between revisions of "ObservationDefinition FHIR Resource Proposal"
Jump to navigation
Jump to search
| (4 intermediate revisions by one other user not shown) | |||
| Line 3: | Line 3: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents a [[:category: | + | This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 13: | Line 13: | ||
| − | = | + | =DataElement= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 37: | Line 37: | ||
* [[Patient Care]] | * [[Patient Care]] | ||
* [[Structured Documents]] | * [[Structured Documents]] | ||
| + | * [[Vocabulary]] | ||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| Line 44: | Line 45: | ||
==Scope of coverage== | ==Scope of coverage== | ||
| − | + | DataElement will define a single piece of information that can potentially be captured, shared, analyzed or displayed. It can 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. | |
<!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | <!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | ||
| Line 63: | Line 64: | ||
==Resource appropriateness== | ==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 | + | 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 Data Elements are. They are typically stored and accessed in registries as independent entities. |
<!-- Does the resource meet the following characteristics? | <!-- Does the resource meet the following characteristics? | ||
| Line 84: | Line 85: | ||
==Content sources== | ==Content sources== | ||
| − | * ISO | + | * ISO 11179.3 |
* HL7 v2 | * HL7 v2 | ||
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult | <!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult | ||
| Line 98: | Line 99: | ||
==Resource Relationships== | ==Resource Relationships== | ||
| − | * Observations may reference | + | * Observations may reference a DataElement (likely by an extension) to indicate what definition they're aligning with |
| − | * Questionnaire questions may reference | + | * Questionnaire questions may reference a DataElement (by extension) to indicate what data element they're capturing |
| − | * Profile structure elements and extension definitions may reference an | + | * Profile structure elements and extension definitions may reference an DataElement to indicate what standard data element they correspond to |
<!-- What are the resources do you expect will reference this resource and in what context? | <!-- What are the resources do you expect will reference this resource and in what context? | ||
| Line 112: | Line 113: | ||
==Timelines== | ==Timelines== | ||
| − | For inclusion in DSTU ballot | + | For inclusion in 2nd FHIR DSTU ballot |
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
Latest revision as of 20:32, 8 April 2015
This page documents a Approved FHIR Resource Proposal
Contents
- 1 DataElement
- 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
DataElement
Owning committee name
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
???
Scope of coverage
DataElement will define a single piece of information that can potentially be captured, shared, analyzed or displayed. It can 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 Data Elements 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 11179.3
- 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 a DataElement (likely by an extension) to indicate what definition they're aligning with
- Questionnaire questions may reference a DataElement (by extension) to indicate what data element they're capturing
- Profile structure elements and extension definitions may reference an DataElement to indicate what standard data element they correspond to
Timelines
For inclusion in 2nd FHIR DSTU ballot
gForge Users
N/A (necessary ids already have access)
