Need to differentiate between ActivityDefinition and DataElement - 2016-09 cqf #12

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Clinical Decision Support
    • ActivityDefinition
    • 14.1.2
    • Hide

      Agreed, there is overlap with the definition of DataElement, we will provide clarifying documentation around the boundaries. In particular, ActivityDefinitions are intended for a less granular expression (i.e. a Lab Order or a Medication) as opposed to a data element, which is more granular (a blood pressure, or an answer to a particular question).

      Show
      Agreed, there is overlap with the definition of DataElement, we will provide clarifying documentation around the boundaries. In particular, ActivityDefinitions are intended for a less granular expression (i.e. a Lab Order or a Medication) as opposed to a data element, which is more granular (a blood pressure, or an answer to a particular question).
    • Richard Esmond/Bryn Rhodes: 8-0-0
    • Clarification
    • Non-substantive
    • DSTU2

      Comment:

      Need to have additional description here of how this relates to and differs from DataElement. This is particularly relevant in regard to the usage in "order catalogs" or "master files", as DataElement also refers to "defining individual pieces of data that might be collected ...", which is an activitiy.

      Summary:

      Need to differentiate between ActivityDefinition and DataElement

            Assignee:
            Unassigned
            Reporter:
            chris_hills
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: