Why “FHIR compatible” is too broad
FHIR® covers many resources, versions and profiles. A concrete integration therefore has to name the profiles, their versions, validation logic and target systems. A successful parser or transport path does not establish general FHIR® or ePA conformance.
A bounded structured-data flow
- Identify content and expected profile.
- Bind the profile version and validation rules.
- Represent acceptance or rejection explicitly.
- Hand accepted content to a separately owned application action.
What this page explicitly does not claim: This page does not claim general FHIR®, ePA or TI conformance, certification, profile completeness or approval by an external authority.