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

QA 5a: Resource references exist in both directions for Condition and ClinicalImpression

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Triaged (View Workflow)
    • Priority: Medium
    • Resolution: Unresolved
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      DSTU2
    • Work Group:
      Patient Care
    • Outstanding Negatives:
      STU
    • Related Artifact(s):
      ClinicalImpression
      Condition
    • Resolution Description:
      Hide

      Deferred and will revisit after STU3

      ClinicalImpression is not mature enough to resolve this issue. Ask MnM for an exemption on the QA checklist (re: Condition having a circular reference with ClinicalImpression)

      Add note: "A known issue exists with circular references between Condition and ClinicalImpression, which is due to the low maturity level of ClinicalImpression. The Patient Care work group intends to address this issue when ClinicalImpression is considered substantially complete and ready for implementation"

      Show
      Deferred and will revisit after STU3 ClinicalImpression is not mature enough to resolve this issue. Ask MnM for an exemption on the QA checklist (re: Condition having a circular reference with ClinicalImpression) Add note : "A known issue exists with circular references between Condition and ClinicalImpression, which is due to the low maturity level of ClinicalImpression. The Patient Care work group intends to address this issue when ClinicalImpression is considered substantially complete and ready for implementation"
    • Change Category:
      Enhancement

      Description

      Resource references exist in both directions for Condition and ClinicalImpression as follows:

      Condition.stage.assessment (to ClinicalImpression)

      ClinicalImpression.problem & ClinicalImpression.finding.item[x] (to Condition)

      Per QA 5a:

      Elements with a type of Resource Reference should be reviewed such that a given relationship shall only be represented in one resource, not both (and should generally be present on the resource that is normally created second - e.g. Procedure is usually created after Encounter, so reference would live on Procedure)

      http://wiki.hl7.org/index.php?title=DSTU_QA_Guidelines

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              michelle.m.miller Michelle Miller
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: