Difference between revisions of "Medication Prescription FHIR Resource Proposal"
Hugh Glover (talk | contribs) |
Hugh Glover (talk | contribs) |
||
| Line 82: | Line 82: | ||
<!-- For resources not deemed "key", what interest is there by implementers in using this particular resource. (Should ideally have multiple independent implementations) --> | <!-- For resources not deemed "key", what interest is there by implementers in using this particular resource. (Should ideally have multiple independent implementations) --> | ||
This is a key resource required by almost all Healthcare systems. As such it is key for any system scoped by CCDA. | This is a key resource required by almost all Healthcare systems. As such it is key for any system scoped by CCDA. | ||
| − | |||
| − | |||
==Content sources== | ==Content sources== | ||
Revision as of 20:33, 19 May 2013
This page documents a Pending FHIR Resource Proposal
Contents
medicationPrescription
Owning committee name
Interested Work Groups
- PHER (Immunizations)
- Patient Care
FHIR Resource Development Project Insight ID
855
Scope of coverage
Prescription (or Ordering) of Medicines Supply and Administration to Humans across All Healthcare Disciplines in All Care Settings and All Regions.
The scope of "Medicines" is as defined by the medicines resource and at it's simplest can be taken to be an identified product. This allows very broad interpretation and can cover non-prescribed medication, herbal products, diet supplements, illicit drugs, and even some products that may be classified as devices. The key distinguishing characteristic is that the product is consumed during the process of medicationAdministration and cannot be reused.
An medicationPrescription may be a single event or may be a series of events over a period of time. As such it is the start point of a process of:
- prescription or ordering
- dispensing or supply
- administration or consumption
Separate resources have been created for medicationDispense and medicationAdministration
RIM scope
medicationPrescription corresponds to the RIM Acts of Substance Administration (SBADM) and Supply as constrained in the Pharmacy Domain model Medication Order PORX_RM010120UV
Resource appropriateness
Prescription is one of the three core steps of use of medicines, the other two being Dispensing (or Supply) and Administration. In many settings the three steps are performed by separate people, and are frequently recorded by separate software systems. Prescription records are a core part of knowing what medication a patient is supposed to receive - having a standard format for this is essential. There is a well established set of attributes that are always required. The pharmacy group spent some time discussing the extent to which the attributes for Prescription, Dispensing and Administration overlapped and came to the conclusion that there is a need to express these attributes as part of distinct resources, not as part of some more abstract "Medicines Processing" resource.
Expected implementations
This is a key resource required by almost all Healthcare systems. As such it is key for any system scoped by CCDA.
Content sources
- Existing normative V3 Pharmacy RMIMs
- HL7 v2 specifications
- Existing specifications in Canada, The Netherlands and UK
- NCPDP specifications
- Developing specifications in Australia
- Some commercial systems
Resource Relationships
medicationPrescription is one of a set of three (along with medicationDispense and medicationAdministration ) that describe the normal business lifecycle for point of care systems dealing with Medication. The business lifecycle will frequently be managed by the Order resource. medicationPrescription will frequently be referred to by a carePlan resource.
Timelines
Ready for second ballot September 2013
gForge Users
hugh_glover, Jean-Henri Duteau
