DEVELOPER

Developer platform

Integrate through FHIR R4, REST/OpenAPI, events, signed webhooks or DeviceKit, then move from synthetic sandbox evidence to controlled production readiness.

01 / CONCEPT

Integration contract

Choose the surface

Use synchronous APIs for request/response, events for state change, webhooks for partner callbacks and DeviceKit for device channels.

Register ownership

Every application has a business owner, technical owner, environment and security contact.

Prove failure handling

Happy-path success is not enough; test validation, authorization, duplication, retry, replay and dependency failure.

Operate safely

Correlation, logs, certificate/token lifecycle and recovery procedures are part of the integration contract.

02 / WORKFLOW

From sandbox to evidence

01Register an application
02Create the correct OAuth client
03Request least-privilege scopes
04Integrate in sandbox using synthetic data
05Test errors, retries and observability
06Complete production-readiness evidence

03 / SECURITY & PRODUCTION

Production is an evidence decision

The developer overview connects the integration surfaces; production approval still requires owners, approved access, tested failure handling, observability and recovery for each interface actually used.