FHIR Chat · Composition Section Section · IG creation

Stream: IG creation

Topic: Composition Section Section


view this post on Zulip AbdulMalik Shakir (Oct 21 2021 at 00:29):

Does anyone have a functioning example of a composition in which a composition.section includes a sub-section (i.e., composition.section.section? How are elements and entries of the subsection specified in the structure definition?

view this post on Zulip Jean Duteau (Oct 21 2021 at 05:26):

Do you mean a profile that includes sub-sections? Or an actual instance example? I have both: Example instance - Composition-SampleSPLDocument.json Profile - http://build.fhir.org/ig/HL7/fhir-spl/branches/main/StructureDefinition-ProductSubmissionDocument.html

view this post on Zulip AbdulMalik Shakir (Oct 23 2021 at 18:22):

Thanks @Jean Duteau is it not possible to place constraints on the subsections allowed in a section. At first, I wondered how the elements of the subsection were exposed in a profile structure definition. Looking at your example I see that the elements of the subsection are all of the elements of section, but I don't see how those elements are contained. Am I missing something?

view this post on Zulip Grahame Grieve (Oct 23 2021 at 18:39):

it is possible - you just keep walking into the sub-section structure

view this post on Zulip Lloyd McKenzie (Oct 23 2021 at 19:50):

You'll need to define slicing within a slice. I.e. you slice the base section. Then, within that, you'll slice the sub-section.

view this post on Zulip Jean Duteau (Oct 24 2021 at 04:55):

I just added some constraints on the sub-section in one of my section slices and it looks like this:

      {
        "id": "Composition.section:OtherSections.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:OtherSections.entry",
        "path": "Composition.section.entry",
        "max": "0"
      },
      {
        "id": "Composition.section:OtherSections.section",
        "path": "Composition.section.section",
        "type": [
          {
            "code": "BackboneElement"
          }
        ]
      },
      {
        "id": "Composition.section:OtherSections.section.text",
        "path": "Composition.section.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:OtherSections.section.entry",
        "path": "Composition.section.section.entry",
        "min": 1,
        "max": "1"
      }

view this post on Zulip AbdulMalik Shakir (Oct 25 2021 at 03:56):

Thanks all. I see how to do this manually, I guest that the limitation I was seeing was in TOF only. @Rick Geimer ?

view this post on Zulip Saul Kravitz (Oct 26 2021 at 05:01):

Hi @AbdulMalik Shakir , don't you want do just slice sections by title, and slice by profile within a section with a given title, rather than have a hierarchy of sections?
Something like this (two sections, and only one profile defined per section just as an illustration) -- http://build.fhir.org/ig/saulakravitz/vrdr/branches/FSHversion/StructureDefinition-VRDR-Death-Certificate.html

view this post on Zulip Lloyd McKenzie (Oct 26 2021 at 13:21):

Title is a human-readable value and is totally unconstrained. Slicing on it is generally not a good idea. (Any change to capitalization, spacing, spelling, etc. will cause the slicing rules to not work). Much better to slice by section.code which is computable and can be constrained.


Last updated: Apr 12 2022 at 19:14 UTC