Difference between revisions of "Substance FHIR Resource Proposal"
| Line 46: | Line 46: | ||
Any material is a substance. | Any material is a substance. | ||
| − | This resource will cover data elements, structures and relationships | + | This resource will cover data elements, structures and relationships required to uniquely define and identify substances and specified substances within medicinal products or used for medicinal purposes, dietary supplements, food and feed additives, cosmetics, etc. |
| + | |||
| + | Substances come in a wide variety of physical forms and can pass through different states (ie. Gas, liquid, solid) while still retaining their physical composition and material characteristics. | ||
| + | |||
| + | Examples: Pharmaceutical substances (including active vaccines containing retarded virus), disposable supplies, durable equipment, implantable devices, food items (including meat or plant products), waste, traded goods | ||
| + | |||
| + | Scope Challenge: When to use substance vs medicine | ||
==RIM scope== | ==RIM scope== | ||
| Line 52: | Line 58: | ||
<!-- 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. --> | ||
**Entity: Material (EntityClass="MAT") | **Entity: Material (EntityClass="MAT") | ||
| + | |||
==Resource appropriateness== | ==Resource appropriateness== | ||
| Line 72: | Line 79: | ||
<!-- 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) --> | ||
| − | + | Future | |
==Content sources== | ==Content sources== | ||
Revision as of 15:20, 9 May 2013
This page documents a Pending FHIR Resource Proposal
Contents
Substance
Owning committee name
Interested Work Groups
- Anatomic Pathology
- Clinical Genomics
- Imaging Integration
- Pharmacy
- Public Health and Emergency Response
FHIR Resource Development Project Insight ID
952
Scope of coverage
DEFINITION (SUBSTANCE): Any material is a substance.
This resource will cover data elements, structures and relationships required to uniquely define and identify substances and specified substances within medicinal products or used for medicinal purposes, dietary supplements, food and feed additives, cosmetics, etc.
Substances come in a wide variety of physical forms and can pass through different states (ie. Gas, liquid, solid) while still retaining their physical composition and material characteristics.
Examples: Pharmaceutical substances (including active vaccines containing retarded virus), disposable supplies, durable equipment, implantable devices, food items (including meat or plant products), waste, traded goods
Scope Challenge: When to use substance vs medicine
RIM scope
- Entity: Material (EntityClass="MAT")
Resource appropriateness
In healthcare, substances are used to treat patients, substances are analyzed for diagnostic, treatment, and research, subjects come in contact with certain substance thereby causing a need for healthcare, and so forth.
Expected implementations
Future
Content sources
- HL7 v3 Laboratory Standard - Normative
- HL7 v3 IDMP Standard
- HL7 v2.x
Resource Relationships
- Order
- OrderResponse ?
- DiagnosticReport
- ImagingStudy ?
- Prescription
- Supply
Timelines
- Vote by WG (Ready for ballot): July 2013
- Ballot: September 2013
gForge Users
- Lorraine Constable
- Patrick Loyd
