Demo Data

Work with demo data to get started quickly

Accessing Demo Data in the API

To help you get started quickly with Human API, we provide a demo data set that is similar to what you will get from a user. This demo data is based on anonymous personal data that we’ve collected.

We make fictional accounts accessible just like any other account. Follow these steps to connect a fictional account:

  1. Launch Connect
  2. When you are prompted to search for a data source, search for Starfleet Medical, Starfleet Labs or Starfleet Pharmacy.
  3. Use demouser and password as the login credentials

Once you have connected your test user to our demo data sources, you are now ready to use our API.

The fictional accounts will have the following datatypes:

  • Allergies
  • Functional Statuses
  • Immunizations
  • Instructions
  • Demographics
  • Plans of Care
  • Procedures
  • Profile
  • Encounters
  • Medications
  • Narratives
  • Problems
  • Test Results
  • Vitals
  • Social History
  • Reports
  • CCDs

For more information about these datatypes, please visit our medical API reference.

Filtering Demo Data by Source

If you would like to see a payload returned from a specific source, you can use the source query parameter like so:

"https://api.humanapi.co/v1/human/medical/encounters?source=54dc427aaa6b4cb7d6203028"
// this is an example--does not return data

🚧

How about demo Wellness accounts?

Human API does not maintain demo accounts with Wellness sources such as Fitbit. Please connect your own accounts in order to test end-to-end authentication.

Simulate errors when authenticating medical sources

Authentication by a medical user in Connect may not always be successful due to a variety of factors. This includes action required in the source medical portal, inaccessibility of the source CCD files, an outage at the source portal, etc.

To help simulate those scenarios, we have specific demo user credentials that you can use for testing. See below for more information:

Common scenarioCredentialsNotesExpected sync status
Technical problem when attempting collection at the source[email protected] / passwordCan use credentials with any sourceError
Terms and Conditions pending approval by the userattention_demouser / passwordUse these credentials only with Starfleet Medical or Starfleet InsuranceAttn Required
User has no collectable data at the sourcenodata_demouser / passwordUse these credentials only with Starfleet Medical or Starfleet InsuranceNo Data Available
3034

You should see the appropriate error status in the Portal and via the API when using different demo credentials

Starfleet Labs

In order to test Starfleet Labs connect, the steps are similar to those listed above:

  1. Launch Connect
  2. When you are prompted to search for a data source, search for Starfleet Labs.
  3. Use demouser and password as the login credentials

The fictional accounts will have the following datatypes:

  • Encounters
  • Medications
  • Narratives
  • Problems
  • Test Results
  • Vitals
  • CCDs

📘

Note:

Starfleet Labs has multiple patient portals

There are several demo accounts available for testing purposes. You can use the same login credentials for all portals: demouser and password

1662

Here are the results from each portal after a successful connection:

Demo_OldNegativeCovid

1870

Demo J&J

1872

Demo - Covid UNK LOINC code

1550

Demo_OldPositiveCovid

1866

Demo Pfizer 1 Date

1872

Demo 3 dates - Pfizer, Moderna, Pfizer

1552

Demo 2 Dates - AstraZeneca, AstraZeneca

1874

Demo_RecentPositiveCovid

1600

Demo_RecentNegativeCovid

1600

Demo_CovidVaccine1Date

1600

Demo Unknown Vaccine

1850

Demo 2 Dates - Novavax, Novavax

1600

Demo Moderna 2 Dates

1600

Demo 3 Dates - Pfizer, Pfizer, Moderna

1600

Demo 3 Dates - Pfizer, Pfizer, Pfizer

1632

Demo 2 Dates - Pfizer, Johnson and Johnson

1622

Endpoints working with demo data

The following endpoints should be able to respond with data. All other endpoints that are not in this list are available and may be called, but will return empty datasets as response