You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Which FHIR backend should Last EHR support next?
#76
Medplum is the supported authenticated backend today, and the bundled HAPI stack covers local synthetic evaluation. The adapter seam is ready for a second authenticated backend: there is a documented contract (docs/adapters.md), an executable starter (examples/fhir-adapter-starter), and shared contract tests.
Open spikes: #73 (Aidbox), #74 (Firely Server), #75 (Oystehr).
What I want to learn from you:
Which backend would you actually integrate against in the next few months?
What auth mode does your deployment use (client credentials, SMART, static token)?
Would you be willing to help validate an adapter against a synthetic project on your stack?
The next adapter ships when someone with a real deployment will co-validate it, so concrete answers here directly set the order of work.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Medplum is the supported authenticated backend today, and the bundled HAPI stack covers local synthetic evaluation. The adapter seam is ready for a second authenticated backend: there is a documented contract (docs/adapters.md), an executable starter (examples/fhir-adapter-starter), and shared contract tests.
Open spikes: #73 (Aidbox), #74 (Firely Server), #75 (Oystehr).
What I want to learn from you:
The next adapter ships when someone with a real deployment will co-validate it, so concrete answers here directly set the order of work.
All reactions