Medication Administration FHIR Resource Proposal

MedicationAdministration

Owning committee name

Pharmacy

Interested Work Groups

• None
• Hugh: There is a distinction between an interest in the construction vs an interest in the outcome. Probaly need to capture both
• Lloyd: Should probably express this as "Reviewing WGs"

FHIR Resource Development Project Insight ID

855

• Hugh: Searching Project Insight for FHIR Resources didn't find this!

Scope of coverage

Administration of Medicines to Humans across All Healthcare Disciplines in All Care Settings and All Regions.

• --Lmckenzi 19:05, 10 February 2013 (UTC) What are the boundaries? Encompass immunizations? Veterinary? Spraying plants? Radiation/light therapy? Non-prescribed medications? Herbal products? Meal Supplements? Illicit drugs? Single administration vs. "course" of administration over days/weeks/years?

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.