Stream: implementers
Topic: resource text.div
Tim Berezny (Nov 17 2020 at 18:41):
What is the simplest way to build the text.div for a resource? Is there a generic script for building these, or are they generally customer per integration? Is the expectation that it would have ALL of the data in the resource, or just the parts that are of human-readable interest (e.g., show display values but not codes)
Lloyd McKenzie (Nov 17 2020 at 18:48):
It needs to be use-case and context specific. The example I usually give is that the narrative for an inpatient would be different than that of an anonymized clinical trial participant, which would be different again from that of a chicken in an agricultural veterinary system. Narrative should expose the 'relevant' information in a format that makes it easy to consume. Every system will need to determine what is 'relevant' and will likely need to involve end users in both making that determination as well as deciding how best to present it.
Lloyd McKenzie (Nov 17 2020 at 18:49):
Certainly exposing text or display values rather than codes would be appropriate for most situations - but narrative for a value set might very well choose to expose the raw codes too. It all depends :)
Grahame Grieve (Nov 17 2020 at 22:10):
There's a framework in the java reference implementation that is getting better over time (see .renderers)
Last updated: Apr 12 2022 at 19:14 UTC
