Convert document to FHIR resource

Extracts text from a document (PDF or image) and converts it into a structured FHIR resource.

Patient identifier handling. When generating a patient (or patient-canvas) resource, 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 resource remains FHIR-valid and US Core conformant. Callers who need a tenant-specific namespace should rewrite the synthetic system after extraction.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required

FHIR version to use

string
required

Type of FHIR resource to create. Accepts any FHIR resource type or US Core profile name.

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.

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
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json