AoR+Use+Case+L1+-+In-Scope+and+Out+of+Scope

include component="page" wikiName="siframework" page="esMD Header"

Updates to the below were made on 7/26.

In Scope
This section indicates what is in scope for the Use Case. For example, it can include the type of transactions, the information/data to be exchanged, and specific aspects that need to be in place to enable the information to be sent, received and understood the same at both ends of the transmission. Note: A suggested starting point for this content is the project charter and related research collected during the Pre-Discovery phase.

Please review items documented in the "In Scope" section of the Charter posted here prior to suggesting additions / revisions to the list


 * Identity Proofing as part of Non-Repudiation of Actor Identity
 * Digital Credential Management required for Non-Repudiation Actions (Signing and Delegation), Data Integrity and Encryption
 * Digital Signatures and Signature Artifacts for Identity and Non-Repudiation
 * Digital Credentials and Artifacts for Non-Repudiation of Delegation as required by UC1 and AoR L1
 * Data Integrity requirement actions and artifacts
 * Encryption of PHI requirements
 * Payer Entity validates submission signature and encryption artifacts(Added 8/3)
 * Payer Entity acknowledges validity* of submission to Provider Entity (Added 8/3)
 * Interactions between Provider Entity or Payer Entity and :
 * Certificate Authority
 * Registration Authority
 * External Provider Directory
 * And each other

Out of Scope
This section indicates what is out of scope for the Use Case. These points may highlight dependencies on the feasibility, implementability, and usability that result in limitations of the Use Case. At a high level, whatever is not declared “In Scope”, is by definition, “Out of Scope”. Note: There may be some items that are out of scope for the Use Case and Functional Requirements Development as well as the Standards Harmonization activities, that can be included as part of a Pilot. These additions will be documented during that particular stage of the S&I Framework process; however, this expansion should not conflict with the previously defined requirements.

Please review items documented in the "In Scope" section of the Charter posted here prior to suggesting additions / revisions to the list


 * Interactions between:
 * Payer and its Payer Contractors
 * Provider and its Agent
 * Payer or Payer Contractor and its Gateway
 * Transaction level encryption
 * Document level signatures and individual contribution signatures (AoR Levels 2,3)
 * Defining delegation of rights within and between Providers and other authors (AoR Levels 2,3)

media type="custom" key="20426068"

media type="custom" key="20482122"

include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"   • Interactions between:  • Payer and its Payer Contractors • Provider and its Agent • Payer or Payer Contractor and its Gateway   • Transaction level encryption • Document level signatures and individual contribution signatures • Defining delegation of rights within and between Providers and other authors