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

Activity Group should not have a fixed code

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • US Physical Activity (FHIR)
    • 1.0.0-ballot [deprecated]
    • Patient Care
    • STU
    • PA Observation - Supporting, Activity Group
    • Hide

      Requiring the use of our code does not prevent the use of additional codes.  It's possible to send multiple panel codes so long as the set of Observations grouped complies with all panels declared.  Our panel simply requires that at least one of our 'activity' observations are present and that when you're sending data that maps to one of our observations, you comply with our profile.  You're free to send other observations.  So if a system wishes to capture more elements and comply with a more complex panel as well as ours, they can.  They're also free to send separate grouping observations if that makes sense.

      We will add documentation highlighting this ability to send multiple codings and/or have more than one 'grouping' observation with some examples of how and where this might be done.

      We believe there's significant value in having a single 'grouping' code that all implementers of the IG can count on being used to find collections of observations about a single exercise 'episode' and therefore wish to retain our current standard code (which will likely eventually be migrated to LOINC too).

      Show
      Requiring the use of our code does not prevent the use of additional codes.  It's possible to send multiple panel codes so long as the set of Observations grouped complies with all panels declared.  Our panel simply requires that at least one of our 'activity' observations are present and that when you're sending data that maps to one of our observations, you comply with our profile.  You're free to send other observations.  So if a system wishes to capture more elements and comply with a more complex panel as well as ours, they can.  They're also free to send separate grouping observations if that makes sense. We will add documentation highlighting this ability to send multiple codings and/or have more than one 'grouping' observation with some examples of how and where this might be done. We believe there's significant value in having a single 'grouping' code that all implementers of the IG can count on being used to find collections of observations about a single exercise 'episode' and therefore wish to retain our current standard code (which will likely eventually be migrated to LOINC too).
    • Jay Lyle/Rob Eastwood : 6-0-1
    • Clarification
    • Non-substantive
    • 1.0.0

    Description

      Requiring a specific code for Activity Groups is a not a good idea. It prevents the group from being identified as a specific type of group. Different types of panels in LOINC have different codes. Even if this is not as structured as a LOINC panel, and only a grouping, the user should have the ability to specify what is being grouped by using a code.  It would also be useful for the recipient of the information when they are trying to figure out what type of grouping it is. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            Mark_Kramer Mark Kramer
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: