Stream: conformance
Topic: text.div no fixed value
Maximilian Reith (Jan 08 2020 at 14:37):
Hey,
i faced the problem of transporting a fixed text in a composition.section. Using text.div was my first idea, but i can not enter it as a fixed value. Is this correct or is this a forge bug?
greetings Max
Mareike Przysucha (Jan 08 2020 at 15:01):
Hello Max,
I think that is not a bug, but correct behaviour: text.div is a xhtml, and the xhtml-text is not an attribute, as it is content, which summarizes the section.
I ask myself if constraining the text of a section to a fixed value makes sense. Could you describe your use case a little bit more, perhaps another field fits better.
Greetings Mareike
Lloyd McKenzie (Jan 08 2020 at 15:51):
Composition.section.text is not XHTML. It's markdown and it should be possible to set it to a fixed value. It should also be possible to set even DomainResource.text to a fixed value.
Oliver Egger (Jan 08 2020 at 16:42):
Composition.section.text is of type Narrative, and in Narrative the div is of type xhtml, @Lloyd McKenzie why should it be markdown?
Lloyd McKenzie (Jan 08 2020 at 16:55):
That's what I get for replying without double-checking the spec. You're right, it's XHTML. We haven't talked about how to do fixed or default values for that. Best thing to do is probably submit a change request to have us clarify. But I do think having fixed text for certain divs is a reasonable requirement. Having certain sections in a document that contain boiler-plate narrative is a pretty common practice.
Oliver Egger (Jan 08 2020 at 17:05):
thanks, :cold_sweat: i was already afraid i have to convert cda markup to markdown
Stefan Lang (Jan 08 2020 at 17:43):
Sounds reasonable to allow fixed values here for a certain set of use cases, e.g. having a certain legally required text within a FHIR document.
Also, while @Mareike Przysucha has a point in case of the XML representation, there is basically no difference between attribute and content in the JSON representation (regarding XHTML content of div).
Maximilian Reith (Jan 09 2020 at 07:09):
But I do think having fixed text for certain divs is a reasonable requirement. Having certain sections in a document that contain boiler-plate narrative is a pretty common practice.
+1 from me
@Lloyd McKenzie Who should submit the change request? Did you submit already?
Lloyd McKenzie (Jan 09 2020 at 07:45):
I have not. As the proponent of the change, I'd encourage you to do so. (One of my objectives with this community is to get as many people as possible in the practice of submitting changes - the immediate benefit is that the person with the immediate/pressing need will automatically be able to monitor the conversation as it occurs. The longer-term benefit is that the more people who feel empowered to propose changes, the more and better feedback we'll get and the more useful the resulting specification will be.)
To submit a change request, just click on the 'propose a change' link at the bottom of any page in the spec. If you run into an issue, holler :)
Maximilian Reith (Jan 09 2020 at 14:44):
OK...I will do that
Last updated: Apr 12 2022 at 19:14 UTC
