EHR Integration

Get EHR integration configuration summary

Returns the authenticated organization's sanitized EHR integration configuration summary, or null when no configuration exists.

GETPublic reference baselineExternal or credentialedEHR IntegrationoperationId: getEhrIntegrationConfighttps://dev-api.quickintell.com/api/v1/ehr-integration/config

Public reference baselineExternal or credentialedIntegrations

Route status

Public reference baseline

Generated endpoint contract may be shown with caveats, but external publication still needs route registry and release evidence.

Publication status

Baseline reference only

Requires E6 route registry and E9 release evidence before external publication. Also requires E2 side-effect policy and E7 credential, webhook, and vendor trust policy before production recipes, SDK inclusion, or try-out access.

Authentication

Bearer API key declared

OpenAPI declares bearer API-key security for this operation.

Tenant context

API-key organization

API-key organization context is authoritative; request organizationId is not a public tenant selector.

Side-effect summary

External or credentialed

May touch credentials, webhooks, SFTP, EHRs, payers, portals, clearinghouses, or other external systems.

Source artifact

docs/openapi/openapi.json

OpenAPI 3.1.0; API 1.0.0.

When to use this endpoint

Use this page as an internal baseline for the integrations contract generated for GET /api/v1/ehr-integration/config. External use still depends on route classification, release evidence, and endpoint-specific side-effect approval.

What this does now

Documents the generated GET /api/v1/ehr-integration/config contract as a external or credentialed baseline endpoint.

What this does not do

Does not prove external GA readiness, SDK readiness, live production execution, or complete module behavior. Read behavior still needs release evidence before broad external publication.

Not public from this page

Live external side effects, file contents, credentials, webhooks, SDK promises, and production recipes are still gated.

Headers and tenancy

Current headers and tenant authority. Target headers stay labeled as future until OpenAPI and release evidence declare them.

Header	Required	Current status	Notes
Authorization	Yes	Current	Bearer <QUICKRCM_API_KEY>. OpenAPI security: bearerAuth.
Idempotency-Key	No	Target/future	Do not claim universal header support until E3 and OpenAPI metadata exist.
X-Request-Id	No	Target/future	Use for support correlation only after approved; not declared as a standard OpenAPI header today.

Required scopes

Unclassified until E6 route metadata exists; do not infer scopes from route names.

Wrong-org behavior

Tenant-safe 404, empty list, or 403 is endpoint-specific and remains an evidence gap until E1 is closed.

Actor and audit

No public actor, audit, or correlation contract is published from OpenAPI alone.

Idempotency and retries

Retry behavior is documented conservatively because universal idempotency headers are not declared.

Topic	Status	Guidance
Current idempotency	Read request; no mutation idempotency contract needed.	Use ordinary safe-read retry behavior with rate-limit backoff.
Universal header	Not declared	Do not document universal Idempotency-Key support until OpenAPI and E3 evidence declare it.
Conflict behavior	Unresolved	Same-key changed-payload, in-flight retry, fingerprint scope, and TTL behavior remain endpoint-specific evidence gaps.

Async jobs and polling

Queued work is accepted work, not proof of completed workflow execution.

Topic	Status	Guidance
Immediate response	No 202 response declared	OpenAPI does not declare HTTP 202 for this operation.
Polling and terminal states	Not indicated by OpenAPI	No generic polling contract is published from this page.
Later side effects	Not proven	Do not infer background execution beyond the documented response.

Files and artifacts

File-like routes need content-class, ownership, scanning, retention, and URL policy evidence before public recipes.

Topic	Status	Guidance
Content class	No file/artifact class inferred	OpenAPI text does not indicate file or artifact handling for this endpoint.
Ownership and storage keys	Not applicable unless a file field is present	Tenant ownership must be proven before retrieval or upload docs. Never expose storage keys as public identifiers.
URLs, scanning, and retention	Unresolved unless endpoint-specific evidence exists	Short-lived URLs, MIME limits, checksums, scanner status, retention, expiration, and legal hold behavior are not implied by OpenAPI examples.

Publication warnings

External or credentialed behavior needs vendor trust, credential, webhook, and callback evidence before publication.

Related platform rules

Workflow Guide Route Status Tenant Context Errors Rate Limits PHI and Security Publication Readiness Side-Effect Modes

Evidence

Evidence	Status	Caveat
OpenAPI artifact	docs/openapi/openapi.json; OpenAPI 3.1.0; API 1.0.0.	Generated baseline contract only.
Route registry	Public reference baseline from documentation classification overlay.	E6 route registry evidence is still required before external publication.
Example validation	Generated examples are internal baseline aids.	No external publication claim; examples must pass no-PHI/no-secret/no-raw-payload/no-storage-key checks.
Last reviewed	Implementation run 20260619T-docs-impl; source boardroom packet 20260619T064820Z.	Refresh this evidence for release workspaces.
Release evidence	E9 required.	No SDK readiness, production readiness, or expanded external docs claim from this endpoint page.

EHR Integration public API.

