Stream: implementers
Topic: Contained resource narratives
Brian Postlethwaite (Apr 11 2017 at 01:48):
There is an invariant dom-1 (http://hl7.org/fhir/domainresource.html#invs) that prevents a contained resource from having narrative. Does anyone else think that this is limiting what you can have in there too much?
It means that you can't have the likes of a care plan with goals as narrative only contained references, for each of the individual goal. They would all have to be thrown into the CarePlan's narrative and therefore a UI can't present it nicely, apart from a large blob on the screen.
Brian Postlethwaite (Apr 11 2017 at 01:49):
anyone else have similar use cases?
Brian Postlethwaite (Feb 02 2018 at 00:21):
Anyone?
relevant to the Clinical Note discussions? @Michelle (Moseman) Miller
Richard Townley-O'Neill (Feb 02 2018 at 00:51):
I do not have a similar case at the moment.
But, it sounds like a problem to me.
It would be nice to have the reasons for not allowing this documented in the DomainResource resource.
Lloyd McKenzie (Feb 02 2018 at 01:48):
The contained resources can't stand alone. Therefore the important information would be expected to be in the Reference.display and the Resource.text of the containing resource. For the goal use-case, just put the narrative in the display if you want it kept separate from a discrete capture perspective.
Richard Townley-O'Neill (Feb 02 2018 at 01:50):
Reference.display sounds good to me.
Richard Townley-O'Neill (Feb 02 2018 at 01:53):
Maybe not.
Is it a problem that display is string and text is Narrative?
Akeem Leighton Foster Spencer (Feb 06 2018 at 16:30):
I notice when I render a patient's careplan's narratives, It looks like this:
A table inside a div for the text attribute in relations to the carePlan resource.
Maybe this topic should be moved to a different stream? (Or a new one).
Last updated: Apr 12 2022 at 19:14 UTC
