Difference between revisions of "MedicinalProduct FHIR Resource Proposal"
Riksmithies (talk | contribs) |
Riksmithies (talk | contribs) |
||
Line 77: | Line 77: | ||
==Example Scenarios== | ==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== | ==Resource Relationships== |
Revision as of 10:29, 27 September 2017
Contents
- 1 MedicinalProduct
- 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
MedicinalProduct
Owning work group name
Committee Approval Date:
13th September 2017
Contributing or Reviewing Work Groups
- Pharmacy
- O&O
FHIR Resource Development Project Insight ID
TBC (PSS has been created and submitted)
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
TODO Reference to Organization, for the manufacturer.
MedicinalProduct and Medication
TODO
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 FMGcontact@HL7.org