Practical FHIR notes on SDC form builders and terminology server implementations for healthcare integration teams.
A new FHIR server performance report quietly went public this week and has not yet made the rounds the way bigger interoperability news usually does. Health Samurai put four FHIR servers on the same hardware, the same data, and the same…
What actually breaks a PHQ-9 program at population scale? Rarely the instrument. The PHQ-9 is nine questions, a clean scoring rule, and a LOINC code most tools already know. What breaks the program is everything around the nine questions:…
Transactional FHIR writes break in subtle ways when the upstream system replays a message. The pipeline thinks the write is new. The FHIR server happily creates a second Patient or a duplicate Encounter. A clinician opens the chart and…
Healthcare startups hit the cloud-native vs self-hosted question for their FHIR form engine earlier than they expect. The first form lands fine on whichever option the founder picked over coffee. The third form, the first audit, and the fir
SMART on FHIR apps have a tighter set of constraints around form layers than general FHIR apps do. The form has to launch from an EHR context, respect the scopes the launcher granted, and behave reasonably when the user's session is short.
Patient surveys sit at an interesting fork in the road for modern healthcare apps. The team can model the form as a FHIR Questionnaire and lean on the standard, or roll a custom JSON schema and own every behavior. Both choices work; they fa
React patient portals have a specific need from a SDC renderer. The renderer has to play nicely with the rest of the React tree, hand control back when the host app needs it, and not bring along an opinionated styling system that fights the
Skip logic looks like a small feature until you watch a clinician fill out a 60-question intake form and realize that half the questions should never have rendered. A FHIR form tool that handles conditional logic well saves real minutes per
Replacing a legacy EHR with a FHIR-native stack has a hidden middle. The data model gets a lot of attention, the UI gets a lot of attention, but the form layer is often the thing that determines whether clinicians accept the new system. For
Enterprise healthcare has a different relationship with FHIR Questionnaire tools than smaller teams do. The form layer has to clear procurement, security review, audit logging, and integration with whichever identity provider the rest of th