Extract multiple FHIR resources from a document
/lang2fhir/document/multiExtracts 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.
Split classifications (optional). config.split_classifications is a caller-defined list, not a fixed taxonomy. Choose each classification id and write a natural-language description for the per-page classifier. For each page, the classifier assigns the best-matching classification or leaves the page ungrouped. Classifications with operation: "group" keep matching pages and label resources extracted from those pages; classifications with operation: "drop" remove matching pages before extraction. The clinical and admin ids in the example are illustrative, not a fixed set.
Body parameters
versionstringrequiredFHIR version to use
contentstringrequiredBase64 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.
providerstringoptionalOptional FHIR provider name for provider-specific profiles
implementation_guidestringoptionalCustom 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_effortstringoptionaldefault standardDetection effort. 'standard' runs detection once, 'deep' runs detection multiple times for higher recall.
standarddeepvalidation_methodstringoptionaldefault noneFHIR 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.
nonecheckfixconfigobjectoptionalOptional processing configuration shared across document endpoints.
page_filterobjectoptionalDeprecated. Use split_classifications instead.
split_classificationsobject[]optionalOptional per-page split classifications. Mutually exclusive with page_filter. This is a caller-defined list, not a fixed taxonomy: choose each classification id and write a natural-language description for the per-page classifier. For each page, the classifier assigns the best-matching classification or leaves the page ungrouped. Pages matching operation=drop are removed before extraction. Pages matching operation=group are kept, and extracted resources attributed to those pages include the classification id in response metadata and FHIR meta.tag. Example ids such as clinical and admin are illustrative, not a fixed set.
idstringrequiredUnique classification id. The reserved id "ungrouped" is not allowed.
descriptionstringrequiredNatural-language description of pages that belong to this classification.
operationstringrequiredOperation applied to pages assigned this classification.
groupdropresource_reviewobjectoptionalOpt-in, report-only faithfulness audit (honored by /lang2fhir/document/multi). For each selected resource type an LLM checks whether the chosen field kinds are actually supported by the full source document. Resources with an unsupported field are pulled out of the returned bundle and reported under resource_review in the response.
targetsobject[]requiredThe resource types to audit and which field kinds to check.
Successfully extracted FHIR resources from document
Response fields
successbooleanoptionalmessagestringoptionalbundleobjectoptionalresourceTypestringoptionaltypestringoptionalentryarray<object>optionalfullUrlstringoptionalresourceobjectoptionalresourceTypestringoptionalmetaobjectoptionaltagarray<object>optionalsystemstringoptionalcodestringoptionalnamearray<object>optionalgivenarray<string>optionalfamilystringoptionalgenderstringoptionalbirthDatestringoptionalrequestobjectoptionalmethodstringoptionalurlstringoptionalresourcesarray<object>optionaltempIdstringoptionalresourceTypestringoptionaldescriptionstringoptionaloriginalTextstringoptionalgroupstringoptionalsourcePagesarray<integer>optionalpage_classificationsarray<object>optionalpage_numberintegeroptionalincludebooleanoptionalclassification_idstringoptionalreasonstringoptional