72-year-old patient with type 2 diabetes on metformin. BP 138/86. No known drug allergies.
Open-source interoperability infrastructure
Turn clinical narratives into FHIR.
FHIR at Will transforms unstructured clinical text into validated FHIR R4 resources. Self-host it and keep clinical data on infrastructure you control.
FHIR at Will
extract · validate
{
"resourceType": "Bundle",
"type": "collection",
"entry": [
{ "resourceType": "Observation", "code": "Age", "value": "72 years" },
{ "resourceType": "Condition", "code": "Type 2 diabetes" },
{ "resourceType": "MedicationStatement", "medication": "metformin" },
{ "resourceType": "Observation", "code": "Blood pressure", "value": "138/86 mmHg" },
{ "resourceType": "AllergyIntolerance", "code": "No known drug allergies" }
]
}
Sponsors
Latest news
What's new
Terminology binding is now its own package
Nearest-neighbor ICD-10-CM binding ships separately. Install it, bind a phrase or a Bundle, and keep codes on catalog rows only.
pip install fhiratwill.terminology_binder
Watch the intro
A short founder intro on why clinical language needs structured FHIR — and how we keep the result deterministic.
The deterministic method
How grounded extraction, deterministic assembly, and verification fit together before a resource is trusted.
Introduction
What is FHIR at Will
Clinical work happens in language. Software needs structure. This short intro explains how FHIR at Will uses AI for interpretation, then deterministic code to assemble FHIR you can inspect.
Watch on YouTubeShape the project
Have a suggestion?
Feature requests, rough ideas, or something that should work better. We read every one.
How it works
From narrative to verified FHIR.
The model identifies grounded facts. Deterministic code handles everything else.
-
01
Protect the narrative
Reviewed rules minimize identifiers before the model sees the text. Protected values are restored only after extraction.
-
02
Extract, then construct
The model selects grounded facts through a closed catalog. Code turns those facts into a deterministic FHIR R4 Bundle.
-
03
Verify before use
Terminology and layered validation determine whether the result can proceed, needs review, or must be rejected.
A required check that cannot run never becomes a false pass. Explore the implementation details →
Why FHIR at Will
Built for real-world interoperability.
Self-hostable
Deploy on your infrastructure.
Privacy first
Your clinical data stays under your control.
Modular
Use only the terminology and validation components you need.
Open source
Transparent, extensible, and community driven.
Available on PyPI
Build with FHIR at Will.
Install the Python package and bring narrative-to-FHIR into your own application.
pip install fhiratwill
Join the community
Build a more interoperable future.
Contribute, suggest features, or explore the project.