Prerequisites
- A Medera Console account — sign up at the Medera Console.
-
A Developer API Key — see Creating Clients to generate one with
read:phiandwrite:phiscopes for the appropriate project.
1
Install the SDK
Choose the SDK for your stack.
2
Initialize the client
Replace the placeholders with values from your Console.The SDKs handle token acquisition, refresh, and retries automatically. There is no need to manage bearer tokens manually.
3
Send a prediction request
POST a clinical note (or a
documentId) to /api/therapy/suggest-codes. The code_systems field controls which classifications are applied.| Parameter | Type | Required | Description | | :--- | :--- | :--- | :--- | | code_systems | string[] | Yes | One or more coding systems. Recommended pairs in Coding Systems. | | context | object | Yes | The clinical input: { "documentId": "doc_abc" } or { "text": "..." }. | | min_confidence | number | No | Filter out predictions below this threshold (default 0.5). |4
Read the response
A successful response returns three top-level fields: -
codes — the model’s high-confidence predictions. Each entry includes code, display, confidence, anchor (with documentId, span, and quote), and optional severity_qualifier_suggestions. - candidates — lower-confidence codes worth reviewing. - usageInfo — credits consumed for this request.5
Combine coding systems
Most US encounters require more than one coding system. Pass multiple values in See Coding Systems for recommended pairings by encounter type.
code_systems — for example, pairing ICD-10-CM with CPT for an outpatient visit. The response includes codes from all requested systems in the same codes array, each tagged with its system.Next steps
Code Prediction
Endpoint, supported features, coding system options.
How it works
Request schema, response fields, evidence spans, filtering.
Use cases
Encounter coding, CDI review, revenue cycle.
Contact us if you need help getting started or run into issues. medera.info/contact