Not all FHIR resources have a clearly defined use case.
Here are 6 multi-purpose resources that can be put to a host of different uses.
- Binary
Used to store any binary content — file, image, XML, PDF document, etc. It’s often referenced from an Attachment url in place of using the Attachment’s data element. Separating out the binary data is especially useful when it comes to query response sizes.
http://hl7.org/fhir/binary.html - Bundle
We’re all familiar with “transaction” bundles and many of us will have encountered “batch” bundles at some point. “Collection” bundles are less common. They have no pre-defined purpose beyond to function as a collection of resources and can be stored in FHIR like any other resource type.
http://hl7.org/fhir/bundle.html - List
A dynamic collection of resources that can be used in a multitude of different ways. One of the great underutilized resources. List is close to being normalized, with a level 4 maturity level. Definitely worth investigating.
http://hl7.org/fhir/List.html - Basic
I wrote an entire post a few months ago warning of the dangers of using the Basic resource. I call it the “when all else fails” resource. It’s a shell of a resource that is given meaning by the extensions you add to it, becoming whatever you want it to be.
http://hl7.org/fhir/R4/basic.html - Flag
Flag’s purpose is to draw attention to something that should be seen immediately. A common use case is to highlight something important about a Patient such as a latex allergy that might cause problems before the Patient’s file is read.
http://hl7.org/fhir/R4/flag.html - Linkage
Connect two or more resources that refer to the same real world entity or occurrence.
Ideal for flagging duplicates, and can reference any resource type.
http://hl7.org/fhir/R4/Linkage.html
Have I missed any hidden gems?
---