EHR

Bulk create EHR patients

Creates up to 100 local QuickRCM patient rows from inline JSON and returns per-row counts plus sanitized patient summaries.

POSTNeeds publication reviewExternal or credentialedEHRoperationId: bulkCreateEhrPatientshttps://dev-api.quickintell.com/api/v1/ehr/patients/bulk

Needs publication reviewExternal or credentialedIntegrations

Route status

Needs publication review

The endpoint contract is visible, but QuickRCM has not approved it yet for normal production API use.

Publication status

Needs publication review

Requires product, security/compliance, tenancy, side-effect, or module-owner approval before production public API use. 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/patients/bulk. External use still depends on route classification, release evidence, and endpoint-specific side-effect approval.

What this does now

Shows the generated OpenAPI shape for POST /api/v1/ehr/patients/bulk, but keeps the route out of ordinary production API positioning until review is complete.

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

Do not publish this endpoint as an ordinary developer API until its unresolved decisions are closed.

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	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

This endpoint needs explicit product, security/compliance, tenancy, or side-effect approval before publication.
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	Needs publication review 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 public API.

The Electronic Health Record (EHR) public API exposes organization-scoped QuickRCM patient, appointment, patient-insurance, and appointment eligibility queueing endpoints. These endpoints are local QuickRCM API wrappers: patient, appointment, and insurance writes persist local database records; bulk patient import accepts inline JSON and stays database-only; and appointment eligibility creates a queued local eligibility-check record with `queueOnly: true` instead of contacting a payer, clearinghouse, or external EHR synchronously. Use these endpoints with a tenant-scoped bearer API key. The API key selects the organization; callers should not send `organizationId` as a tenant selector. Lookup/list endpoints require `ehr:read` or `ehr:write`, while create/update/queue endpoints require `ehr:write`. organizationId`. Public responses do not return address JSON, contact JSON, raw EHR payloads, raw payer payloads, raw EDI, credentials, transcripts, uploaded file contents, or other sensitive payloads. Patient names, dates of birth, Medical Record Numbers (MRNs), member identifiers, policy numbers, and contact details are Protected Health Information (PHI) or sensitive coverage data and should be logged only in redacted form. Patient matching behavior differs by endpoint. `findEhrPatientByDemographics` is a narrow lookup by exact trimmed first name, exact trimmed last name, and date-of-birth day. Patient create and bulk create use duplicate-detection helpers that can match same-organization demographics case-insensitively and also consider Medical Record Number (MRN) when supplied.

What this endpoint does

Use case

Use this endpoint for small, API-driven patient backfills or incremental registration imports when a caller can send structured JSON directly.

Before calling

Authenticate with an API key that has `ehr:write`. Split large imports into batches of 100 or fewer patients and use synthetic or redacted data in logs and test fixtures.

Request and response behavior

Request guidance

`patients` must contain 1 to 100 patient objects using the same patient fields as create patient. For each row, the handler checks for an existing same-organization patient matching the row demographics or the supplied MRN. Matching rows are skipped and returned in `patients`; new rows are created. This bulk skip behavior differs from single create, which can return 409 when MRN and demographics identify different patients.

This endpoint does not accept CSV files, presigned uploads, S3 keys, or background-worker job payloads.
Rows are skipped when the authenticated organization already has a patient matching demographics or the supplied MRN.
Address and contact JSON can be stored but are omitted from returned public patient summaries.
Bulk duplicate matching is broader than find-by-demographics because it can match same-organization demographics case-insensitively and can also use supplied MRN.

Response semantics

A 201 response means at least one row was created; a 200 response means the batch completed with no new rows. The response includes `created`, `skipped`, `failed`, sanitized `patients`, row-level `errors`, `meta.organizationId`, and `meta.mode: SAFE_WRITE_DB_ONLY`.

`meta.mode` is `SAFE_WRITE_DB_ONLY`.
`created + skipped + failed` should equal the number of input rows.
`errors[].row` uses a 1-based input row number.

Errors and retries

Treat top-level 400 as an invalid batch shape, 401/403 as credential or tenant authorization issues, and 429 as rate limiting. Row-level failures appear in `data.errors` while successful or skipped rows can still be returned. Reconcile by MRN and demographics before retrying failed rows.

Top-level schema errors fail the request before row processing.
Row-level errors are sanitized messages and should not include raw PHI-heavy payloads.
Do not retry a full batch blindly after a partial success; use returned counts and row errors.

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
patients	body	Yes	object[]	Array of 1 to 100 patient objects to create or skip.	Potential PHI; use synthetic examples and avoid logging raw values.
patients[].firstName	body	Yes	string	Patient given name for the bulk row.	Minimum length: 1. Maximum length: 100. Potential PHI; use synthetic examples and avoid logging raw values.
patients[].lastName	body	Yes	string	Patient family name for the bulk row.	Minimum length: 1. Maximum length: 100. Potential PHI; use synthetic examples and avoid logging raw values.
patients[].dob	body	Yes	string	Patient date of birth for the bulk row. Send `YYYY-MM-DD` when possible.	Minimum length: 1. Potential PHI; use synthetic examples and avoid logging raw values.
patients[].gender	body	No	string	Optional gender value for the bulk row.	Minimum length: 1. Maximum length: 60. Potential PHI; use synthetic examples and avoid logging raw values.
patients[].mrn	body	No	string	Optional Medical Record Number for the bulk row.	Minimum length: 1. Maximum length: 120. Potential PHI; use synthetic examples and avoid logging raw values.
patients[].address	body	No	object	Optional address JSON object for the bulk row. Not returned in public summaries.	Potential PHI; use synthetic examples and avoid logging raw values.
patients[].contacts	body	No	object	Optional contact JSON object for the bulk row. Not returned in public summaries.	Potential PHI; use synthetic examples and avoid logging raw values.

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.

{
  "patients": [
    {
      "firstName": "John",
      "lastName": "Smith",
      "dob": "1984-03-22",
      "gender": "example-gender",
      "mrn": "example-mrn",
      "address": {},
      "contacts": {}
    }
  ]
}

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

Bulk patient import result with no new rows.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "created": 1,
    "skipped": 1,
    "failed": 1,
    "patients": [
      {
        "id": "00000000-0000-4000-8000-000000000001",
        "organizationId": "00000000-0000-4000-8000-000000000001",
        "firstName": "John",
        "lastName": "Smith",
        "dob": "1984-03-22",
        "gender": "example-gender",
        "mrn": "example-mrn",
        "createdAt": "2026-06-08T10:15:30Z",
        "updatedAt": "2026-06-08T10:15:30Z"
      }
    ],
    "errors": [
      {
        "row": 1,
        "message": "Request failed"
      }
    ]
  },
  "meta": {
    "organizationId": "00000000-0000-4000-8000-000000000001",
    "mode": "SAFE_WRITE_DB_ONLY"
  }
}

201

Bulk patient import result.

Generated from the OpenAPI response schema.

{
  "success": true,
  "data": {
    "created": 1,
    "skipped": 1,
    "failed": 1,
    "patients": [
      {
        "id": "00000000-0000-4000-8000-000000000001",
        "organizationId": "00000000-0000-4000-8000-000000000001",
        "firstName": "John",
        "lastName": "Smith",
        "dob": "1984-03-22",
        "gender": "example-gender",
        "mrn": "example-mrn",
        "createdAt": "2026-06-08T10:15:30Z",
        "updatedAt": "2026-06-08T10:15:30Z"
      }
    ],
    "errors": [
      {
        "row": 1,
        "message": "Request failed"
      }
    ]
  },
  "meta": {
    "organizationId": "00000000-0000-4000-8000-000000000001",
    "mode": "SAFE_WRITE_DB_ONLY"
  }
}

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.