PPA+UC+1+-+CMS+focused+User+Story

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





= The content within this page has been incorporated into the PPA UC 1 - Provider Registration =

toc The below sections have been drafted for Provider Registration with CMS using the Generic User Story as a baseline.

Click to download an editable copy.

** User Story **
The Provider Profile Authentication (PPA) work stream is a two part process. The first part is covered in this Use Case and is associated with the provider sending a registration request or Trading Partner Agreement to a payer entity in order to receive the Medical Documentation Request (MDR) electronically.

The provider or Health Information Handler (HIH) submits a registration request to CMS. A secure, trusted registration request via NwHIN Exchange is received by CMS and provider eligibility to receive electronic Medical Documentation Requests (including provider identity) is validated by CMS. CMS then requests Electronic Service Information (ESI) from an External Provider Directory using the validated provider’s identity to determine the capability of provider or Health Information Handler (HIH) to receive an electronic Medical Documentation Request (eMDR). If a valid ESI for eMDR is received by CMS from the External Provider Directory, a confirmation is sent to the provider or HIH as appropriate to notify them of their registration status.

The provider’s registration request can be either confirmed or rejected by the payer entity. If the registration request is confirmed, the payer will attempt to send all future MDRs electronically. If the provider registration request is rejected, the provider does not receive electronic MDRs and can submit another registration request

** Assumptions **

 * 1) The electronic provider registration request will be in a structured electronic format (to be determined through harmonization process).
 * 2) Providers will be identified by their National Provider Identifier (NPI) for registration (CMS). In the absence of an NPI, other unique provider identification can be used (except for CMS).
 * 3) Each provider registration request is for one individual or entity identified by a single NPI (CMS). In the absence of an NPI, other unique provider identification can be used (except for CMS).
 * 4) The External Provider Directory can be a Provider's Internal PD, CMS’ Internal PD, or provided by a third party like Council for Affordable Quality Healthcare (CAQH), Regional Health Information Organization (RHIO) or Health Information Exchange (HIE) Provider Directory (PD) (community or state).
 * 5) esMD Gateway is used by CMS and will support provider registration activities.
 * 6) All transactions will follow national standards.
 * 7) All transactions will have appropriate security to ensure data is transmitted securely, reliably, and with authentication of both the sender and receiver.
 * 8) Providers and/or HIHs will register ESI information with the appropriate Provider Directory.
 * 9) Registration will not expire, but may be subject to reasonable update and termination conditions as determined by each payer.
 * 10) All transactions will use NwHIN Exchange.
 * 11) CMS requires that all providers who wish to receive eMDRs will be required to use this process.

** Pre-Conditions **

 * 1) Provider or HIH can submit all required information electronically to CMS entity to begin registration process.
 * 2) CMS via esMD Gateway can receive and process electronic request for registration.
 * 3) Provider entity or HIH supports the required transmission and payload standards for the registration request.
 * 4) Participating entities have completed any required on boarding processes and signed any required participation or data use agreements.
 * 5) CMS internal information systems are established and in place for timely information verification.
 * 6) External Provider Directories are established and in place for timely information verification.
 * 7) External Provider Directories have the ability to receive information request queries sent from CMS entities, process them, and respond back to CMS using the S&I Provider Directory data sets.
 * 8) CMS can receive and process ESI information from External Provider Directories.
 * 9) Providers or HIHs can receive and act on registration request confirmations (both affirmative and rejection) from CMS.

** Post Conditions **

 * 1) Providers and HIHs will maintain the ability to receive eMDRs after successful registration.
 * 2) Provider registration information is maintained by CMS and available for use by CMS or other users of the provider registration system.

** Actors and Roles **
This section describes the Business Actors that are participants in the information exchange requirements for each scenario. A Business Actor is an abstraction that is instantiated as an IT system application that a Stakeholder uses in the exchange of data needed to complete Use Case action(s). Furthermore, the systems perform specific roles in this Use Case as listed below: __ NOTE: __ A role can be carried out by actors not included in this table; however, for the purposes of this Use Case, we are focusing on the content within the table below. In addition, the same actor may perform a combination of roles.


 * **Business Actor - Generic** || **Business Actor - Specific** || **System** || **Role** ||
 * Registration Requestor || Registration Requestor || Registration Requestors Information System || * Provider Information Source
 * Registration Requestor and Confirmation Receiver ||
 * Provider Agent / Access || Health Information Handler (HIH) || Agent/Access Information System || * Information Requestor/Collector
 * Information Combiner/Router ||
 * Payer (Healthcare and Disability) || Medicare

Medicaid

SSA - Disability

Commercial || Payer Information System || * Validates Providers against current enrolled provider list
 * Confirms ESI to receive MDRs electronically
 * Respond to registration request ||
 * External Provider Directory || External Provider Directory || Provider Directory || * Manage Provider Information
 * Stores and responds to queries for Provider Information ||
 * Payer Gateway || esMD Gateway || Payer Gateway Information System || * Auditing
 * Transaction Logging
 * Routing
 * Transforming ||

Expanded descriptions of the terms corresponding to the table above can be but are not limited to:
 * __Registration Requestor__ - Provider, Provider Organization, Agent
 * __Registration Requestors Information System__ - Provider Directory / Billing System / Medical Records System
 * __Agent/Access Information System__ - Transforming/routing system, Auditing System, (Provider Directory)
 * __Payer Information System__ - Claims System, (Provider Registration System (Provider Directory), Business to Business Systems
 * __Payer Gateway Information System__ - Transforming/routing system, Auditing System

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