Developers
Build apps for Max Health members
Max Health members keep their health records in one place. Build a SMART on FHIR app against our sandbox, and once it is ready, members can open it with their own record connected.
You apply with your Max Health account. Signing in creates one if you do not have one yet.
What you get
A free developer account
Apply with your GitHub username. Once we have verified it, register up to 5 apps against a FHIR R4 server full of synthetic records.
Open standards
SMART App Launch 2.2 and FHIR R4. What you build here runs against any SMART on FHIR server, not only ours.
Sign-in handled
Members sign in with their Max Health account. Your app receives a scoped token and never sees a password.
Members to reach
Listed apps open from the Max Health App Store with the member’s own health record already connected.
How it works
- Sign in with your Max Health account and apply with your GitHub username. The developer account is free.
- We verify your account, and the developer portal at developers.maxhealth.tech opens to you. Your dashboard shows where your application stands.
- Register your app in the developer portal, copy its client ID, and build against synthetic patients.
- Submit it for the live App Store when it is ready: $9 per month or $99 per year per app, refunded if we do not approve it.
Common questions
What does it cost?
The developer account and the sandbox are free. An app listed in the live App Store costs $9 per month or $99 per year per app. You pay when you submit it, and we refund you if we do not approve it.
Why do you verify developers?
Apps in the App Store reach real health records, so we want to know who builds them. Your GitHub account shows us your public work; we may ask a question or two before verifying.
Will my app see real patient data in the sandbox?
No. The sandbox holds synthetic records only. Real member data is reachable only by apps listed in the App Store, and only for members who launch them.
Do I need a backend?
No. A browser or mobile app registers as a public client and uses PKCE. If your app has a backend, give it a JWKS URL and it signs its own token requests, so there is no client secret to store.
Which standards do I build against?
SMART App Launch 2.2 for authorization and FHIR R4 for data. Any SMART on FHIR client library works.
How does my app get into the App Store?
Submit it once it works in the sandbox. We check the scopes it asks for and its privacy policy, then register it in production and list it.
Ready to list your app?
Send us its client ID and what it does. We reply to every developer.