Conecion

Practical FHIR notes on SDC form builders and terminology server implementations for healthcare integration teams.

HL7 FHIR Server Requirements: What You Need Before Buying

Selecting an HL7 FHIR server requires answering specific questions upfront. Getting these right prevents 6-12 months of downstream rework. Question 1: What FHIR version and profiles? R4 with US Core baseline for US deployments. R4B for Subscription-Topic support. R5 for niche cases. Match US Core version explicitly. Question 2: What write throughput? Sustained POST/s at […]

Continue Reading

FHIR Server Value: What Investment Actually Delivers

FHIR server investment delivers specific value; understanding the ROI drivers shapes the business case. Value 1: Ecosystem integration. SMART on FHIR ecosystem access. Third-party apps consume the FHIR API without custom integration per vendor. Value 2: Regulatory compliance. US Core, CMS-0057, ONC certification. FHIR server foundation reduces compliance work per regulation. Value 3: Bulk data […]

Continue Reading

FHIR Implementation Playbook: 7 Steps From Planning to Production

FHIR implementation follows a repeatable playbook. Seven steps cover essentially every production deployment. Step 1: Scope and stakeholder alignment. Define what FHIR APIs, which profiles, which regulatory targets, which timeline. Executive sponsor and dedicated team. Step 2: Server and infrastructure selection. Pick FHIR server, terminology server, auth server based on requirements. See vendor comparison. Step […]

Continue Reading

FHIR Schema in Practice: How Real Systems Structure Data

FHIR schema — resource structure with extensions and profiles — has real-world patterns worth understanding. Six that show up in production. Pattern 1: Profile-driven data model. Every resource conforms to a specific profile. US Core baseline; specialty profiles for specific use cases. Pattern 2: Extension for site-specific data. Custom fields via Extension. Each extension has […]

Continue Reading

FHIR Data Sharing: What Actually Works Cross-Organization

Cross-organization FHIR data sharing is enabled by specific patterns. Four cover essentially all production use cases in 2026. **Pattern 1: SMART Backend Services.** Server-to-server integration via JWT assertion + client credentials. Best for automated system-to-system exchange. **Pattern 2: Bulk Data IG $export.** Payer-to-payer, provider-to-analytics. Best for bulk data movement. Pattern 3: FHIR Messaging with signed […]

Continue Reading

FHIR Platform Integration: 5 Design Patterns for Complex Deployments

Complex FHIR platform deployments use specific integration patterns. Five that show up in enterprise settings. Pattern 1: FHIR API gateway. Central gateway routes to backend FHIR servers, enforces auth, normalizes responses. Uses FHIR REST spec as canonical contract. Pattern 2: Multi-tenant FHIR server. Single deployment, multiple tenants isolated by data partition. Common in health plan […]

Continue Reading