FHIR Chat · Section Level Profiles · conformance

Stream: conformance

Topic: Section Level Profiles


view this post on Zulip Grahame Grieve (Nov 05 2018 at 07:05):

One of my outstanding tasks has to sort out how to make section level templates work in FHIR. @Ewout Kramer and I laid out a strategy for this - here are my test templates to test that I have it working. @Sean McIlvenna can you check that these make sense to you. (&Ewout can you check too)
document-structure.xml document-section-library.xml

view this post on Zulip Grahame Grieve (Nov 06 2018 at 06:47):

updates.... (@Sean McIlvenna @Ewout Kramer no comment yet...) document-bad-no-sections.xml document-section-library.xml document-good.xml document-structure.xml document-bad-bad-sections.xml

view this post on Zulip Grahame Grieve (Nov 06 2018 at 20:28):

ok well committed the test, and the validator now passes.

view this post on Zulip Grahame Grieve (Nov 06 2018 at 20:47):

now that I go to write up the changes, I realise that there's a problem. GF#13973 says

This funcitionality can be realized using the (as yet undocumented) functionality that type.profile can refer to a set of constraints within a StructureDefinition, by appending a # and the id of the element that contains the constraints

well, that's what I did. But this runs into the same problem we had with Questionnaire.item.definition - you can't add #[element id] and change this to refer to an element definition instead of a structure definition. In questionnaire, we left the definition as a uri, but that's not an option here. I'm going to add an extension for this, and update the tests to use the extension.

@Lloyd McKenzie @Josh Mandel @Ewout Kramer @Rick Geimer (FHIR-I co-chairs)

view this post on Zulip Lloyd McKenzie (Nov 06 2018 at 21:25):

Best we can do at the moment I guess

view this post on Zulip Grahame Grieve (Nov 07 2018 at 03:28):

ok all committed.

view this post on Zulip Ewout Kramer (Nov 19 2018 at 14:30):

you can't add #[element id] and change this to refer to an element definition instead of a structure definition

Why is that a problem exactly? I am not familiar with the discussion around Questionnaire.item.definition. I can see you are switching from a StructureDefinition to an ElementDefinition, but where does that cause problems?

view this post on Zulip Grahame Grieve (Nov 19 2018 at 20:20):

mainly in the definition


Last updated: Apr 12 2022 at 19:14 UTC