<< Click to Display Table of Contents >> Navigation:  Prescription Entry  > Rx History > View XML

If History is selected for hospital visits, the system will retain and display the data received from SureScripts via the MHR changes. SureScripts will send a synchronous status response message indicating either a success or failure. If no match for the patient query is returned, "No Records Found" will display.

 

 

Select Web Client > Charts > Select Patient > Select Account > Medication Reconciliation > Rx History

 

Medication History - Claim History

 

 

When View XML is selected, the XML that displays will reflect what is currently being displayed on the screen. If the user has selected All in the Payer drop-down, all payers should display in the XML. If only one payer is selected, then only that payer should display in the XML. If a patient has more than 50 medications, the View XML is capable of displaying all of the meds at one time. For Clinic and Outpatient visits, the information will refresh and generate a new XML file every 72 hours.

 

The message request will display the following sections:

 

•Header

oTo Qualifier and From Qualifier

oMessageID will include: uname_profilenum_visitnum_arid_spid

•Patient

•Prescriber

oIncludes Organizational NPI from the Presciber/Identification field, if there is one existing. If not, the Individual NPI of the prescriber should be provided. The NPI will be validated against the industry standard check digit routine (LUHN check).

▪When a nurse accesses Prescription History, the attending physician's NPI will be used for the query.

oWhen the provider associated to the prescription is not the person addressing it, the tag PrescriberAgent tag will be included to show who took the action. This field should be sent if the sender of the message isn't the actual prescriber referenced in Prescriber/Identification.

▪Examples of this when the tag would be included are: a Nurse entering a Telephone Order, a Pharmacist enters a Verbal Order, or the Provider that is covering for the original Prescriber answers a Refill Request.

▪This element would be sent for NewRx, RefillResponse, CancelRx, or RxChangeResponse. For RxRenewalResponses, the PrescriberAgent could appear in ApprovedWithChanges response. A Replace response would populate the Prescriber elements with the new prescriber's information.

•Benefits Coordination

oThe EffectiveDate of the request cannot be more than 1 year into the past and may not be set to go into the future.

oThe ExpirationDate should be set to the current date.

 

NOTE: For ExpirationDate, errors will occur if the date range is more than one year or a future date.

 

oConsent Values:

▪Y = Consent Given

▪X = Parental/Guardian consent on behalf of a minor for prescriber to receive the medication history from any prescriber.

 

 

Select Web Client > Charts > Select Patient > Select Account > Medication Reconciliation > Rx History > View XML

 

Rx XML