Difference between revisions of "SubstanceSpecification FHIR Resource Proposal"
Riksmithies (talk | contribs) |
Riksmithies (talk | contribs) |
||
| Line 87: | Line 87: | ||
==Timelines== | ==Timelines== | ||
| − | + | Early draft by December 2018 ballot. | |
==gForge Users== | ==gForge Users== | ||
Revision as of 14:54, 23 September 2017
This page documents a Pending FHIR Resource Proposal
Contents
- 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
SubstanceSpecification
Owning work group name
Committee Approval Date:
13th September 2017
Contributing or Reviewing Work Groups
- Pharmacy
- O&O
FHIR Resource Development Project Insight ID
1338
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. Initial focus to be on the 'Chemical' type (substance and specified substance parts) of that standard and draft resources will be produced to explore the use of FHIR for this. If successful, future scope may be expanded to other areas, and bring the work forward for formal inclusion in the FHIR draft standard.
RIM scope
Similar in scope to the substance parts of CPM
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 project does not intend to clash with the existing Substance FHIR resource, but could potentially complement it with profiles and/or new resource(s).
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 catalogues.
Expected implementations
FDA (already impmented a proprietary message solution for 11238 substances). EMA
Content sources
Basis for the resource is the information in ISO 11238 Substances
Example Scenarios
Substance definitions for the various categories (Chemical, Polymer, Protein etc). Use of "Specified Substance" to add extra information around manufacturing process etc.
Resource Relationships
Reference to Organization (Manufacturer) Expected to be a reference from Substance to SubstanceSpecification, to be able to point to a more detailed definition
Timelines
Early draft by December 2018 ballot.
gForge Users
riksmithies (already has commit permission)
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
