1. NATE Blue Button Directory Detailed overview
May 11, 2017
Webinar

2. NBBD Prototype

5. Fill in all required fields and click next.

6. Upon clicking CONFIRM, the registration component begins the process of validating the registrant.
Review submitted data and CONFIRM or click PREVIOUS and correct.

7. Click DONE and go to the registrant’s email to confirm the address.
First – a new account is created for the registrant and we start the process of confirming that the supplied is correct.
There may be different levels based on the organization’s Consumer Access Capability Maturity Level (?)
Let’s say that they don’t have a CEHRT and aren’t interested in buying a Direct Address to share with consumers securely. Is it still worthwhile to let them register to the Directory with the information that they have?
Click DONE and go to the registrant’s to confirm the address.

8. Note code and click on Activate NBBD Account to validate email account.

9. Log in to your account and enter the code sent to the registrant’s email.

10. Once the account validation steps are complete, a repository record and Direct account is provisioned for the registrant’s organization and an invoice is presented to complete activation.

11. NATE Blue Button for Consumers (NBB4C) Trust Bundle.
Some provider organizations may already have Direct addresses assigned to their medical records department.
This prototype does not show the process flow that would enable the registrant to provide an existing Direct address, nor the verification that would confirm that the given address is configured to enable exchange with consumer controlled applications found in the
NATE Blue Button for Consumers (NBB4C) Trust Bundle.
It is our intent to support this BYODA (bring your own Direct Address) capability when the NBBD is launched for nationwide production purposes.

12. Once the account validation steps are complete, a repository record and a Direct account are provisioned for the registrant’s organization and an invoice is presented to complete activation (this is for demonstration purposes only – many sustainability models may be supported).

13. Prior to moving to production we will need to implement functionality to help manage renewals similar to what WildApricot supports for Membership.
Prior to being released into production, online payment functionality would be implemented. For the prototype, simply click on PAY INVOICE to proceed.

14. Go to the registrant’s email to view the “Registration Successful” message.

15. This message provides the registrant with links to the record that has been inserted in the FHIR-based repository and a link to their Direct portal.

16. Same login as the registration page.
The registrant can access their record in the FHIR-based repository from the sent or via on the prototype’s main page.

17. The prototype supports discovery of Organizations and their associated Medical Records Department. In the future when EMRs support exporting list of consumer friendly associated Providers we will be able to extend the approach to search by Provider Name.
Upon logging into their Editor account, the registrant is able to populate and continuously maintain information about how they enable consumer access.

18. By clicking the View button to the left of the sub-organization level record, the registrant can access the resource record for that “Department.”

19. Note provisioned Direct address populated by the registration process
Edit Medical Records Level Information
Update Type to appropriate value for this sub-org record.
Add phone number to reach Medical Records staff.
Adding additional End users authorized to maintain the Organizations Directory entry not supported in prototype.
Add the MedRec Rep who registered to create the Account.
Note provisioned Direct address populated by the registration process
As a FHIR-based repository, the NBBD is future ready and will be able to support both API-based access methods and other yet to be determined methods of enabling consumer access.

20. By clicking the View button to the left of the organization level record, the registrant can access the resource record for that “Organization.”

21. Edit Organization Level Information
Registrant has the power to make their records discoverable by consumer search, not NATE.
NOTE: NPI value from registration.
NOTE: Support for multiple levels of hierarchy.
NOTE: Sub-organization records indicated.
Physical address of organization can be supplied to support geo-based searching in the future.
Adding additional End users authorized to maintain the Organizations Directory entry not supported in prototype.
Add organizational level details at option of registrant.
Support is provided for multiple hierarchical levels and other benefits of the FHIR-based data model.

22. NBB4C Interoperable Direct Address Portal Provisioned
Same login as the registration page.
A link to the Direct portal provisioned to the organization is also given in the “Successful Registration” . Registrant enters the Direct address provisioned to them and the password they supplied during registration.

23. NBB4C Interoperable Direct Address Portal Provisioned
Same login as the registration page.
Once they are logged into the portal, the registrant can change user information such as the notifications address, which alerts staff to newly arrived messages.

24. NBB4C Interoperable Direct Address Portal Provisioned
All portal functionality is accessible via APIs. Greater workflow integration is achievable for organizations that outsource the MedRec function to third parties.
Same login as the registration page.
Once they are logged into the portal, the registrant can send and receive Direct messages to/from consumers.

26. Consumer Directory Search and Individual Right of Access Requests
Once configuration is complete and the organization has activated their record in the directory, consumers can begin to discover the interoperable address to send their requests.

27. Prototype supports limited search at the organization level
Persona: Alice Vargas -- Fictitious providers and clinical data.

28. For illustration purposes, let’s imagine that the consumer searches the repository for providers in the state of Michigan. She finds the VA facility from which she wants her records and selects “View” to see if she can discover what options she has to retrieve her data.

29. For illustration purposes, let’s imagine that the consumer searches the repository for providers in the state of Michigan. She finds the VA facility from which she wants her records and selects “View” to see if she can discover what options she has to retrieve her data.

30. For illustration purposes, let’s imagine that the consumer searches the repository for her children’s Pediatrician. She finds the Brighton Pediatrics Center and selects “View” to see if she can discover what options she has to retrieve her data.

31. Sending Individual Right of Access request to
Provider Organization via NBBD Direct Address
From within the consumer controlled app of Alice’s choice, she creates a Direct Message. She enters the Direct address she discovered via the NBBD consumer search and provides all three components of an IRA in the body of the message.