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

Narrative and structure mis-match on abatement date

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Core (FHIR)
    • current
    • Cross-Group Projects
    • STU
    • US Core Condition Profile
    • Hide

      Background:

      The Documentation attempts to provide a human readable description of the requirement in contrast to the formal definitions. Based on the Condition.abatement[x] definition, the friendlier term "date of resolution" was used instead of "abatement date"

       

      Each Condition must support:

      1. ...
      2. ...
      3. ...
      4. a date of resolution

      Reasoning:

       We agree with the commenter that "date of resolution" may confuse some readers.

      Proposed Changes:

      Change:

       

      Each Condition must support:

      1. ...
      2. ...
      3. ...
      4. a date of resolution

      to :

      Each Condition must support:

      1. ...
      2. ...
      3. ...
      4. abatement date (in other words, date of resolution or remission)
      Show
      Background: The Documentation attempts to provide a human readable description of the requirement in contrast to the formal definitions. Based on the Condition.abatement [x] definition, the friendlier term "date of resolution" was used instead of "abatement date"   Each Condition must support: ... ... ... a date of resolution Reasoning:  We agree with the commenter that "date of resolution" may confuse some readers. Proposed Changes: Change:   Each Condition must support: ... ... ... a date of resolution to : Each Condition must support: ... ... ... abatement date (in other words, date of resolution or remission)
    • Brett Marquard/Eric Haas: 15-0-0
    • Clarification
    • Non-substantive

    Description

      The Condition profile flags abatement as MS, but the narrative section only mentions assertedDate (extension), onsetDate, and recordedDate

       

      We should either remove MS* from abatement, or add language around it in the narrative.

       

      • I have another tracker to make the date of diagnosis stuff an invariant instead of MS flags.  But either way, we should either include abatement in both narrative and structural requirements or neither.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: