Extract multiple FHIR resources from a document

post

https://{instanceUrl}/lang2fhir/document/multi

Extracts text from a document (PDF or image) and converts it into multiple FHIR resources,
returned as a transaction Bundle. Combines document text extraction with multi-resource detection.
Automatically detects Patient, Condition, MedicationRequest, Observation, and other resource types.
Resources are linked with proper references (e.g., Conditions reference the Patient).

Patient identifier handling. US Core requires Patient.identifier (a business identifier such as an MRN). When the source text contains an identifier, it is extracted with an appropriate URI system. When the source text does not contain a detectable identifier, a synthetic one is generated with system: "urn:phenoml:lang2fhir-generated-id" and a UUID value so the bundle remains FHIR-valid and US Core conformant. Callers who need a tenant-specific namespace should rewrite the synthetic system after extraction.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

version

string

required

FHIR version to use

content

string

required

Base64 encoded file content.
Supported file types: PDF (application/pdf), PNG (image/png), JPEG (image/jpeg), TIFF (image/tiff).
File type is auto-detected from content magic bytes.

provider

string

Optional FHIR provider name for provider-specific profiles

implementation_guide

string

Custom Implementation Guide name. When specified, profiles from this IG are included alongside US Core profiles during resource detection. US Core is always the base layer; custom IG profiles are additive.

detection_effort

string

enum

Defaults to standard

Detection effort. 'standard' runs detection once, 'deep' runs detection multiple times for higher recall.

Allowed:

validation_method

string

enum

Defaults to none

FHIR validation method to apply to the generated bundle. 'none' skips validation (default). 'check' runs the bundle through a FHIR structure validator and includes the results in the response. 'fix' runs validation and attempts to auto-correct errors using an LLM (up to 3 validation passes). The response includes results from each pass. Warning: 'fix' can significantly increase latency due to multiple LLM and validation round-trips.

Allowed:

config

object

Optional processing configuration shared across document endpoints.

Responses

400

Invalid request

401

Unauthorized

404

Profile not found

422

Document could not be processed or generated resource failed validation

499

Client closed request before response was ready

500

Server error

504

Request timed out

Language

Credentials

Bearer

JWT

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successfully extracted FHIR resources from document