Print Page   |   Your Cart   |   Sign In   |   Join
News & Press: State Legislation

Participating in the Prescription Monitoring transaction (via HIE)

Wednesday, February 14, 2018   (0 Comments)
Posted by: Janet Anderson
Share |

For parties interested in, or participating in, using the Prescription Monitoring transaction (via HIE) for meeting Washington State Meaningful Use / MIPPS requirements…

 

OneHealthPort has completed development and testing of the web services connectivity and processing for the Prescription Monitoring Program (PMP) transaction.   This transaction is available to all providers contracted with the OneHealthPort Health Information Exchange (HIE).

 

The OneHealthPort PMP Implementation Guide has been updated with information about the web services connectivity requirements and posted to the OneHealthPort website.  As a courtesy we are attaching a copy of that guide to this message.

 

The web services version is merely an additional connectivity method for the transaction.  There is no change in the format or content requirements of the existing NCPDP 10.6 version of the PMP query .xml file itself, or the actions and activities that occur at the HIE to transform the NCPDP transaction to a form that is able to be interpreted and to which a response can be returned by the WA State PMP database. 

 

We would like to outline some highlights that are relevant to the web services version of the transaction:

  1. Customers configuring the former version of the PMP transaction have encountered challenges with moving the medication history query out of their electronic health record (EHR) and into their AS2 connectivity tool to be able to exchange the PMP transaction across the HIE.  The new web services connectivity for the PMP transaction will eliminate the need to move the transaction into an intermediary integration tool and/or to the AS2 tool in order to get the transaction to the HIE for processing.  The web services connectivity will allow the transaction to move directly from the EHR to the HIE as a synchronous transaction.
  2. Certificate Authority certificate exchange is required for the web services transaction.  Customers with whom OneHealthPort has already exchanged certificates for use in other web service transactions (i.e. CCD submissions to the CDR), need not use different certificates for the PMP transaction.  The existing certificate configuration can be leveraged at the web services gateway.  What will have to be done at the provider site is configuration for a new endpoint where the PMP transaction will deliver.  Once that endpoint is configured, the transaction will function similarly to how a medication history query processes to a pharmacy benefits manager database (i.e. SureScripts). 
  3. Turnaround times for response messages are expected to be greatly improved, and high volumes of PMP transaction queries are expected to process more efficiently and effectively.

If you are interested in pursuing the web service version of the PMP transaction, at a high level the process would be: 

  1. Provider organization will make the necessary UAT endpoint configuration changes in the EHR.
  2. Successfully process test transactions in UAT
  3. Upon successful testing OneHealthPort will provide the Production PMP transaction endpoint
  4. Provider organization will make the necessary Prod endpoint configuration changes and move forward with production system processing  

Questions or requests for discussion meetings should be sent using the OneHealthPort Support Ticket.

[Note: If your organization is currently processing production transactions, to avoid duplicates, a cutover date/time to discontinue the current AS2 connectivity model and switch to the web services version of the transaction would need to be established.]


more Calendar

2/19/2018
WSPA Legislative Day

2/22/2018
Webinar: A Compounder's Guide to Environmental Monitoring and Remediation

3/5/2018
WSPA Legislative Day

Online Surveys
1402 - ICU Medical Inc Campaign
Association Management Software Powered by YourMembership  ::  Legal