This wiki has undergone a migration to Confluence found Here
Difference between revisions of "ObservationDefinition FHIR Resource Proposal"
Jump to navigation
Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| Line 13: | Line 13: | ||
| − | = | + | =ObservationDefinition= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 30: | Line 30: | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | ||
| − | [[ | + | [[Orders_%26_Observations_WG]] |
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | ||
| − | * | + | * [[Patient Care]] |
| − | * | + | * [[Structured Documents]] |
| − | |||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| + | ??? | ||
<!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | <!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | ||
==Scope of coverage== | ==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. | ||
<!-- 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 57: | Line 58: | ||
==RIM scope== | ==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" . . . | |
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
==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 CDEs 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 77: | Line 79: | ||
==Expected implementations== | ==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 | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
==Content sources== | ==Content sources== | ||
| − | + | * ISO 11169 | |
| + | * 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 86: | Line 91: | ||
==Example Scenarios== | ==Example Scenarios== | ||
| − | + | * Define administrative gender as CDE | |
| + | * Define a LOINC lab test as a master file definition | ||
<!-- 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.) --> | ||
==Resource Relationships== | ==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 | ||
<!-- 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 101: | Line 110: | ||
==Timelines== | ==Timelines== | ||
| − | + | For inclusion in 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 --> | ||
==gForge Users== | ==gForge Users== | ||
| − | + | N/A (necessary ids already have access) | |
<!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
Revision as of 03:28, 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
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)
