Open Compute
Open-source agentic AI for health-tech
Open Compute is a powerful Python library that uses AI agents to transform patient journeys into standards-compliant FHIR (Fast Healthcare Interoperability Resources) data. Built by Jori Health, this tool enables healthcare developers to bridge the gap between narrative patient experiences and structured healthcare data.
Quick Start
Installation
pip install open-compute
Requirements
- Python 3.9+
- OpenAI API Key: Set as environment variable
export OPENAI_API_KEY='your-api-key-here'
Usage
Patient Journey to FHIR Conversion
The primary use case is converting narrative patient journeys into structured, validated FHIR resources:
from open_compute import (
PatientJourney,
JourneyStage,
generate_fhir_from_journey,
)
# 1. Define a patient journey with clinical narrative
journey = PatientJourney(
patient_id="patient-123",
summary="58 year old male presents to ER with chest pain, diagnosed with acute MI",
stages=[
JourneyStage(
name="Registration",
description="Patient registered in ER",
metadata={
"timestamp": "2024-01-15T10:30:00Z",
"location": "Emergency Department"
}
),
JourneyStage(
name="Triage",
description="Initial assessment - chest pain, elevated BP",
metadata={
"vital_signs": {
"blood_pressure": "150/95 mmHg",
"heart_rate": "88 bpm"
},
"chief_complaint": "Chest pain"
}
),
JourneyStage(
name="Diagnosis",
description="Diagnosed with acute myocardial infarction",
metadata={
"condition": "Acute MI",
"icd10_code": "I21.9"
}
),
JourneyStage(
name="Treatment",
description="Administered aspirin and nitroglycerin",
metadata={
"medications": ["Aspirin 325mg", "Nitroglycerin 0.4mg"]
}
),
]
)
# 2. Generate FHIR resources using AI
result = generate_fhir_from_journey(
journey=journey,
patient_context="58 year old male named John Doe with history of hypertension",
model="gpt-4o-mini", # or "gpt-4", "gpt-3.5-turbo"
fhir_version="R4",
max_iterations=3,
auto_save=True # Saves to output/john_doe/
)
# 3. Check results
print(f"✅ Success: {result.success}")
print(f"📊 Generated {len(result.generated_resources)} FHIR resources")
print(f"🔄 Iterations: {result.iterations}")
# View generated resource types
for resource in result.generated_resources:
print(f" - {resource['resourceType']}/{resource.get('id', 'no-id')}")
Output Structure
When auto_save=True, generated files are saved to output/{firstname_lastname}/:
output/john_doe/
├── patient_bundle.json # Complete FHIR Bundle (all resources)
├── bulk_fhir.jsonl # Bulk FHIR format (one resource per line)
└── README.txt # Summary of generated resources
Advanced Configuration
from open_compute import AIJourneyToFHIR
# Create agent with custom configuration
agent = AIJourneyToFHIR(
api_key="your-openai-key", # or use env var OPENAI_API_KEY
model="gpt-4o-mini",
fhir_version="R4",
max_iterations=5,
max_fix_retries=3,
auto_save=True,
save_directory="output",
parallel_generation=True, # Faster generation
use_enhanced_context=True # Better accuracy with FHIR profiles
)
# Generate resources
result = agent.generate(journey, patient_context="...")
Examples
We provide comprehensive examples to help you get started:
Running the Examples
# Make sure you have your OpenAI API key set
export OPENAI_API_KEY='your-api-key-here'
# Run the main example
python examples/patient_journey_to_fhir_example.py
Available Examples
| Example | Description | File |
|---|---|---|
| Basic Usage | Complete patient journey with ER visit, diagnosis, and treatment | examples/patient_journey_to_fhir_example.py |
The example demonstrates:
- Creating a patient journey with multiple stages
- Generating FHIR resources (Patient, Encounter, Observation, Condition, MedicationStatement, Procedure)
- Validating generated resources
- Auto-saving to organized output directory
Contributing
We welcome contributions! Open Compute is an open-source project and we'd love your help.
Areas for Contribution
- Additional FHIR resource types
- Support for more FHIR versions
- Enhanced validation rules
- Performance optimizations
- Documentation improvements
Getting Started
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Make your changes
- Run tests (
pytest) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
License
MIT License - see LICENSE for details
Made with 🏥 for better healthcare interoperability
Metadata
Release files for open-compute 0.1.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| open_compute-0.1.9.tar.gz | 6.7 MB | With provenance | Details for open_compute-0.1.9.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| open_compute-0.1.9-py3-none-any.whl | Python 3 | none | any | Details for open_compute-0.1.9-py3-none-any.whl |
Total release size: 13.6 MB
Release files / open_compute-0.1.9.tar.gz
| Download URL | open_compute-0.1.9.tar.gz |
|---|---|
| Size | 6.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b1f9d7cebc1e16512dc0b0b2ae4cefb2ddc2f2a98aa691ff05ebd2518e7bbac
|
|
BLAKE2b-256 checksum How to use checksums |
d722f644414adc9dcd3589ca820427e1b21d3ce59c264abbbabd8203ad73de09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2025.
Transparency logRelease files / open_compute-0.1.9-py3-none-any.whl
| Download URL | open_compute-0.1.9-py3-none-any.whl |
|---|---|
| Size | 6.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
54c647b0d423920b93af22f32a0418689621febd0a802752b7ead40639fa9940
|
|
BLAKE2b-256 checksum How to use checksums |
5f8c3f6cd5dc488f34778ea378054b1c80d1e8d692860ac00772a30756c14fdd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2025.
Transparency logSecurity for open-compute 0.1.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for open_compute-0.1.9.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.