Single Request/Response Sample Clauses

Single Request/Response. End End End End End Log in to HIT No Valid HIT? Pass attributes, and the following search criteria to CURES: • Patient First Name Yes • Patient Last Name • DEA/Pharm. Lic. Number • Optional data No No No Validate user credentials Valid user? Valid Role? Valid search criteria? Yes Yes Yes Return result Reject request Reject request Reject request Reject request Pass P/D attributes, search criteria, and security wrapper Single Request/Response Flow Validate Role Validate search criteria Prescriber/Dispenser MOU Entity 1) First Name 2) Last Name 3) DEA # 1) First Name 2) Last Name CURES DOJ 3) Pharmacist Lic. # • Query Use Case 2 – Multiple Matches (Picklist) o Use Case 2 supports multiple matches, via a picklist. In this use case, a patient search returns multiple entities using a NCPDP-like message structure. The requesting entity would then send one or multiple single requests to retrieve the prescription history associated to the matched entity. o For those HIT systems that cannot support this functionality, a response message redirecting the health care practitioner/pharmacist to the CURES web application is returned.