CMS Production Access
Information on getting Production Access to all network of Payer FHIR R4 endpoints
To have your API keys synced with all of our health plan customer environments, you will need to fill out our Privacy and Security form and submit evidence of connecting to our Demo Health Plan environment.
- 1.Fill out our privacy & security attestation questionnaire form, that references our public API terms & conditions and send an email with your completed questionnaire to: cms-prod-access @ 1up.health
[email protected] - 2.Submit the following info to cms-prod-access @ 1up.health
[email protected]- Your App Terms Of service (link or attachment)
- Your App Privacy Policy (link or attachment)
- A square logo for your app (link or attachment)
- 3.In addition, submit a screen recording video of your app connecting to our Demo Health Plan environment and displaying synthetic patient data in your front-end app UI to cms-prod-access @ 1up.health
[email protected](this is more than just showing ability to connect to raw FHIR, but also demonstrate how the data is rendered/used in your app). For information on connecting to our Demo Health Plan sandbox environment see here. - 4.We will review your information and request and approve or request changes or clarifications
- 5.Upon approval, your API keys (and redirects uris) will be synced with our CMS health plan customer environments. Note - you may not use a localhost redirect with our PROD environments, but can in our sandbox while testing and developing.
- 6.To review details on how to access specific health plan customer environments for Patient Access, Provider Directory and Formulary APIs see Connecting to Payer Endpoints.
Guidance on Legal Requirements for App Developers:
https://www.ftc.gov/tips-advice/business-center/guidance/mobile-health-apps-interactive-tool