Stream: genomics
Topic: FHIR lingo
Bret H (Nov 21 2019 at 11:48):
This thread is to help beginners or refresh intermediate FHIR implementers on lingo which maybe new in the world of FHIR. The terms will change over time and some will become more well-worn. But in the mean time to help out threads be clearer, let's get some definitions going
Bret H (Nov 21 2019 at 11:54):
Extension - this element is a FHIR construct to allow creation of a data element to extend a profile. Specific extensions may not be supported by all systems. The best way to describe them maybe to say that if a receiving system were to ignore an extension the information would still be valid (i.e. the extension could be removed form the data instance - message - and the information would still be correct/complete). An example extension might be a field such as 'human readable drug name' in a data instance about a Medication. The extension is computable from the other fields in the data instance (product, dose etc). The absence of the extension 'human readable drug name' would not remove essential information.
Bret H (Nov 21 2019 at 11:55):
@Patrick Werner or @Jamie Jones the use of 'invariant on' is a phrase that is showing up on the zulip chat. Can you define what it means in the context of FHIR today.
Kevin Power (Nov 21 2019 at 14:30):
https://www.hl7.org/fhir/conformance-rules.html#constraints
All elements may have constraints attached to them (also known as 'invariants').
Bret H (Nov 25 2019 at 15:58):
https://www.hl7.org/fhir/conformance-rules.html#constraints
All elements may have constraints attached to them (also known as 'invariants').
``` Kevin Power could you expound on how 'invariant' might be used?
Kevin Power (Nov 25 2019 at 16:11):
Lots of things. Most if not all resources have a Constraints section, like this one on the base Observation resource: http://build.fhir.org/observation.html#invs
Last updated: Apr 12 2022 at 19:14 UTC
