Developers

Build AI-assisted clinical business processes on governed FHIR rails.

Cernia Health is an extensible platform for connected care: FHIR-native data, integration adapters, workflow automation, AI review, applications, SDKs, and deployment choices that let healthcare teams build without starting over.

Quickstart

Make your first authenticated FHIR call

Start with a tenant-scoped developer account and keep the one-time API key in your secret manager. Never commit it to source control or expose it in browser code.

  1. 1. Sign up

    Create your tenant

    Complete onboarding, then open the Developers tab in the admin workspace.

    Start onboarding →
  2. 2. Mint a key

    Copy the secret once

    In Admin → Developers, name the integration and create an API key. The plaintext secret is shown only once; Cernia stores only its hash.

  3. 3. Call the API

    Fetch one Patient resource

    curl --fail --get 'https://api.staging.cerniahealth.com/Patient' \
      --data-urlencode '_count=1' \
      --header 'Authorization: Bearer $CERNIA_API_KEY' \
      --header 'Accept: application/fhir+json'

    A 200 response containing a FHIR search Bundle confirms the key and tenant scope.

  4. 4. TypeScript SDK

    npm install @cernia/sdk-typescript@0.2.1
    import { CerniaClient } from '@cernia/sdk-typescript';
    
    const client = new CerniaClient({
      baseUrl: 'https://api.staging.cerniahealth.com',
      getToken: () => process.env.CERNIA_API_KEY ?? '',
    });
    
    const patients = await client.search('Patient', { _count: 1 });
  5. 5. Python SDK

    python -m pip install cernia==0.2.1
    import os
    from cernia import CerniaClient
    
    client = CerniaClient(
        base_url='https://api.staging.cerniahealth.com',
        get_token=lambda: os.environ['CERNIA_API_KEY'],
    )
    
    patients = client.search('Patient', {'_count': 1})

Need another endpoint? Explore request schemas, responses, and authentication in the interactive API reference.

FHIR-native foundation

Build against patient, visit, task, device, and workflow context without creating a new healthcare data model.

Connect the required context

Bring EHR, device, file, webhook, partner, and custom protocol data into workflow-ready signals.

Workflow runtime

Turn events into queues, assignments, reminders, escalations, approvals, and documented closeout.

Add automation and review

Route work to the right role, let AI prepare drafts where useful, and keep approval steps explicit.

Apps, APIs, and SDKs

Create role-specific screens, extensions, APIs, and SDKs to deliver the workflows your teams need.

Choose your deployment

Match hosting and data-residency to the requirements of the healthcare teams you serve.