Compliance
FHIR R4, ABDM, ICD-10 / SNOMED / LOINC.
OHM Studio extractions are designed to slot into your hospital's compliance stack with minimal friction.
HL7 FHIR R4
Clinical primitives map directly to FHIR R4 resources:
| OHM primitive | FHIR resource |
|---|---|
vitals-block | Observation (LOINC-coded) |
diagnosis-list | Condition |
medication-list | MedicationRequest |
allergy-list | AllergyIntolerance |
investigation-list | ServiceRequest |
procedure-list | Procedure |
ABDM (India)
Outputs include ABDM-ready identifier fields. The Studio doesn't push to ABDM directly — that's your hospital's job — but the shape it produces is ready to wrap in an ABDM HealthInformationBundle.
Coding systems
OHM canonicalises clinical content for downstream coding:
- ICD-10 — diagnoses
- SNOMED CT — diagnoses, procedures, allergies
- LOINC — laboratory + imaging investigations
- RxNorm — medications (US deployments)
The extraction emits canonical names; a downstream code-picker (built into OHM's main pipeline) attaches codes against your local terminology server.
Audit log
Every Studio API call is logged with:
- Organization ID
- API ID
- API key prefix (never the plaintext)
- Timestamp, latency, token usage
- Request IP, user-agent
Optionally — when retainPayloads is enabled per API — the full input + output JSON. Off by default for privacy.
Data retention
| Data type | Default retention |
|---|---|
| Audio uploads | Discarded immediately after STT |
| Transcripts | Discarded after extraction |
| Structured output | Not stored unless retainPayloads |
| Invocation metadata | 90 days (configurable per org) |
| Audit log | 365 days (configurable per org) |
Self-host
If your compliance posture requires no third-party data movement, OHM Studio is fully self-hostable — Postgres, Redis, MinIO, the API and all three frontends behind a Caddy reverse proxy. Talk to us about enterprise self-hosting.