GAO Ballot Package

This page is part of the FHIR Specification (v1.1.0: STU 3 Ballot 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

This is a frozen snapshot of the FHIR specification created for the purpose of balloting the GAO implementation Guide. It includes draft changes that may be part of the future DSTU 2.1 release but further change is expected. Readers should focus solely on the GAO implementation content, and FHIR DSTU 2 for other purposes.

Detectedissue-example-dup.json

Raw JSON (canonical form)

Diagnostic order is placed when a recent image of the same body site already exists

{
  "resourceType": "DetectedIssue",
  "id": "duplicate",
  "text": {
    "status": "generated",
    "div": "<div>\n      <p>Similar test was performed within the past 14 days</p>\n      <ul>\n        <li>\n          <a href=\"DiagnosticOrder/id\">Chest CT - ordered May 8, 2013 by Dr. Adam Careful</a>\n        </li>\n        <li>\n          <a href=\"ImagingStudy/example\">Image 1 from Series 3: CT Images on Patient MINT (MINT1234) taken at 1-Jan 2011 01:20 AM</a>\n        </li>\n      </ul>\n    </div>"
  },
  "category": {
    "fhir_comments": [
      "  test 1  "
    ],
    "coding": [
      {
        "system": "http://hl7.org/fhir/v3/ActCode",
        "code": "DUPTHPY",
        "display": "Duplicate Therapy Alert"
      }
    ]
  },
  "implicated": [
    {
      "reference": "DiagnosticOrder/di",
      "display": "Chest CT - ordered May 8, 2013 by Dr. Adam Careful"
    },
    {
      "fhir_comments": [
        "  test 2  "
      ],
      "reference": "ImagingStudy/example",
      "display": "Image 1 from Series 3: CT Images on Patient MINT (MINT1234) taken at 1-Jan 2011 01:20 AM"
    }
  ],
  "detail": "Similar test was performed within the past 14 days",
  "date": "2013-05-08",
  "author": {
    "reference": "Device/dsp"
  }
}

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.