FHIR Chat · Clinical Impression - Problem, Investigations, Findings · implementers

Stream: implementers

Topic: Clinical Impression - Problem, Investigations, Findings


view this post on Zulip Binu DGIT (Dec 08 2016 at 08:04):

Why there is no option with clinical impression to keep text for Problem, Investigations, findings and Plan? Right now all are given as references whereas many time the initial writing will be always as simple text data.
Is there any profile available which match with this requirement?

view this post on Zulip Grahame Grieve (Dec 08 2016 at 11:44):

if you just have text, that's ClinicalImpression.summary

view this post on Zulip Binu DGIT (Dec 11 2016 at 08:30):

It is difficult to separate out individual items problems, Investigations, finding etc. from a single ClinicalImpression.summary text. Need to identify attributes individually but data type to be maintained as String

view this post on Zulip Lloyd McKenzie (Dec 11 2016 at 16:00):

When you have a Reference data type, you have a Reference.display you could use to capture text. (I wouldn't recommend using it to capture paragraphs worth of text, but a short sentence would be fine). If you want more than that, then use the narrative of the referenced resource

view this post on Zulip Lloyd McKenzie (Dec 11 2016 at 16:00):

(which could be contained)

view this post on Zulip Richard Townley-O'Neill (Dec 14 2016 at 00:21):

As I see it, Reference.display is for identifying the reference, not for summarising it. See http://build.fhir.org/references-definitions.html#Reference.display

  • Definition: Plain text narrative that identifies the resource in addition to the resource reference.
  • Comments: This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.

view this post on Zulip Grahame Grieve (Dec 14 2016 at 07:02):

fully describe != summarise.


Last updated: Apr 12 2022 at 19:14 UTC