Stream: implementers
Topic: When should we use ElementDefinition.condition ?
Richard Townley-O'Neill (Sep 20 2019 at 06:30):
I'm looking for suggestions as to how to best use ElementDefinition.condition.
In the Patient resource Patient.contact has invariant pat-1 : name.exists() or telecom.exists() or address.exists() or organization.exists()
Of the four elements mentioned in invariant pat-1 (name, telecom, address and organization) only organization claims to be affected by pat-1 (this clam is made with condition)
This is displayed in the standard structure display with the I flag:
1/ Why is organization different to the other elements?
2/ Are there guidelines on when to use condition in resource definitions, such as Patient?
3/ Is it worth applying changes to R4 resources?
4/ Is it worth setting values of condition in profiles?
Grahame Grieve (Sep 23 2019 at 21:13):
- probably an editorial mistake
- the guildeline is that should all be marked. But you can see how important it isn't y the fact that you're the first to comment
- not as a technical correction, but for R5 - make a task
- yes, probably
Richard Townley-O'Neill (Sep 25 2019 at 00:46):
Thanks.
#24860
Last updated: Apr 12 2022 at 19:14 UTC
