HealthCampOnFHIR

There are more than 10,000 test user accounts available on api.bbonfhir.com.

Here is a list of these users with passwords. All data associated with these users is synthetic.

Some things to be aware of:

• You are working with synthetic data.
• Do not try to design a production version of your app based on implied linkages between user, password and FHIR Id. These linkages are provided to make getting at data in the Code-a-thon easier.
• You can use any of the ids below to log in.
• Once logged in using the standard /api/v1/Patient and /api/v1/ExplanationOfBenefit calls with a FHIR Id the data returned will be based on the FHIR Id that the logged in user is lined to in the Crosswalk. In production a user will only have access to their individual patient profile and ExplanationOfBenefit claims data.
• If the OAuth interface is used the above rule applies. The OAuth calls are at /api/v1/o/Patient or /api/v1/o/ExplanationOfBenefit. A registered application with a valid user token will only be able to access the data that is related to that specific beneficiary user account.
• The /api/v1/open/Patient and /api/v1/open/ExplanationOfBenefit api calls are provided to allow you to pull bulk data for the duration of the Code-a-thon. This type of access WILL NOT BE AVAILABLE in the production implementation. The /api/v1/open calls allow a logged in user to use ANY FHIR Id as part of the call and pull the respective beneficiary’s data. These calls are provided to allow Code-a-thon teams to demonstrate the potential of their applications when they have permission from thousands of beneficiaries to access their records. In other words, these are convenience api calls to allow teams to demonstrate the power of a network of beneficiaries sharing information.

Here is a json version of the table of user ids: https://drive.google.com/file/d/0B5afSPRIQeJaTkctVWR6anJlNmM/view?usp=sharing