Change terminology binding strength for Condition.verificationStatus from "required" to "example"

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Care
    • STU
    • Condition
    • 9.2.3 and 9.2.3.1
    • Hide

      New motion is to find tracker (i.e. change binding strength to example) to be NOT persuasive was done on Oct 2, 2018 with a vote: Danielle/Emma: 18-0-0

      Show
      New motion is to find tracker (i.e. change binding strength to example) to be NOT persuasive was done on Oct 2, 2018 with a vote: Danielle/Emma: 18-0-0
    • Danielle/Emma: 18-0-0
    • Correction

      Implementers should have the choice to specify the "verification status" using a value set based on standard clinical terminology (e.g. SNOMED CT). SNOMED CT could be used to clarify "differential"; it could refer to either 263735002-"Differential (qualifier value)" or to 47965005 -"Differential diagnosis (contextual qualifier) (qualifier value).

      Therefore we need to change the terminology binding strength for Condition.verificationStatus from "* required " to *"example". The majority of coded data elements in more mature resources (e.g. Observation) use "example" terminology bindings to allow meaningful profiling.

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            greg_staudenmaier, Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: