Difference between revisions of "Prescription Repository Query"

From IHE Wiki
Jump to: navigation, search
(Created page with "''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 ital...")
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
''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.''
+
This Prescription Repository Query defines a Retrieve query and HTTP GET transaction that specifies the dispensed medication history information that should be seen by primary care givers to assist in making an informed decision prior to prescribing additional medications to a patient.  
  
''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.''
 
  
 +
__TOC__
  
''<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>''
+
==Summary==
 +
PRQ defines services that allow physicians to retrieve their patients’ current dispensed medications. This can be useful for identifying potentially deadly drug to drug interactions and over prescribing for opioids.
  
''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
+
==Benefits==
 +
:*Prevent doctor shopping
 +
:*Prevent opioid abuse
 +
:*Prevent drug diversion
 +
:*Prevent life threatening drug to drug interactions
 +
:*Provide physicians with vital information to help make an informed decision before prescribing medications.
  
__TOC__
+
==Details==
  
==Summary==
+
Prescription drug repositories collect data on prescribing and dispensing of controlled substances. This Prescription Repository Query utilizes Pharmacy and FHIR transactions to query a prescription repository for a patient's dispensed medication history. This dispensed medication history can be utilized by providers, pharmacists, and others to address overuse of opioids, drug diversion, physician shopping, and prevent accidental, life threatening, drug to drug interactions. Integrating this information into an Electronic Health Record (EHR) can help simplify the workflow and inform the physician when prescribing medications to a patient.
''<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.  .>''
+
==Systems Affected==
 +
:* EHR Systems
 +
:* Prescription Drug Repository Systems
  
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+
'''Actors & Transactions:'''
  
==Benefits==
+
Transactions
''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (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.  Such benefits help users and vendors make the business case for the profile.  If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
+
  
==Details==
+
The Query Pharmacy Documents [PHARM 1] - This transaction defines how a querying actor has to query the Community Pharmacy Manager
 +
for Community Medication Treatment Plans (MTP), Community Prescriptions (PRE), Community Dispenses (DIS) and Administrations (CMA) and their related documents.
  
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
Dispensed Medication Query [QRPH-57] - The Data Consumer retrieves a patient’s dispensed medications form the Data Creator.  
  
''<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
  
''<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.>''
+
Content Creator - The Content Creator shall be responsible for the creation of content and sharing of the patient’s dispensed medications containing the data elements defined in QRPH TF-3: 6.3.1.D.4.
 
   
 
   
==Systems Affected==
+
Content Consumer - A Content Consumer is responsible for viewing, importing, or other processing options for PRQ document content created by a PRQ Content Creator. This is specified in [PCC-1] document sharing transaction in PCC TF-2: 3.1.
''<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.>''
+
 
 
+
Data Creator - The Data Creator shall be responsible for the creation of content and the transmission of PRQ data elements to a Data Consumer.
* ''PACS systems may store, manage, and/or display Evidence Documents.''
+
* ''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>''
+
Data Consumer - The Data Consumer is responsible for initiating a query to the Data Creator system for data elements meeting certain criteria and can retrieve selected data supplied by the Data Creator.>''
  
 
==Specification==
 
==Specification==
  
'''Profile Status:''' [[Comments| Final Text]]   
+
'''Profile Status:''' [[Comments| Public Comment]]   
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
+
  
 
'''Documents:'''  
 
'''Documents:'''  
  
''<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/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.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-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
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 +
:* PHARM Common parts document [https://www.ihe.net/uploadedFiles/Documents/Pharmacy/IHE_Pharmacy_Suppl_Common.pdf]
 +
:* PHARM Community Medication list [https://www.ihe.net/uploadedFiles/Documents/Pharmacy/IHE_Pharmacy_Suppl_PML.pdf]
 +
:* PHARM Community Medication Prescription and Dispense Integration Profile (CMPD) [https://www.ihe.net/uploadedFiles/Documents/Pharmacy/IHE_Pharmacy_Suppl_CMPD.pdf]
 +
:* HL7 FHIR US Meds Prescription Drug Monitoring Program (PDMP) FHIR Implementation Guide [http://hl7.org/fhir/us/meds/2018May/pdmp.html]
 +
  
 
'''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==
 
 
''<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'''
 
 
''<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.>''
 
 
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
 
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
 
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
 
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
 
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
 
 
 
'''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>''
 
 
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'''
 
 
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>''
 
 
'''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. >''
 
 
[[Category:Profiles]]
 
 
This page is based on the [[Profile Overview Template]]
 
 
[[Category:Templates]]
 
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
 
 
<!--
 
 
Categorize the Domain of your Profile with one of the following (delete the rest):  
 
Categorize the Domain of your Profile with one of the following (delete the rest):  
[[Category:CARD Profile]]
 
[[Category:DENT Profile]]
 
[[Category:ENDO Profile]]
 
[[Category:EYECARE Profile]]
 
[[Category:ITI Profile]]
 
[[Category:PaLM Profile]]
 
[[Category:PCC Profile]]
 
[[Category:PCD Profile]]
 
[[Category:PHARM Profile]]
 
 
[[Category:QRPH Profile]]
 
[[Category:QRPH Profile]]
[[Category:RO Profile]]
+
 
[[Category:RAD Profile]]
+
  
 
Categorize key standards used in your Profile with one or more of the following (delete the rest):
 
Categorize key standards used in your Profile with one or more of the following (delete the rest):
 
[[Category:CDA]]
 
[[Category:CDA]]
 
[[Category:FHIR]]
 
[[Category:FHIR]]
[[Category:DICOM]]
 
[[Category:DICOMweb]]
 
[[Category:HL7v2]]
 
[[Category:XDW]]
 
[[Category:DocShare]]
 
 
And if people forget to do this, we'll comment this out and you can forget to opt-in. :-)
 
-->
 

Revision as of 13:12, 7 June 2019

This Prescription Repository Query defines a Retrieve query and HTTP GET transaction that specifies the dispensed medication history information that should be seen by primary care givers to assist in making an informed decision prior to prescribing additional medications to a patient.


Summary

PRQ defines services that allow physicians to retrieve their patients’ current dispensed medications. This can be useful for identifying potentially deadly drug to drug interactions and over prescribing for opioids.

Benefits

  • Prevent doctor shopping
  • Prevent opioid abuse
  • Prevent drug diversion
  • Prevent life threatening drug to drug interactions
  • Provide physicians with vital information to help make an informed decision before prescribing medications.

Details

Prescription drug repositories collect data on prescribing and dispensing of controlled substances. This Prescription Repository Query utilizes Pharmacy and FHIR transactions to query a prescription repository for a patient's dispensed medication history. This dispensed medication history can be utilized by providers, pharmacists, and others to address overuse of opioids, drug diversion, physician shopping, and prevent accidental, life threatening, drug to drug interactions. Integrating this information into an Electronic Health Record (EHR) can help simplify the workflow and inform the physician when prescribing medications to a patient.

Systems Affected

  • EHR Systems
  • Prescription Drug Repository Systems

Actors & Transactions:

Transactions

The Query Pharmacy Documents [PHARM 1] - This transaction defines how a querying actor has to query the Community Pharmacy Manager for Community Medication Treatment Plans (MTP), Community Prescriptions (PRE), Community Dispenses (DIS) and Administrations (CMA) and their related documents.

Dispensed Medication Query [QRPH-57] - The Data Consumer retrieves a patient’s dispensed medications form the Data Creator.

Actors

Content Creator - The Content Creator shall be responsible for the creation of content and sharing of the patient’s dispensed medications containing the data elements defined in QRPH TF-3: 6.3.1.D.4.

Content Consumer - A Content Consumer is responsible for viewing, importing, or other processing options for PRQ document content created by a PRQ Content Creator. This is specified in [PCC-1] document sharing transaction in PCC TF-2: 3.1.

Data Creator - The Data Creator shall be responsible for the creation of content and the transmission of PRQ data elements to a Data Consumer.

Data Consumer - The Data Consumer is responsible for initiating a query to the Data Creator system for data elements meeting certain criteria and can retrieve selected data supplied by the Data Creator.>

Specification

Profile Status: Public Comment

Documents:

  • Vol. 1 - Section 5 (SWF Profile)
  • Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
  • Vol. 3 - Appendix E
  • PHARM Common parts document [1]
  • PHARM Community Medication list [2]
  • PHARM Community Medication Prescription and Dispense Integration Profile (CMPD) [3]
  • HL7 FHIR US Meds Prescription Drug Monitoring Program (PDMP) FHIR Implementation Guide [4]


Underlying Standards:

Categorize the Domain of your Profile with one of the following (delete the rest):


Categorize key standards used in your Profile with one or more of the following (delete the rest):