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

Need an Observation profile for strength-based rep measurements

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US Physical Activity (FHIR)
    • 1.0.0
    • Orders & Observations
    • (NA)
    • Hide

      Several concerns with doing this at this point:

      • Lots of providers are not yet ready to handle this sort of data (formal evidence suggesting this)
      • We don't have much evidence around the use of this sort of data
      • Keep it 'simple' for now to get people on board.  Look at ramping up once there's broader adoption and more demand
      • We don't necessarily have 'standardized' questions that are reliable tools for gathering this sort of data
      • Concerned about it increasing costs for software development

      However, we may want to revisit this in the future.

      We will add an open issue into the IG highlighting that this release doesn't have specific guidance around detailed strength-based training (and some of the reasons why), but are actively soliciting feedback on what the community would like to see in this space.

      We will add an issue marked as "considered for future use" for us to revisit this in the future when we can evaluate feedback from implementers and reconsider.

      We're also open to testing at connectathons.

      Show
      Several concerns with doing this at this point: Lots of providers are not yet ready to handle this sort of data (formal evidence suggesting this) We don't have much evidence around the use of this sort of data Keep it 'simple' for now to get people on board.  Look at ramping up once there's broader adoption and more demand We don't necessarily have 'standardized' questions that are reliable tools for gathering this sort of data Concerned about it increasing costs for software development However, we may want to revisit this in the future. We will add an open issue into the IG highlighting that this release doesn't have specific guidance around detailed strength-based training (and some of the reasons why), but are actively soliciting feedback on what the community would like to see in this space. We will add an issue marked as "considered for future use" for us to revisit this in the future when we can evaluate feedback from implementers and reconsider. We're also open to testing at connectathons.
    • Clarification
    • Non-substantive

    Description

      When representing strength-based exercises, there's typically a need to capture 3 things:

      • what type of exercise - e.g. lateral press (Observation.code)
      • what part of body - e.g. left leg (Observation.bodySite)
      • how much weight/resistance
      • how many reps

      The weight and reps really need to be captured as part of a single Observation because knowing reps without weight or weight without reps doesn't buy you much.

      We need to define a structure that defines how to use components to manage this and to nail down which is value and which is component, or whether we have two components.  We also need to define the standard codes for the components to be used.  Should seek OO feedback on these questions, so assigning it there first.

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: