Difference between revisions of "Community Medication Prescription and Dispense"

From IHE Wiki
Jump to navigation Jump to search
m (New page: '''This is a template page. CLICK HERE if you're not sure how to use it. DO NOT MODIFY this page unless you are changing the template for all future users.''' '...)
 
(→‎Specification: updated text in link to supplement)
 
(16 intermediate revisions by 6 users not shown)
Line 1: Line 1:
'''This is a template page.  [[:Category:Templates|CLICK HERE]] if you're not sure how to use it.  DO NOT MODIFY this page unless you are changing the template for all future users.'''
+
__TOC__
  
 +
==Summary==
 +
The Community Medication Prescription and Dispense Integration Profile (CMPD) describes the process of prescription, validation, dispense and administration of medication in the community domain.
  
''This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment.  Delete text in italics and replace it with your material.  Don't forget to delete the double quotes too.''
 
  
''Your page name should simply be Full Profile Name with spaces, with capitals, without the acronym. e.g. Scheduled Workflow. so it provides a title to the page. You can redirect the acronym to the full named page if you like for bonus points.''
+
==Benefits==
  
 +
* Covers the complete workflow in Community Pharmacy setting
 +
** Planning, prescribing, managing, dispensing and administring medication of a patient
 +
* Capable to work with XDS document-based- or database backends
 +
** Includes XDW
  
''<IN ONE LINE, tell a user what the profile is about (including the acronym) so they can decide if they're on the right page.  Basically this should be the same sentence that appears on the [[Profiles]] catalog page>''
 
  
''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
+
==Details==
  
__TOC__
+
In general, the medication business process consists of five distinct processes, which have to be connected through interactions that transfer information and/or guide the workflow. The following figure shows this flow:
  
==Summary==
+
[[image:Pharm_process.PNG|800px|center|The Pharmacy process]]
''<Describe the profile in about a paragraph using user-oriented language. Focus on what it accomplishes for a user (i.e. the Use Cases).  Don't get into how it works, leave that to the Details section.>''
 
  
''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''
+
In the Community Pharmacy domain, the processes of “Planning”, “Prescription”, “Pharmaceutical Advice”, “Dispense” and “Administration” are covered by the Community Medication Prescription and Dispense Profile.
  
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+
The CMPD Profile is intended to be used in the context of the Pharmacy Content Profiles :
 +
* Community Medication Treatment Plan (MTP)
 +
* Community Prescription Supplement (PRE)
 +
* Community Pharmaceutical Advice Supplement (PADV)
 +
* Community Dispense Supplement (DIS)
 +
* Community Medication Administration (CMA)
 +
* Community Medication List (PML)
  
==Benefits==
 
  
''<List the key benefits the profile provides (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler).  Consider using a bullet list for readability>''
 
  
==Details==
+
==Systems Affected==
 +
* Software modules for recording the planning of medication to a patient in clinics, general practicion offices, etc.
 +
* Software modules for recording prescriptions in clinics, general practicion offices, etc.
 +
* Pharmacy software for recording the dispensing of medications
 +
* Software modules for recording medication administrations in clinics, general practicion offices, etc.
  
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
 
  
''<If the user might be familiar with the mechanisms used by the profile, you can mention them here.  E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
+
== Actors & Transactions ==
  
''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
+
* Client-side actors
+
:* Medication Treatment Planner
==Systems Affected==
+
:* Prescription Placer
''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''
+
:* Pharmaceutical Adviser
 +
:* Medication Dispenser
 +
:* Medication Administration Performer
 +
* Server-side actors
 +
:* Community Pharmacy Manager
 +
:* Repository actors (backend)
 +
::* Medication Treatment Plan Repository
 +
::* Prescription Repository
 +
::* Pharmaceutical Advice Repository
 +
::* Dispensed Medication Repository
 +
::* Administered Medication Repository
 +
::* Medication List Repository
  
* ''PACS systems may store, manage, and/or display Evidence Documents.''
+
[[Image:CMPD_Actors_Transactions_Diagram.PNG|800px]]
* ''Display systems may query, retrieve and display Evidence Documents.''
 
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
 
  
'''Actors & Transactions:'''
 
 
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
 
  
 
==Specification==
 
==Specification==
  
'''Profile Status:''' [[Comments| Final Text]]   
+
'''Profile Status:''' [[Comments| Trial Implementation]]   
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 
  
'''Documents:'''  
+
'''Documents:'''
 
+
[https://www.ihe.net/resources/technical_frameworks/#pharmacy IHE Pharmacy Technical Framework:]
''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile.  This is a simple inventory of official normative and informative text.  If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below.  If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>''
+
:* [http://www.ihe.net/uploadedFiles/Documents/Pharmacy/IHE_Pharmacy_Suppl_CMPD.pdf Community Medication Prescription and Dispense (CMPD) Supplement]
 
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
 
''<list all the standards on which the profile is based; if possible with links to sources>''
 
:* [http://dicom.nema.org DICOM]
 
 
:* [http://www.hl7.org HL7]
 
:* [http://www.hl7.org HL7]
:* ...
 
  
 
==See Also==
 
==See Also==
 
''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
 
 
  
 
'''Related Profiles'''
 
'''Related Profiles'''
  
''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''
+
The Community Medication Prescription and Dispense Integration Profile (CMPD) describes the process of prescription, validation, dispense and administration of medication in the community domain.
 +
* [[Community Medication Prescription and Dispense]] [CMPD] defines actors and transactions
  
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
+
The following profiles are defining the content for the CMPD profile:
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
+
* [[Community Medication Treatment Plan]] [MTP] records the planning of medication to a patient.
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
+
* [[Community Prescription]] [PRE] records a prescription to a patient.
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
+
* [[Community Pharmaceutical Advice]] [PADV] records a pharmaceutical advice (validation outcome, management command, etc.) in response to a planned or prescribed medication.
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
+
* [[Community Dispense]] [DIS] records the dispensation of medication to a patient.
 +
* [[Community Medication Administration]] [CMA] records the administration of medication to a patient.
 +
* [[Community Medication List]] [PML] carries a list of planned, prescribed, dispensed or administered medication to a patient.
  
  
 
'''Consumer Information'''
 
'''Consumer Information'''
  
The [[Profile FAQ Template]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''
+
None
  
The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.  ''<Replace the link with a link to the actual Purchasing page for the Profile>''
 
  
 
'''Implementer Information'''
 
'''Implementer Information'''
  
The [[Profile Implementation Template]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
+
None
 +
 
  
 
'''Reference Articles'''
 
'''Reference Articles'''
  
''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis).  Go ahead, Google: IHE <Profile Name> abstract  or Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''
+
None
 
 
  
  
Line 99: Line 104:
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]
 
+
[[Category:PHARM Profile]]
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
+
[[Category:DocShare]]
 +
[[Category:XDW]]

Latest revision as of 15:12, 18 January 2022

Summary

The Community Medication Prescription and Dispense Integration Profile (CMPD) describes the process of prescription, validation, dispense and administration of medication in the community domain.


Benefits

  • Covers the complete workflow in Community Pharmacy setting
    • Planning, prescribing, managing, dispensing and administring medication of a patient
  • Capable to work with XDS document-based- or database backends
    • Includes XDW


Details

In general, the medication business process consists of five distinct processes, which have to be connected through interactions that transfer information and/or guide the workflow. The following figure shows this flow:

The Pharmacy process

In the Community Pharmacy domain, the processes of “Planning”, “Prescription”, “Pharmaceutical Advice”, “Dispense” and “Administration” are covered by the Community Medication Prescription and Dispense Profile.

The CMPD Profile is intended to be used in the context of the Pharmacy Content Profiles :

  • Community Medication Treatment Plan (MTP)
  • Community Prescription Supplement (PRE)
  • Community Pharmaceutical Advice Supplement (PADV)
  • Community Dispense Supplement (DIS)
  • Community Medication Administration (CMA)
  • Community Medication List (PML)


Systems Affected

  • Software modules for recording the planning of medication to a patient in clinics, general practicion offices, etc.
  • Software modules for recording prescriptions in clinics, general practicion offices, etc.
  • Pharmacy software for recording the dispensing of medications
  • Software modules for recording medication administrations in clinics, general practicion offices, etc.


Actors & Transactions

  • Client-side actors
  • Medication Treatment Planner
  • Prescription Placer
  • Pharmaceutical Adviser
  • Medication Dispenser
  • Medication Administration Performer
  • Server-side actors
  • Community Pharmacy Manager
  • Repository actors (backend)
  • Medication Treatment Plan Repository
  • Prescription Repository
  • Pharmaceutical Advice Repository
  • Dispensed Medication Repository
  • Administered Medication Repository
  • Medication List Repository

CMPD Actors Transactions Diagram.PNG


Specification

Profile Status: Trial Implementation

Documents: IHE Pharmacy Technical Framework:

Underlying Standards:

See Also

Related Profiles

The Community Medication Prescription and Dispense Integration Profile (CMPD) describes the process of prescription, validation, dispense and administration of medication in the community domain.

The following profiles are defining the content for the CMPD profile:


Consumer Information

None


Implementer Information

None


Reference Articles

None


This page is based on the Profile Overview Template