Question: #FHIR conformance requirements

Feb 17, 2016

Question:

  • status has a cardinality of 0..1 , but it is mentioned as required under Description.
  • Similarly, rest/resource/searchParam/ modifier  has cardinality of 0..* which means optional, but it is mentioned as required under Description. Should I go by the cardinality of these elements?

Answer:

Conformance Status does have a cardinality of 0..1. None of us know why it’s 0..1 not 1..1 like all the other conformance resources. See gForge task 9581.

But the ‘required’ under description for all of these elements refers to the value set binding - if you have one of these elements, it is required to come from one of the specified codes in the valueset. So, yes, you should go by the stated cardinality.