AoR+UC+L1+-+Assumptions,+Pre+and+Post+Conditions

include component="page" wikiName="siframework" page="esMD Header" toc =Assumptions = Section Description – The Use Case Assumptions section outlines what needs to be in place to meet or realize the requirements of the Use Case (i.e. the necessary privacy and security framework). These points are more functional in nature and state the broad overarching concepts related to the Initiative. The Use Case assumptions will serve as a starting point for subsequent harmonization activities.


 * 1) Federal Bridge and NIST specifications for Level 3 identity assurance are available.
 * 2) Registrations Authority models (RA) and registration authority processes exist for Level 3 identity proofing
 * 3) Certificate Authorities (CA) exist and are capable of providing the necessary digital credentials for signing, encryption and other services required by this Use Case.
 * 4) Technology exists to utilize the digital credentials for signing and encryption of documents and transactions
 * 5) Provider registration process as defined in Use case 1 and AoR L1 require support for proxy or delegation of rights
 * 6) The RA process, CA process, and digital credentials in combination with the signing and encryption process provide all of the necessary information and security context for non-repudiation of the signer and integrity of the Document Bundle
 * 7) Payer, Payer Contractors and Payer Gateway shall be treated as the Payer Entity
 * 8) A Provider, Group of Providers, Agent, and Hospital/Health Systems shall be treated as Provider Entity
 * 9) The signature on a bundle attests that the information submitted is an appropriate, complete (except as noted) and accurate response to the information requested
 * 10) All entities involved in AoR L1 transactions will maintain appropriate audit logs
 * 11) All actors shall create all transactions utilizing industry accepted standards, where available
 * 12) All actors shall ensure all transactions will have appropriate security to ensure data is transmitted with integrity, confidentiality, and reliability
 * 13) All actors and systems shall ensure all transactions will be delivered in a timely manner
 * 14) All actors shall have signed any required participation or data use agreements

=Pre Conditions = Section Description: The Pre-Conditions section describes the state of the system, from a technical perspective, that must be true before an operation, process, activity or task can be executed. It lists what needs to be in place before executing the information exchange as described by the Functional Requirements and Dataset requirements.


 * 1) Payer Entity has the ability to register Provider Entitles for the esMD service, produce and electronically transmit the eMDR to the Provider Entity
 * 2) Provider Entity has the ability to assemble and electronically transmit the required documentation to the Payer Entity in the required format to the required destination.
 * 3) Provider Entity has the required identity materials to qualify for (be identity proofed), receive, and maintain the electronic signing credentials.
 * 4) Provider Entity and Payer Entity shall have completed any required onboarding processes.
 * 5) Provider Entity systems shall maintain the ability to receive eMDRs after successful registration unless terminated through established mechanisms

=Post Conditions = Section Description: The Post Conditions section describes the state of the system, from a technical perspective, that will result after the execution of the operation, process activity or task.


 * 1) Post submission credential and signature artifact processing required by the transmission standard (Deleted 8/3 as it is now part of the Assumptions)
 * 2) Payer Entity information system process the Document Bundle

media type="custom" key="20482192" media type="custom" key="20482196"

include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"