SubstanceSpecification FHIR Resource Proposal
- 1 SubstanceSpecification
- 1.1 Owning work group name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Timelines
- 1.13 gForge Users
- 1.14 When Resource Proposal Is Complete
- 1.15 FMG Notes
Owning work group name
Committee Approval Date:
13th September 2017
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
Scope of coverage
To support the content of the revised ISO 11238 IDMP Substance standard and its ISO/TS 19844 Technical Specification, and other domain areas with similar requirements (detailed definition of substances, to molecular level, including manufacturing processes and ingredients).
Similar in scope to the substance parts of CPM. Entity: Material (EntityClass="MAT")
There is an upcoming requirement to support the standardised exchange of detailed definitional Substance data, as covered by the ISO 11238 specification.
This resource does not intend to clash with the existing Substance FHIR resource, but complements with an extra level of detail. It is seen as a sibling rather than a parent or a superclass to be profiled.
It is intended to add an extra level of substance specification detail, such as is typically used by regulators, and only indirectly used during normal medication related work flows (e.g. for lookups of unfamiliar substances).
Manufacturers submit this data to regulators, when substances are created or the parameters change (ingredient manufacturer, process etc).
Regulators exchange this information between each other, to synchronize substance catalogs.
FDA (already implemented a proprietary message solution for 11238 substances). EMA
Basis for the resource is the information in ISO 11238 Substances standard. Actual data exists in the FDA GSRS implementation of 11238.
Substance definitions for the various categories (Chemical, Polymer, Protein etc). Use of "Specified Substance" area of 11238 to add extra information around manufacturing process etc.
Reference to Organization, for the manufacturer.
SubstanceSpecification and Substance
There is expected to be a reference from Substance to SubstanceSpecification, to be able to point to a more detailed definition. This may be an actual FHIR reference, or, perhaps more likely, it could operate via Substance.Code, which would correspond to SubstanceSpecification.codes.
This resource is not expected to replace the existing Substance resource - which is limited in scope to the small number of items needed to support direct clinical/medicinal use. (The Substance resource could be considered to be a "Substance Use".)
SubstanceSpecification is a collection of definitional information that an instance of a Substance resource (e.g. in a Medication, within a MedicationDispense) can refer to.
It is not expected that a SubstanceSpecification would ever directly substitute for the use of Substance.
In theory, all the SubstanceSpecification information could be contained in a hugely expanded Substance resource (and then the existing Substance scope could be profiled back out again). But this would create an unmanageably large Substance resource for the very common and narrow medical/clinical use cases.
Since the use of SubstanceSpecification is almost orthogonal to the clinical use cases, it seems appropriate to have the SubstanceSpecification resource available as a sibling to Substance, not a parent. The SubstanceSpecification resource would also be used on its own, unrelated to any Substance instance, in the distinct regulatory and drug information use cases.
Overlap between SubstanceSpecification and Substance
In practical terms there very little overlap of attributes between SubstanceSpecification and Substance. The Substance resource has only a few fields that are definitional (which are the only ones that would overlap).
Identifier and status are specific to this substance instance.
Category is definitioanl, and so does overlap, but could also be a local classification.
Code is the link between the two, and description could be considered a very small summary of the whole SubstanceSpecification, and so be a useful overlap.
The Instance component is not definitional so does not clash.
The Ingredient class is primarily for cases when the main Substance is made up on-demand - mixed rather than manufactured - and so would not itself be covered by a global SubstanceSpecification.
SubstanceSpecification and Device
There is no direct relationship between SubstanceSpecification and Device anticipated. In theory, since devices are made of substances, it would be possible, as with any physical object, to use a SubstanceSpecification to describe the materials is composed of. However this is not a currently proposed use case and device material is not supported by the existing Device resource. The separate IDMP Product use case (not proposed here, but a possible future concept) does also include details of manufactured devices, and their materials. A expanded Device resource to cover the requirements of IDMP Products, could inculde a Device.Material field, which could be a reference to a Substance, or to a SubstanceSpecification. (For that future use case, Device could be expanded with a large set of extensions, or possibly an analogous DeciveSpecification resource).
Early draft by December 2017 comment-only ballot.
riksmithies (already has commit permission)
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org