This wiki has undergone a migration to Confluence found Here

Difference between revisions of "SubstanceSpecification FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Blanked the page)
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
<div class="messagebox cleanup metadata">
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
<!-- For additional guidance on considerations for resource creation, refer to [[FHIR Resource Considerations]] -->
<!-- Resource names should meet the following characteristics:
* Lower camel case
* U.S. English
* Domain-friendly
* Short
* Clear
* Unique
* Avoid non-universal abbreviations (e.g. URL would be ok)
* Be expressed as a noun
* Be consistent with other similar resources
==Owning work group name==
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
==Committee Approval Date:==
<i>13th September 2017</i>
==Contributing or Reviewing Work Groups==
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
* Pharmacy
* O&O
==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: -->
==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).
==RIM scope==
Similar in scope to the substance parts of CPM. Entity: Material (EntityClass="MAT")
==Resource appropriateness==
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.
==Expected implementations==
FDA (already implemented a proprietary message solution for 11238 substances).
==Content sources==
Basis for the resource is the information in ISO 11238 Substances standard. Actual data exists in the FDA GSRS implementation of 11238.
==Example Scenarios==
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.
==Resource Relationships==
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.code.
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 key regulatory 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 those 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 definitional, 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 (possibly local) summary of the whole SubstanceSpecification, and so be a useful overlap.
The Instance component is not definitional so does not clash.
The Ingredient component 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 details of materials that comprise it. However this is not a currently proposed use case and device material is not supported by the existing Device resource.
Side note: The separate IDMP Product use case (not proposed here, but a possible future concept) does also include details of manufactured devices, and their materials. An expanded Device resource to cover the requirements of IDMP Products, could include 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 via an analogous DeviceSpecification resource, to keep the Device resource small).
Early draft by December 2017 comment-only ballot.
==gForge Users==
riksmithies (already has commit permission)
==When Resource Proposal Is Complete==
'''When you have completed your proposal, please send an email to []'''
==FMG Notes==

Latest revision as of 17:21, 25 June 2019