Aller au contenu principal

Document to FHIR

Category: Healthcare Standards
Node id: document-to-fhir

Standards: PHI, IEC-62304-Class-C

Deterministically map a document-extract ExtractionResult into a FHIR R4 transaction Bundle (Patient + Coverage/Claim/ExplanationOfBenefit for bills, Procedure/Condition for reports, ServiceRequest for referrals, Observation/DiagnosticReport for labs).

What it does​

  • Deterministic ExtractionResult → FHIR R4 mapping
  • Transaction Bundle with conditional-create idempotency
  • No LLM / no code invention

Input ports​

NameTypeRequiredDescription
extractedjsonNoExtractionResult object from document-extract
raw_responsetextNoExtractionResult JSON string (alternative to 'extracted')
document_idtextNoStable document identifier for idempotent conditional creates

Output ports​

NameTypeRequiredDescription
bundlefhir-bundleNoFHIR R4 transaction Bundle ready for fhir-crud transaction
resource_countnumberNoNumber of resources in the bundle
document_typetextNoSource document type
needs_reviewbooleanNoPassthrough of the extraction review flag
successbooleanNoWhether mapping succeeded

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
MRN Identifier Systemidentifier_systemstringNourn:tietai:hydra:mrnFHIR identifier system for the patient MRN
Document Identifier Systemdocument_identifier_systemstringNourn:tietai:hydra:documentFHIR identifier system for the source document id
Default CurrencycurrencystringNoUSDISO-4217 currency when the document does not state one

Runtime notes​

  • Emits a FHIR transaction Bundle; POST it with the fhir-crud 'transaction' operation.
  • With a document_id, Claim/EOB dedupe by document identifier and Patient dedupes by MRN.

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.