01
HL7 FHIR Architecture
FHIR R4 APIs, US Core profiles, resource modeling, search, bundles, terminology, implementation guides, data mapping, validation, and implementation strategy.
Healthcare interoperability
FHIR is more than an API.
It is infrastructure for better healthcare.
I design and implement standards-based healthcare platforms using the HL7® FHIR® standard, SMART on FHIR, secure APIs, cloud architecture, analytics, and modern data workflows — turning fragmented healthcare data into usable information and interoperable applications.
FHIR · SMART on FHIR · OAuth 2.0 / OIDC · US Core · Bulk FHIR · Healthcare APIs · Data Quality · Analytics
$ GET /Patient/43dd4e31-0c9d-42c7-a2e1-53ccf0e09dba
200 OK
{
"resourceType": "Patient",
"meta": {
"profile": [
"http://hl7.org/fhir/us/core/..."
]
}
}
$ GET /.well-known/smart-configuration
SMART App Launch discovery
authorization_endpoint
token_endpoint
grant_types_supported
code_challenge_methods_supported
capabilitiesInteroperability expertise
From standards to production architecture.
I work across the full interoperability lifecycle: requirements, architecture, data mapping, API design, security, validation, implementation, and delivery.
02
SMART on FHIR
Application launch architecture using OAuth 2.0, OpenID Connect, PKCE, SMART scopes, launch context, discovery, registration, and reusable app-launch frameworks.
03
Cloud + Data Platforms
Cloud-native healthcare platforms, event-driven integration, analytics, data quality, governance, and scalable pipelines across payer, provider, HIE, and public-sector environments.
HL7 FHIR R4
US Core
SMART App Launch
OAuth 2.0
OpenID Connect
PKCE
Bulk FHIR
FHIRPath
LOINC
SNOMED CT
RxNorm
X12 / NCPDP
SMART on FHIR
Secure applications inside healthcare workflows.
SMART on FHIR combines standards-based clinical data access with OAuth 2.0 and OpenID Connect so authorized applications can launch with appropriate user and clinical context.
Discover
The app reads the FHIR server's SMART configuration and supported capabilities.
Authorize
The app requests approved scopes through OAuth 2.0 Authorization Code flow with PKCE.
Launch
Authenticated identity and applicable SMART launch context are passed to the application.
Use FHIR
The app calls the FHIR API using the authorized access token and agreed resource scopes.
SMART discovery essentials
For SMART App Launch 2.x, a FHIR server exposes /.well-known/smart-configuration. Core launch metadata includes authorization and token endpoints, supported grant types, PKCE support, and SMART capability declarations.
Modern interoperability architecture
FHIR is becoming a platform for workflows, not just data exchange.
Modern interoperability increasingly combines secure application launch, event-driven exchange, population-scale access, payer-provider automation, analytics, and governed data products.
Prior Authorization
CRD, DTR, and PAS support standards-based payer-provider workflows and the reduction of manual administrative exchange.
FHIR Subscriptions
Subscription patterns support responsive workflows when encounters, observations, and other clinical events change.
Bulk FHIR
Asynchronous population export enables analytics, quality measurement, research, and large-scale healthcare data processing.
SMART Permission Tickets
An emerging approach to portable authorization and access decisions across connected healthcare networks and data holders.
Implementation matters. Successful FHIR programs depend on more than exposing endpoints:
profiles, terminology, extensions, data quality, conformance testing, identity, security, governance, and workflow validation all matter.
FHIR lab
Public servers, synthetic data, and implementation tools.
This site doubles as a practical learning and development hub for testing FHIR APIs, SMART launch patterns, synthetic data transformation, and interoperability workflows.
Synthetic data examples
Multi-organization patient
Albert Ward is split across State of Oklahoma and Ash Family Medical LLC to demonstrate one patient represented by multiple contributors in an HIE-style workflow using a deterministic Medicaid anchor.
20 encounters · 366 resources
Longitudinal patient records
Two lifetime Synthea patient records demonstrate how linked FHIR resources form a longitudinal record.
591 resources
Transformation scripts
synthea_sanitize_v4.py
Removes or replaces Synthea/GitHub artifacts while preserving standards-based FHIR, US Core, LOINC, SNOMED CT, CVX, NPI, UCUM, and related content.
myhealth_gamble_localize.py
Applies Oklahoma / practice-specific values after neutral sanitization, including Organization, Location, Practitioner, and PractitionerRole localization.
FHIR resource count utility — sample output
Observation: 99
Encounter: 16
DiagnosticReport: 2
MedicationRequest: 2
Condition: 3
Procedure: 8
------------------------
TOTAL: 130How I help
Interoperability strategy grounded in implementation.
My focus is the practical work required to move from standards and requirements to usable healthcare platforms.
A
FHIR Architecture & API Design
Resource strategy, profiles, implementation guides, API patterns, cloud architecture, scalability, and conformance guardrails.
B
SMART Application Integration
Reusable launch frameworks, OAuth/OIDC, PKCE, scopes, context, app configuration, launch placement, and verification.
C
Healthcare Data Transformation
Mapping and normalization across clinical, claims, HL7, X12, NCPDP, synthetic data, quality, governance, and analytics workflows.
About
Healthcare interoperability built for real-world delivery.
My background spans payer, provider, health information exchange, state health, analytics, cloud architecture, and product delivery. I focus on making complex healthcare standards understandable, implementable, and operational.
FHIR & API Strategy
FHIR R4, US Core, SMART on FHIR, Bulk FHIR, implementation guides, API ecosystems, resource modeling, validation, and conformance.
Healthcare Data Engineering
Mapping and transformation across HL7, FHIR, X12, NCPDP, clinical data, claims, terminology, synthetic data, and analytics-ready models.
Architecture & Delivery Leadership
Cloud platforms, governance, technical requirements, cross-functional delivery, product thinking, process improvement, and practical implementation guardrails.
Build on standards
Better healthcare workflows start with trusted, usable data.
FHIR creates the common language. SMART on FHIR creates the application model. Good architecture turns both into working healthcare systems.