Haidy® right inside your software.

Your system keeps the patient record. Haidy takes over one step: it receives the context, the doctor records and finishes the consultation in Haidy, and the report comes back into your system. One referral shows how.

Example with a fictional practice system and fictional patient data. Endpoints and fields as documented at docs.44ai.ch.

  1. 1

    Send the context

    Your system uploads the referral letter for the patient as a FHIR DocumentReference. If Haidy does not know the patient yet, it creates them. Sending the same document again does no harm: Haidy keeps one copy.

    POST/v2/patient-files/upload/fhir/external/pat-4711
    {
      "patient_first_name": "Anna",
      "patient_last_name": "Muster",
      "patient_gender": "F",
      "patient_birth_date": "1972-03-14",
      "fhir_document_reference": {
        "resourceType": "DocumentReference",
        "status": "current",
        "type": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "55751-2",
              "display": "Clinical context note"
            }
          ]
        },
        "content": [
          {
            "attachment": {
              "contentType": "application/pdf",
              "data": "JVBERi0xLjcK…",
              "title": "Referral letter"
            }
          }
        ]
      },
      "is_synced_from_ehr": true
    }
    ✓ Sent twice? 409: already uploaded, nothing to do.
  2. 2

    Jump off into Haidy

    A button in your software opens Haidy with the patient already selected: in the browser, or by QR code in the Haidy app on the phone. You build no recording and no report view.

    Practice system
    Muster Anna14.03.1972Today, 10:30 · Palpitations
    Open in Haidy
    https://haidy.ch/integration?email=…&integration=…&unique_id=pat-4711&metadata=…

    Or scan the QR code with the Haidy app

    GET /v2/external-integrations/{integration_id}/qr-code?unique_id=pat-4711
    ⓘ Integration approaches
  3. 3

    Record and finish in Haidy

    The doctor records the consultation. Haidy writes the report from the recording and the referral letter, with a reference to every source. The doctor checks it and finishes the consultation.

    Anna Muster14.03.1972

    Report

    Chief complaint

    Palpitations for three weeks, referred by her GP.1

    Assessment

    Paroxysmal palpitations, so far no signs of structural heart disease.1

    Plan of treatment

    Holter ECG and echocardiography, follow-up in two weeks.2

    1 Referral letterEHR Synced2 Recording 1
    Finish consultation
  4. 4

    Get the report back

    Your system fetches the finished consultations, or Haidy notifies it by webhook. The report comes as FHIR with a LOINC code on every section, or as SOAP, PDF or DOCX, together with the ICD-10-GM codes the doctor confirmed.

    GET/v2/consultations?unique_id=pat-4711&approved=true
    { "total": 1, "data": [{ "id": "c-0815", "unique_id": "pat-4711" }] }

    ↳ Or by webhook, as soon as the consultation is finished

    GET/v2/consultation/c-0815/report/fhir

    One section of the FHIR report

    {
      "title": "Assessment",
      "code": {
        "coding": [
          {
            "system": "http://loinc.org",
            "code": "51848-0",
            "display": "Assessment"
          }
        ]
      }
    }
    GET/v2/consultation/c-0815/codes
    {
      "user_selected_codes": {
        "ICD-10-GM": [
          { "code": "R00.2", "title_full": "Palpitationen", "relation": "treated" }
        ]
      }
    }

Highest quality, full data sovereignty.

Haidy runs its own AI models, without external AI services. You decide where it runs: on your own servers or in a sovereign cloud. Both with the same quality.

  • On premises, in your own data centre
  • Sovereign cloud
  • Medical device
  • ISO 13485:2016
  • EU AI Act
  • EU GDPR
  • No US CLOUD Act
  • ISO/IEC 27001Hosting provider
  • BSI C5Hosting provider

Everything in the Haidy API.

Jump-off for the recommended integration, and the direct endpoints for teams that build their own interface.

FeatureIncluded
Jump-off into Haidy
Jump-off link with the patient already selected
QR code for the Haidy app on the phone
Automatic patient linking by your patient ID
Planned consultations from your calendar
Jump-off link into the Haidy chat for a patient
Your own Haidy address in a custom deployment
Patient context
Upload per patient as a FHIR R4B DocumentReference
PDF, Word, images, text, CSV, JSON and XML
Identical documents kept only once
Import by HIN e-mail
Documents your system manages marked as synced
Write-back
List of finished consultations, with filters
Webhook when a consultation is finished
Report as FHIR with C-CDA sections and LOINC codes, as SOAP, JSON, PDF or DOCX
Public C-CDA section mapping, without an API key
ICD-10-GM codes: Haidy’s proposal and the doctor’s selection
Consultations marked as downloaded
Direct endpoints
Transcription of audio files with Klara: MP3, WAV, WebM, MP4, M4A
Swiss German, German, French, Italian, English and Spanish
Report generation from a transcript, with templates and style settings
Report generation as a stream
Chat API, scoped to a patient
Several API keys per account, each with an expiry date

Want to connect your system to Haidy?

We'll discuss with you which endpoints you need, what the integration into your product looks like, and what that costs for your use case.