|
|
| (38 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]]
| |
| − | </div>
| |
| − | </div>
| |
| − | [[Category:FHIR Resource Proposal]]
| |
| − | [[Category:Pending FHIR Resource Proposal]]
| |
| − |
| |
| − |
| |
| − | <!-- For additional guidance on considerations for resource creation, refer to [[FHIR Resource Considerations]] -->
| |
| − |
| |
| − |
| |
| − | =SubstanceSpecification=
| |
| − |
| |
| − | <!-- 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. -->
| |
| − | [[BR&R]]
| |
| − |
| |
| − | ==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==
| |
| − |
| |
| − | 1338
| |
| − |
| |
| − | <!-- 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==
| |
| − |
| |
| − | 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==
| |
| − |
| |
| − | <!-- 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==
| |
| − |
| |
| − | <!-- What are the resources do you expect will reference this resource and in what context?
| |
| − |
| |
| − | What resources do you expect this resource reference and in what context?
| |
| − |
| |
| − | Note: These may be existing resources or "expected" resource
| |
| − |
| |
| − | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
| |
| − | -->
| |
| − |
| |
| − | ==Timelines==
| |
| − |
| |
| − | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
| |
| − |
| |
| − | ==gForge Users==
| |
| − |
| |
| − | riksmithies (already has commit permission)
| |
| − |
| |
| − | ==When Resource Proposal Is Complete==
| |
| − | '''When you have completed your proposal, please send an email to [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]'''
| |
| − |
| |
| − | ==FMG Notes==
| |
