Stream: Profiling Academy
Topic: Immunization status drop in profile
ravi.kuchi (Jun 17 2021 at 14:48):
Hi, we have a business usecase where the status values in Immunization resource (R4) do not capture different values we have internally. So, we are planning to create an extension to capture our custom status. Having said that we do not want to use the status field which is required as per the spec. Can any one guide how to deal with this kind of situation? Is it expected to populate some value in status even though it does not carry any significance or is there a way to drop that in the profile? (We are using fsh and we get below error)
Cardinality constraints cannot widen the cardinality. 0..0 is wider than 1..1.
Richard Townley-O'Neill (Jun 18 2021 at 01:17):
An immunization without a value for status is not a valid instance of Immunization.
You might find that all of your immunization records are for completed immunizations and that is why have no interest in Immunization.status. If so, in your profile fix the value of Immunization.status to 'completed' and do not make it must support.
That will mean that the sender must populate the element that way and the receiver can ignore it.
ravi.kuchi (Jun 18 2021 at 11:24):
ThankYou!
Last updated: Apr 12 2022 at 19:14 UTC
