Clarify purpose of page

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Highest
    • US SDOH Clinical Care (FHIR)
    • 0.1.0 [deprecated]
    • Patient Care
    • Support for Multiple Domains [deprecated]
    • Hide

      Will add clarification on the approach that this IG is using to incorporate code systems and value sets from the Gravity Project terminology workstream.  Updates will be made to accommodate an observation resource that is not derived from the survey/assessment and the inclusion of SNOMED-CT to describe goals.  In addition, we will describe the use of the supplemental guide as an interim solution until the additional capability to use value set metadata is added to FHIRPath and can be used to select a value set specific to an instance of a resource (based, in general, on the value in .category)

      Show
      Will add clarification on the approach that this IG is using to incorporate code systems and value sets from the Gravity Project terminology workstream.  Updates will be made to accommodate an observation resource that is not derived from the survey/assessment and the inclusion of SNOMED-CT to describe goals.  In addition, we will describe the use of the supplemental guide as an interim solution until the additional capability to use value set metadata is added to FHIRPath and can be used to select a value set specific to an instance of a resource (based, in general, on the value in .category)
    • Bob Dieterle / Jay Lyle : 7-0-3
    • Clarification
    • Non-substantive

      In reading the page as it statnds, it wasn't terribly clear what it was trying to accomplish. There needs to be language that makes clear to implementers what the page is doing and why they should care (when it's not immediately obvious from the page content, which in this case, it wasn't.)

      Proposed Wording:

      Not all of the terminologies to be used for this implementation guide are yet fully defined and nailed down. This section describes the planned approach to terminology for some of the key concepts represented in the IG to provide guidance and set expectations for future releases of this specification.

      (Comment 92 - imported by: Robert Dieterle)

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: