Exploring and sharing hands-on best practices for cloud-based FHIR servers and SMART on FHIR integrations — turning fragmented healthcare data into secure, interoperable applications that improve patient care, public health, and healthcare outcomes.
The work shared here reflects more than 15 years of experience working with large, heterogeneous data sets across life sciences and healthcare — from research and analytics to interoperability, cloud architecture, and production healthcare systems.
$ 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
capabilitiesMy work spans the healthcare data lifecycle — from standards-based interoperability and secure application integration to data quality, data governance, digital measures, population health, and value-based care.
Standards-based clinical and administrative data exchange, secure APIs, application authorization, and modern healthcare workflows.
Normalizing heterogeneous healthcare data using standard vocabularies, common data models, profiling, and data-quality frameworks.
Standards and analytics that transform clinical data into measurable quality indicators, care gaps, and actionable information.
Using integrated clinical, claims, and social data to support risk stratification, population health, quality improvement, and outcomes-based reimbursement.
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.
The app reads the FHIR server's SMART configuration and supported capabilities.
The app requests approved scopes through OAuth 2.0 Authorization Code flow with PKCE.
Authenticated identity and applicable SMART launch context are passed to the application.
The app calls the FHIR API using the authorized access token and agreed resource scopes.
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 increasingly combines secure application launch, event-driven exchange, population-scale access, payer-provider automation, analytics, and governed data products.
CRD, DTR, and PAS support standards-based payer-provider workflows and the reduction of manual administrative exchange.
Subscription patterns support responsive workflows when encounters, observations, and other clinical events change.
Asynchronous population export enables analytics, quality measurement, research, and large-scale healthcare data processing.
An emerging approach to portable authorization and access decisions across connected healthcare networks and data holders.
This site doubles as a practical learning and development hub for testing FHIR APIs, SMART launch patterns, synthetic data transformation, and interoperability workflows.
My focus is the practical work required to move from standards and requirements to usable healthcare platforms.
Resource strategy, profiles, implementation guides, API patterns, cloud architecture, scalability, and conformance guardrails.
Reusable launch frameworks, OAuth/OIDC, PKCE, scopes, context, app configuration, launch placement, and verification.
Mapping and normalization across clinical, claims, HL7, X12, NCPDP, synthetic data, quality, governance, and analytics workflows.
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 creates the common language. SMART on FHIR creates the application model. Good architecture turns both into working healthcare systems.