|
|
| (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]]
| |
| − | </div>
| |
| − | </div>
| |
| − | [[Category:FHIR Resource Proposal]]
| |
| − | [[Category:Pending FHIR Resource Proposal]]
| |
| − |
| |
| − |
| |
| − | <!-- For additional guidance on considerations for resource creation, refer to [[FHIR Resource Considerations]] -->
| |
| − |
| |
| − |
| |
| − | =MedicinalProduct=
| |
| − |
| |
| − | <!-- 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==
| |
| − |
| |
| − | TBC (PSS has been created and submitted)
| |
| − |
| |
| − | <!-- 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 ISO 11615 IDMP Medicinal Product standard and its ISO/TS 20443 Technical Specification, and other domain areas with similar requirements. 11615 covers detailed definition of products, their submissions to regulators, authorization activitues, ingredients, packaging, accompanying devices, clinical particulars etc). Not all of those are expected to be covered in this single resource.
| |
| − |
| |
| − | ==RIM scope==
| |
| − |
| |
| − | Similar in scope to the product parts of CPM. Entity: Material (EntityClass="MAT")
| |
| − |
| |
| − | ==Resource appropriateness==
| |
| − |
| |
| − | There is an upcoming requirement to support the standardised exchange of detailed Product data, as covered by the ISO 11615 specification.
| |
| − |
| |
| − | This resource does not intend to clash with the existing Medication 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 product 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 products).
| |
| − |
| |
| − | Manufacturers submit this data to regulators, when products are registered or altered, or marketing situations change.
| |
| − |
| |
| − | ==Expected implementations==
| |
| − |
| |
| − | EMA
| |
| − | European Drug manufacturers, who have a requirement to submit to EMA (and already do so in a proprietary format. They will be required to move to IDMP, and this is a good opportunity to use a standards based FHIR solution.
| |
| − | FDA (currently using SPL, which is not likely to change in the near term, but have expressed an interest in researching what can be done with FHIR).
| |
| − |
| |
| − | ==Content sources==
| |
| − |
| |
| − | Basis for the resource is the information in ISO 11615 Substances standard. Actual data exists in the EMA XEVMPD data base and XEVPRM XML messages.
| |
| − |
| |
| − | ==Example Scenarios==
| |
| − |
| |
| − | Pharma companies submit details of new products to regulators. Updates are made when necessary e.g. Clinical particulars change (a new contra-indication), a new marketing authorization exists etc.
| |
| − |
| |
| − | Pharmacies and prescribers can view and download this information for reference and integration with their systems.
| |
| − |
| |
| − | ==Resource Relationships==
| |
| − |
| |
| − | Reference to Organization, for the manufacturer.
| |
| − | Reference to Device (or an auxilliary device defintion such as DeviceSpecification.)
| |
| − |
| |
| − | ===MedicinalProduct and Medication===
| |
| − |
| |
| − | This resource is intended to complement the Medication resource, which is focused on what is commonly needed for medical/clinical use cases. MedicinalProduct adds information needed for regulatory use cases, of which there is little overlap, and also may be appropriate for drug database use.
| |
| − |
| |
| − | Most aspects of MedicinalProduct are not present in Medication at all, and are not current candidates for inclusion in the prescribe/dispense/administer workflow.
| |
| − |
| |
| − | Clinical particulars - indications, contra-indications etc
| |
| − | Authorisations and Marketing - key area for regulators, of little interest to prescribers. Dates, statuses, territories etc.
| |
| − | Product packaging - details of packages, including contents, sizes etc
| |
| − | Ingredients - Typically at a prescribing level these are inherent in the medication code. The Medication resource does allow specifying ingredients of a medicine but this is typical for extemporaneous mixtures, and not the manufacturing of products.
| |
| − |
| |
| − | ===MedicinalProduct and Device===
| |
| − |
| |
| − | TODO
| |
| − |
| |
| − | ==Timelines==
| |
| − |
| |
| − | 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 [mailto:FMGcontact@HL7.org FMGcontact@HL7.org]'''
| |
| − |
| |
| − | ==FMG Notes==
| |
