Adapter quickstart
Start from the implementation path before coding endpoints.
Adapter contract
Use this reference for endpoints your system implements under the configured adapter base URL. The generated contract below is built from OpenAPI 3.1.0, contract 1.0.
ChartHero calls standard routes under your configured URL.
https://ehr.example.com/integrations/chartheroChartHero sends the partner-issued credential verbatim as the Authorization header value.
Authorization: <partner_issued_header_value>Confirm ChartHero can reach your adapter and authenticate.
POST /v1/validate-connectionVerify and hydrate launched patient or appointment context.
POST /v1/launch/contextReturn provider rows for reviewed mapping and provider linking.
POST /v1/providers/searchReturn ordered partner recommendations for an encounter checklist.
POST /v1/checklist-recommendations/fetchResolve a verified email to stable partner external identifiers.
POST /v1/users/resolve-by-emailReceive failures ChartHero observed at the HTTP boundary of an adapter call.
POST /v1/diagnostics/errorsGenerated from OpenAPI
The raw schema is available at /openapi/organization-adapters/v1/openapi.json.
| Endpoint | Summary |
|---|---|
POST /v1/checklist-recommendations/fetch | Fetch checklist recommendations |
POST /v1/diagnostics/errors | Report error diagnostic |
POST /v1/launch/context | Get launch context |
POST /v1/providers/search | Search providers |
POST /v1/users/resolve-by-email | Resolve user by verified email |
POST /v1/validate-connection | Validate connection |
Loading generated API reference
Rendering the bundled OpenAPI contract.
Start from the implementation path before coding endpoints.
Understand the browser launch and callback sequence.
Use readiness checks before activating an installation.