PPA+UC+2+-+Functional+Requirements+and+Sequence+diagram





toc = The content within this page has been incorporated into the full Use Case posted here =

= = =Functional Requirements= Functional Requirements identify the capabilities a system playing a role must have in order to enable interoperable exchange of the healthcare data of interest. They provide a detailed breakdown of the requirements in terms of the intended functional behaviors of the application. The Functional Requirements include Information Interchange Requirements and System Requirements. Functional requirements are of two types: Information Interchange Requirements and internal System Requirements. Note: The steps below are not outlined in a sequential order.

Information Interchange Requirements
Information Interchange Requirements define the systems’ names and roles and specify the actions associated with the actual transport of content from the sending system to the receiving system. Information systems participating in this Use Case must meet certain functional requirements based on their role.

Note - Each row in the table is a unique interchange. In rows __III-IV__, __V-VI__, and __VII-XI__, the interchange requirement itself is the same; however, the Sending and Receiving Systems vary.


 * || **Initiating System** ||  || **Information Interchange Requirement Name** ||   || **Receiving System** ||
 * I || Payer Contractor Information System || Send || Query to validate eMDR Consumer’s registration status to receive eMDR request || Receive || Payer Information System ||
 * II || Payer Information System || Send || Response to eMDR Consumers registration status query, address of External Provider Directory, and Integration Profile to receive eMDR request || Receive || Payer Contractor Information System ||
 * III || Payer Information System || Send || Request for Current ESI of eMDR Consumer || Receive || External Provider Directory ||
 * IV || Payer Contractor Information System || Send || Request for Current ESI of eMDR Consumer || Receive || External Provider Directory ||
 * V || External Provider Directory || Send || Response for Current ESI of eMDR Consumer || Receive || Payer Information System ||
 * VI || External Provider Directory || Send || Response for Current ESI of eMDR Consumer || Receive || Payer Contractor Information System ||
 * VII || Payer Contractor Information System || Send || eMDR || Receive || Payer Information Gateway System ||
 * VIII || Payer Information System || Send || eMDR || Receive || Payer Information Gateway System ||
 * IX || Payer Gateway Information System || Send || eMDR || Receiver || eMDR Consumer ||
 * X || Payer Contractor Information System || Send || eMDR || Receive || eMDR Consumer ||
 * XI || Payer Information System || Send || eMDR || Receive || eMDR Consumer ||

System Interchange Requirements
c. Translate /transform received eMDR requests to industry standard or proprietary transactions that can be consumed by the provider eMDR Consuming Information System || f. Query Provider Directory for current ESI g. Generate eMDR request || Consumer registration status i. Query Provider Directory for current ESI j. Generate eMDR request || l. Provide appropriate error messages m. Select appropriate eMDR Consumer based on query parameters n. Return eMDR Consumer demographic and ESI or appropriate error message ||
 * **System** || **System Requirement** ||
 * eMDR Consuming Information System || a. Incorporate eMDR request ||
 * Agent /Access Information System || b. Receives eMDR request
 * Payer Gateway Information System || d. Translate /transform information between payer and industry standard transactions ||
 * Payer Information System || e. Validate eMDR Consumer registration status
 * Payer Contractor Information System || h. Request Payer Information System to validate eMDR
 * Provider Directory || k. Provide demographic and ESI information