EHR Integration public APIs expose the tenant-scoped control plane for an organization's configured EHR connection: sanitized configuration summaries, local activation state, field and facility mappings, sync-log visibility, queue-only sync requests, dry-run validation, and conflict-resolution metadata. These endpoints are not raw Fast Healthcare Interoperability Resources (FHIR) proxy routes. Public docs should distinguish returned local metadata from omitted sensitive identifiers. Local ids such as organizationId, config ids, mapping ids, syncLogId, integrationConfigId, entityConfigId, facilityId, and conflictId may be returned, and FACILITY mapping responses intentionally include externalFacilityId and externalSiteId. Raw vendor payload identifiers, sync-log internalId/externalId, conflict localData/remoteData values, raw request/response payloads, patient/source-record identifiers, credentials, endpoint URLs, transformConfig, webhook secrets, and patient demographics should not be documented as returned unless an endpoint schema explicitly does so. Authentication is bearer API-key based. Read endpoints accept EHR Integration read access, while configuration mutations, mapping mutations, queue endpoints, validation endpoints, and conflict resolution require write-level EHR Integration access plus tenant authorization and role-based access control (RBAC). The API key selects the organization; public docs should not present organizationId as a caller-supplied tenant selector. Side-effect language should be precise. `testEhrConnection`, `validateEhrRecordSync`, and `validateEhrFullResync` are validation-only/dry-run routes. `activateEhrIntegrationConfig` and `deactivateEhrIntegrationConfig` are local database-only state transitions. `queueEhrManualSync` and `queueEpicBulkImport` return HTTP 202 queue acknowledgements and do not prove that an external EHR accepted or completed work. Manual sync is publicly allowed only for PATIENT, APPOINTMENT, INSURANCE, and ENCOUNTER even though the shared entityType schema lists additional values for other EHR workflows.

What this endpoint does

Use case

Use this before rendering integration settings, reconciling an ambiguous config update, deciding whether queue/validation calls have a configured EHR, or showing current local health/config metadata.

Before calling

Authenticate with a tenant-scoped API key that can read EHR Integration data. Do not send organizationId; tenant context comes from the bearer credential.

Request and response behavior

Request guidance

This endpoint has no request body or filters.

No request body is accepted.
The API key selects the organization.
Use this to confirm current local configuration before retrying ambiguous write calls.

Response semantics

HTTP 200 returns `data.config` as a sanitized object or null. Config responses include local ids, vendor/display metadata, health metadata, rate/retry/batch settings, webhook-enabled flag, entityConfigs, and timestamps. They intentionally omit baseUrl, siteId, authType, credential status, credentials, webhook secrets, endpoint URLs, and custom vendor config.

`data.config` may be null.
`entityConfigs` describes configured local entity sync policy, not a live vendor capability statement.
The response may include local organization/config ids but not raw vendor credentials or endpoint URLs.

Errors and retries

Treat 401/403 as credential or authorization failures and 429 as a backoff signal. A transient 5xx can be retried with bounded client retries.

401 means bearer authentication is missing or invalid.
403 means the credential/user context cannot read EHR Integration data for the organization.
429 should be retried with backoff.

Template boundary before examples

The route class, authentication state, tenancy rule, side-effect mode, idempotency status, async behavior, file policy, warnings, links, and evidence above are part of the endpoint contract. Treat generated examples below as internal baseline aids until release evidence closes.

Path parameters

This endpoint does not define path parameters.

Query parameters

This endpoint does not define query parameters.

OpenAPI-declared header parameters

Standard platform header guidance appears in the governance panel. This table only lists operation-specific headers declared in OpenAPI.

This endpoint does not define operation-specific header parameters.

Request body

JSON fields from the generated OpenAPI schema with pilot enrichment applied where available. Nested object fields are shown with dotted paths.

This endpoint does not define a JSON request body.

Generated request example

Generated examples are baseline contract aids only. They are not external publication evidence and must not include real PHI, credentials, raw vendor payloads, raw EDI, transcripts, storage keys, or signed URLs.

No request example is declared.

Successful responses

Generated response examples show the baseline OpenAPI contract. Tenant identifier echo, PHI redaction, pagination, money, date/time, and enum semantics remain endpoint-specific publication checks.

200

Sanitized EHR integration configuration for the authenticated organization.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "config": {
      "id": "00000000-0000-4000-8000-000000000001",
      "organizationId": "00000000-0000-4000-8000-000000000001",
      "ehrSystem": "OPENEMR",
      "ehrDisplayName": "Example ehr_integration_config",
      "ehrVersion": "example-ehrversion",
      "apiPreference": "STANDARD_REST",
      "isActive": true,
      "healthStatus": "HEALTHY",
      "lastHealthCheckAt": "2026-06-08T10:15:30Z",
      "rateLimitPerMinute": 1,
      "retryMaxAttempts": 1,
      "retryBackoffMs": 1,
      "syncBatchSize": 1,
      "enableWebhooks": true,
      "entityConfigs": [
        {
          "id": "00000000-0000-4000-8000-000000000001",
          "entityType": "PATIENT",
          "syncDirection": "READ_ONLY",
          "syncStrategy": "REAL_TIME",
          "syncSchedule": "example-syncschedule",
          "sourceOfTruth": "OPENEMR",
          "conflictResolution": "LAST_WRITE_WINS",
          "isActive": true,
          "createdAt": "2026-06-08T10:15:30Z",
          "updatedAt": "2026-06-08T10:15:30Z"
        }
      ],
      "createdAt": "2026-06-08T10:15:30Z",
      "updatedAt": "2026-06-08T10:15:30Z"
    }
  },
  "meta": {
    "organizationId": "00000000-0000-4000-8000-000000000001"
  }
}

Error responses

Errors must remain sanitized. Do not include raw payer, EHR, SFTP, SMTP, Stripe, LLM/OCR, browser automation, file, transcript, EDI, worker, or vendor payloads.

400

Invalid request.