What is not in your FHIR Profile? The Role of the 'Contract' Between Systems
Was steht nicht in Ihrem FHIR-Profil?
Summary
An FHIR profile is not merely a technical document, but rather a 'contract' between source and target systems. Care must be taken because information outside the scope defined by this contract (e.g., precision, time, required metadata) risks being lost during the mapping process.
Details
The core nature of an FHIR profile is not just a technical document, but rather an 'agreement' or 'contract' between source and target systems. Information falling outside the scope defined by this contract may be lost during the initial data mapping stage. The author points out that when creating a profile, one commits to the format of the data provided (e.g., cardinalities, data types, bound ValueSets). A critical point is what is *not* in the profile. For instance, while a ValueSet might be bound, it is rare to specify the required level of precision. Furthermore, regarding time data (dateTime), even if only daily records are expected, without constraints, second-level details may be allowed, leading to unintended information loss. Other crucial elements include mandatory metadata (Unit, Status, Negation) and maintaining reference integrity. These require preserving not just the existence of data, but its context or meaning. The author argues that while profiles act as a 'Structure Guardian' by confirming structural rules, they do not guarantee the 'Meaning Guardian,' necessitating a second layer of validation. Ultimately, improving a profile means not simply adding more constraints, but explicitly answering the four key questions mentioned (precision, time, metadata, reference integrity) where they belong. Furthermore, it is concluded that explicitly stating what remains intentionally open is far superior to having a silent omission.
Original content copyright by respective publishers