Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-36858

Provide a mechanism to reference "prior studies"

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Orders & Observations
    • DiagnosticReport
      Procedure
    • Hide

      make supportingInfo a backbone element with initial example binding using the V2  Table 0936 (https://terminology.hl7.org/3.1.0/CodeSystem-v2-0936.html) and further clarification  of those codes on the Lab call 9/2

      Show
      make supportingInfo a backbone element with initial example binding using the V2  Table 0936 ( https://terminology.hl7.org/3.1.0/CodeSystem-v2-0936.html ) and further clarification  of those codes on the Lab call 9/2
    • Lorraine Constable / Riki Merrick: 9 - 0 - 1
    • Enhancement
    • Non-compatible
    • R5

    Description

      There is no obvious way for a Procedure or DiagnosticReport to reference another relevant Procedure/DiagnosticReport. This would be helpful for referring physicians who may want to navigate from a current radiology report which discusses a mass of some size to the prior study a month ago where the mass was another size. I can envision a number of situations where a current report would want to reference a "prior," "comparison", "relevant," or "baseline" report. This is particularly useful if the patient has a large number of Procedures/reports, and it isn't immediately obvious which would be the relevant prior.

      I don't think that linking at the Observation is the correct approach (although doing that as well could be useful), since (a) the compared content is often at the level of the report, not the individual observation, and (b) some practitioners (particularly outside the institution) would only have access to the report, not the individual observations.

      I don't think that basedOn really fulfills the need here, and there isn't a standard way of flagging what the nature of the relationship is with basedOn anyhow.

      I suggest addition of a standard extension, or addition of new elements to DiagnosticReport, which allows expressing a related DiagnosticReport or Procedure, and the type of the relation (likely via a small controlled vocabulary). It isn't clear to me whether we only need to be concerned with DiagnosticReports, or whether Procedures and ServiceRequests (or other resources) can have similar relationships to other Procedure/ServiceRequests.

      Attachments

        Activity

          People

            rhausam Robert Hausam
            esilver Elliot Silver
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: