EHR Integration

Validate EHR connection-test request

Validates a redacted EHR connection-test request shape and credential-status metadata without calling an external EHR adapter.

POSTPublic reference baselineExternal or credentialedEHR IntegrationoperationId: testEhrConnectionhttps://dev-api.quickintell.com/api/v1/ehr-integration/config/test

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 POST /api/v1/ehr-integration/config/test. External use still depends on route classification, release evidence, and endpoint-specific side-effect approval.

What this does now

Documents the generated POST /api/v1/ehr-integration/config/test 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. Mutating behavior still needs side-effect and retry evidence.

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	No idempotency mechanism is declared.	Do not retry blindly. Check resource, status, batch, or job state before repeating the request.
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	Endpoint-specific	Use only operation-specific status endpoints visible in OpenAPI; generic job behavior, cancellation, retries, and retention are unresolved.
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

Universal Idempotency-Key header support is not declared; retry only after checking endpoint-specific state.
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 Idempotency

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 before saving or reviewing config metadata to confirm public request shape and redaction flags.

Before calling

Prepare a non-secret baseUrl and redacted credentialStatus flags. This is not a live connectivity test.

Request and response behavior

Request guidance

`baseUrl` is required and must be a URI. `ehrSystem` defaults to OPENEMR and accepts OPENEMR, EPIC, CERNER, ECLINICALWORKS, ATHENA, MEDITECH, or OTHER. `validateOnly` must be true for the public handler; sending false returns 400. `credentialStatus.scopes` accepts up to 50 non-empty strings. `credentialStatus.epicBulkGroupId` may be sent as request metadata, but the response returns only `epicBulkGroupIdConfigured`.

`validateOnly` is effectively mandatory as true.
Do not include credential values.
Use healthStatus/health jobs, not this response, for live availability.

Response semantics

HTTP 200 returns `status=VALIDATED`, `validateOnly=true`, `externalRequestMade=false`, and redacted credential-status flags. It does not prove connectivity or expose the Epic group id value.

`externalRequestMade` is always false in the documented public response.
`epicBulkGroupIdConfigured` is boolean only.
No raw endpoint responses or tokens are returned.

Errors and retries

Correct invalid URL, enum, strict-body, or validateOnly=false errors before retrying. Do not poll this as a health check.

400 can mean validateOnly=false or invalid request shape.
403 means write/update permission is missing.

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.

Name	Location	Required	Type	Description	Validation and safety notes
validateOnly	body	No	boolean	Must be true for the public connection-test handler.	Default: true.
ehrSystem	body	No	OPENEMR \| EPIC \| CERNER \| ECLINICALWORKS \| ATHENA \| MEDITECH \| OTHER	Configured vendor enum for request-shape validation. Defaults to OPENEMR.	Enum values are declared in the Type column. Default: OPENEMR.
baseUrl	body	Yes	string (uri)	Vendor endpoint base URI accepted for validation; it should not contain embedded credentials and is not returned.	Format: uri. Sensitive credential or storage-adjacent value; use placeholders only.
credentialStatus	body	No	object	Redacted credential metadata flags/scopes accepted by the request; never raw credential values.	Default: [object Object]. Sensitive credential or storage-adjacent value; use placeholders only.
credentialStatus.hasClientSecret	body	No	boolean	OpenAPI description is missing; publication gap.	Default: false. Sensitive credential or storage-adjacent value; use placeholders only.
credentialStatus.hasPrivateKey	body	No	boolean	OpenAPI description is missing; publication gap.	Default: false. Sensitive credential or storage-adjacent value; use placeholders only.
credentialStatus.hasJwk	body	No	boolean	OpenAPI description is missing; publication gap.	Default: false. Sensitive credential or storage-adjacent value; use placeholders only.
credentialStatus.tokenUrlConfigured	body	No	boolean	OpenAPI description is missing; publication gap.	Default: false. Sensitive credential or storage-adjacent value; use placeholders only.
credentialStatus.scopes	body	No	string[]	Array of up to 50 non-empty scope strings; do not include tokens or secrets.	Default: . Sensitive credential or storage-adjacent value; use placeholders only.
credentialStatus.epicBulkGroupId	body	No	string	OpenAPI description is missing; publication gap.	Minimum length: 1. Sensitive credential or storage-adjacent value; use placeholders only.

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.

{
  "baseUrl": "https://example.quickintell.com/resource",
  "validateOnly": true,
  "ehrSystem": "OPENEMR",
  "credentialStatus": {}
}

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

Connection-test request validation result.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "validateOnly": true,
    "status": "VALIDATED",
    "externalRequestMade": false,
    "credentialStatus": {
      "hasClientSecret": true,
      "hasPrivateKey": true,
      "hasJwk": true,
      "tokenUrlConfigured": true,
      "scopes": [
        "example-scopes"
      ],
      "epicBulkGroupIdConfigured": true
    }
  },
  "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.