Stream: implementers
Topic: mandatory
Ashwin Kandel (Feb 05 2019 at 06:38):
I am confused about notion of mandatory field for a resource in FHIR. .Is there such thing as mandatory field for a resource ?
Looking at a specification (Structural Definition) for a certain resource, how will i be able to know what all data fields are mandatory and what all are not if I am to provide a FHIR compliant system.
Yunwei Wang (Feb 05 2019 at 14:43):
Cardinality is 1..1 or 1..*
Lloyd McKenzie (Feb 05 2019 at 15:56):
Mandatory is pretty uncommon in the core specification because resources are expected to be used in such a wide variety of contexts. You'll find tighter requirements in implementation guides. For example, Patient.name is optional in the base spec, because we need to allow for situations where the name is unknown, where the patient is anonymous and for where the patient is a chicken that doesn't have a name. However, the U.S. Core implementation guide which is used for EHR human-centric querying requires patients to have a name - because in that context, the use-cases for no name don't apply.
Last updated: Apr 12 2022 at 19:14 UTC
