Stream: conformance
Topic: snapshot constraints
Chris Grenz (Sep 01 2016 at 23:03):
The snapshot of an SD accumulates constraints from base SDs. For example, if one profiles Patient, the Patient.contact element will include the pat-1 constraint defintion. Should it also include ele-1 from Element?
Chris Grenz (Sep 01 2016 at 23:03):
For completeness, I vote yes. For bloat prevention, no! ;)
Grahame Grieve (Sep 01 2016 at 23:05):
can I have a vote each way too?
Chris Grenz (Sep 01 2016 at 23:05):
ha! sure
Chris Grenz (Sep 01 2016 at 23:05):
looks like the build votes no.
Chris Grenz (Sep 01 2016 at 23:05):
Some profiles on Grahame's server vote yes...
Chris Grenz (Sep 01 2016 at 23:06):
http://fhir3.healthintersections.com.au/open/StructureDefinition/11179-de-change-description
Chris Grenz (Sep 01 2016 at 23:07):
sort of..
Chris Grenz (Sep 01 2016 at 23:08):
@Michel Rutten ?
Grahame Grieve (Sep 01 2016 at 23:13):
see, I can very efficiently vote both ways at once...
Michel Rutten (Sep 02 2016 at 10:08):
Currently the FHIR.NET API snapshot generator does not aggregate constraints from the Element base type. However simply this reflects the current state of the implementation, and not a conscious design decision. I am open to guidance.
Last updated: Apr 12 2022 at 19:14 UTC
