Difference between revisions of "Medication Administration FHIR Resource Proposal"
Hugh Glover (talk | contribs) |
|||
| Line 12: | Line 12: | ||
| − | = | + | =medicationAdministration= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 32: | Line 32: | ||
==Interested Work Groups== | ==Interested Work Groups== | ||
| − | * | + | *PHER (Immunizations) |
| − | |||
| − | |||
<!-- Additional work groups that may have an interest in assisting with the content of the resource (optional) --> | <!-- Additional work groups that may have an interest in assisting with the content of the resource (optional) --> | ||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
855 | 855 | ||
| − | |||
<!-- 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 --> | <!-- 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== | ==Scope of coverage== | ||
| − | Administration of Medicines to Humans across All Healthcare Disciplines in All Care Settings and All Regions. | + | Administration of Medicines 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 administration may be a single event or may be a series of events over a period of time. As such it is the end point of a process of: | ||
| + | *prescription or ordering | ||
| + | *dispensing or supply | ||
| + | *administration or consumption | ||
| + | |||
| + | Separate resources have been created for medicationPrescription and medicationDispense. | ||
| + | |||
| + | medicationAdministration should not be used to record reports that a patient is taking or has taken a particular medicine. Use the medicationStatement resource for this. | ||
| + | |||
| + | |||
| + | |||
| − | |||
<!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | <!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | ||
Revision as of 10:45, 19 May 2013
This page documents a Pending FHIR Resource Proposal
Contents
medicationAdministration
Owning committee name
Interested Work Groups
- PHER (Immunizations)
FHIR Resource Development Project Insight ID
855
Scope of coverage
Administration of Medicines 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 administration may be a single event or may be a series of events over a period of time. As such it is the end point of a process of:
- prescription or ordering
- dispensing or supply
- administration or consumption
Separate resources have been created for medicationPrescription and medicationDispense.
medicationAdministration should not be used to record reports that a patient is taking or has taken a particular medicine. Use the medicationStatement resource for this.
RIM scope
Substance Administration (SBADM)
- --Lmckenzi 19:05, 10 February 2013 (UTC) Need to be more explicit - SBADM also used for foods, radiation, crop spraying, etc.
Resource appropriateness
Administration is one of the three core steps of use of medicines, the other two being Ordering and Dispensing. In many settings Administration is performed by a separate person from those doing Ordering and Dispensing, and the recording of the administration is frequently recorded by a separate software system. Administration records are a core part of knowing what medication a patient has actually received - having a standard format for this is essential. There is a well established set of attributes that are always required. The pharmacy grpoup spent some time discussing the extent to which the attributes overlapped with those inthe Prescription and Dispensing resources and came to the conclusion that there is a need to express these attributes as part of an Administration resource, not as part of some more abstrtact "Medicines Processing" resource.
- Hugh: I've written this as a paragraph but it might be easier as a table??
Expected implementations
This is a key resource required by almost all Healthcare systems.
- Hugh: Are we looking for named expected implementers here?
- Lloyd: For new resources, I think yes. One of the criteria is "If we develop this resource, who's going to exercise it during the DSTU period". However, this one falls into the category of "anyone using CCDA"
Content sources
- Existing normative V3 Pharmacy RMIMs
- Existing implementations in Canada, The Netherlands and UK
- Planned implementation in Australia
- Some commercial systems
- Lloyd: I'd add - v2, NCPDP, maybe OpenEHR. Not sure we should reference implementations but rather national specifications.
Resource Relationships
Pharmacy will produce resources for MedicationPrescription, MedicationDispense and Medication. There will also be the closely related MedicationStatement resource. Outside Pharmacy Patient; Attribution; Order; Encounter; and Annotation will all be required.
- Lloyd: I think we need more than an enumeration - referenced in what context?
Timelines
Ready for first ballot January 2013
gForge Users
Hugh Glover, Jean-Henri Duteau
- Lloyd: Would normally want the gForge ids rather than names, though doesn't really matter here.
