Built to drop into your ecosystem

Works with your stack

Don't see your vendor? If it speaks HL7 v2, FHIR R4, or REST, it connects. Scoped keys and a per-hospital terminology map handle the site-specific details.

Inbound interfaces

Native protocol — read the verdict back out

GRACE has its own vendor-neutral protocol (grace.v1) that works without HL7 or FHIR. Push data in with the ingest endpoints above, then read the computed verdict back out with a scoped key. Every read returns one consistent envelope, so a human or an agent learns the shape once:

# Read the live verdict — no HL7/FHIR required
curl https://iamgrace.baby/api/v1/level \
  -H "Authorization: Bearer grace_xxx"

# → grace.v1 envelope
{
  "protocol": "grace.v1",
  "ok": true,
  "data": {
    "level": "red",
    "drivingAxis": "staffing",
    "drivingAxisLabel": "AWHONN staffing shortfall",
    "awhonnShortfall": 2
  },
  "meta": { "requestId": "…", "generatedAt": "…", "hospitalId": "…" }
}

Errors use the same envelope with { "ok": false, "error": { "code", "message" } } and stable codes (unauthorized, forbidden_scope, not_found, unprocessable). Send an X-Request-Id header and we echo it back in meta.requestId.

Acquiring the modifiers

Most high-value acuity modifiers are not diagnoses — they are medications, flowsheet observations, and labs. Send them as normalized clinical signals (or as FHIR Observation / MedicationAdministration resources) and GRACE maps them to acuity factors automatically, applying time-based decay where AWHONN ratios change over time (e.g. magnesium sulfate is 1:1 for the first hour, then 1:2).

curl -X POST https://iamgrace.baby/api/ingest/clinical \
  -H "Authorization: Bearer grace_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "roomId": 12,
    "roomLabel": "LDR 12",
    "signals": [
      { "kind": "medication", "system": "RxNorm", "code": "6585",
        "display": "magnesium sulfate", "status": "active",
        "startedAt": "2026-06-21T22:05:00Z" },
      { "kind": "observation", "system": "LOINC", "code": "32421-5",
        "value": "Category II", "observedAt": "2026-06-21T22:30:00Z" }
    ]
  }'

Unknown site-local codes fall through to a per-hospital terminology map, so "group beta strep" at one site and "GBS" at another both resolve to the same factor once an admin maps them.

The table below shows how each acuity modifier is acquired out of the box.Diagnosis = HL7 v2 DG1 / FHIR Condition; Signal = FHIR Observation / MedicationAdministration or /api/ingest/clinical; Site-mapped = no shipped rule — activate it for your hospital with a terminology mapping or manual entry.

Scoped API keys

Mint a key per integration at /app/integrations and grant only the scopes it needs. A PeriGen key might carry only ingest:clinical; a Workday key only ingest:roster.

Outbound interfaces

GRACE emits tiered surge alerts over email, SMS (Telnyx), and HMAC-signed webhooks. Point a webhook at your integration engine or a per-vendor adapter (Pulsara, Epic Secure Chat, secure messaging) and relay alerts to the devices your team already uses. Each delivery includes an X-Grace-Signature header (sha256=HMAC_SHA256(secret, rawBody)).

Beyond alerts, GRACE pushes native state events the moment the computed verdict changes — so a partner system can mirror GRACE in real time without polling. Events ship in the same grace.v1 envelope:

Configure endpoints and signing secrets at /app/integrations. Agents can read the full machine contract — read endpoints, envelope, and webhook events — at /api/public/integration-capabilities or /api/openapi.json.