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

Change Smoking History profile to allow effectivePeriod instead of effectiveDateTime

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Core (FHIR)
    • current
    • Cross-Group Projects
    • US Core Smoking Status Observation Profile
    • Hide
      1. √Retain US Core Smoking Status 
      2. Add “tobacco use”, “pack/day”, “packyear” LOINC to Observation.code valueset ( extensible)
      3. bind to an improved Tobacco Use value set 
      4. Remove max binding to all of SNOMED CT
      5. Loosen effective time binding  - add a period
      Show
      √Retain US Core Smoking Status   Add “tobacco use”, “pack/day”, “packyear” LOINC to Observation.code valueset ( extensible) bind to an improved Tobacco Use value set  Remove max binding to all of SNOMED CT Loosen effective time binding  - add a period
    • Brett Marquard/Cooper Thompson: 40-0-0
    • Enhancement
    • Compatible, substantive

    Description

      In US Core 3.1.1, the SmokingStatus profile was silent on what data type to use for Observation.effective.  We chose to use Observation.effectivePeriod, where we communicate the start and end date for a patient's smoking history (in the case they have stopped smoking).

      However, in US Core 4.0.1 SmokingStatus now has effectiveDateTime as 1..1 MS.   When we were looking to make updates to conform to US Core 4, we realized that converting from effectivePeriod to effectiveDateTime means we'd start exchanging less data, as we'd no longer be sending the end date.  

       

      I don't expect US Core's goal was to prevent us from exchanging the end date when we have it.  I propose we allow effectivePeriod as an option, probably alongside effectiveDateTime.

       

      And patch back to 4.01.

      Attachments

        Activity

          People

            Unassigned Unassigned
            cooper.thompson Cooper Thompson
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: