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

Bad description in mandatory element for DiagnsticReport.effective

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Core (FHIR)
    • 4.1.0
    • Cross-Group Projects
    • STU
    • US Core DiagnosticReport Profile for Laboratory Results Reporting
    • 10.107.1.1
    • Hide

      Background:

      See the commenters description:

      The Documentation attempts to provide a human readable description of the requirement in contrast to the formal definitions. The friendlier term "a time indicating when the measurement was taken" was used instead of  "clinically relevant time" which is a HL7 specific term and not widely understood.

      Reasoning:

      We agree that this term does not reflect that it is typically the time of specimen collection and will update it to reflect that and reference the HL7 FHIR term "effective" time.

      Proposed Changes:

      Change from:

      Each DiagnosticReport must have:

      1. ...
      2. ...
      3. ...
      4. ...
      5. a time indicating when the measurement was taken*
      6. ...

      *These elements have the following constraints: SHALL be present if status is ‘partial’, ‘preliminary’, ‘final’, ‘amended’, ‘corrected’ or ‘appended’.

      to:

      Each DiagnosticReport must have:

      1. ...
      2. ...
      3. ...
      4. ...
      5. the diagnostically relevant time*  (known as the "effective time" and typically the time of specimen collection)
      6. ...

      *These elements have the following constraints: SHALL be present if status is ‘partial’, ‘preliminary’, ‘final’, ‘amended’, ‘corrected’ or ‘appended’.

      Show
      Background: See the commenters description: The Documentation attempts to provide a human readable description of the requirement in contrast to the formal definitions. The friendlier term "a time indicating when the measurement was taken" was used instead of  "clinically relevant time" which is a HL7 specific term and not widely understood. Reasoning: We agree that this term does not reflect that it is typically the time of specimen collection and will update it to reflect that and reference the HL7 FHIR term "effective" time. Proposed Changes: Change from: Each DiagnosticReport must have: ... ... ... ... a time indicating when the measurement was taken* ... *These elements have the following constraints: SHALL be present if status is ‘partial’, ‘preliminary’, ‘final’, ‘amended’, ‘corrected’ or ‘appended’. to: Each DiagnosticReport must have: ... ... ... ... the diagnostically relevant time*  (known as the "effective time" and typically the time of specimen collection) ... *These elements have the following constraints: SHALL be present if status is ‘partial’, ‘preliminary’, ‘final’, ‘amended’, ‘corrected’ or ‘appended’.
    • Floyd Eisenberg/Eric Haas: 12-0-2
    • Clarification
    • Non-substantive

    Description

      Each DiagnosticReport must have:

      1. a status
      2. a category code of ‘LAB’
      3. a code (preferably a LOINC code) which tells you what is being measured
      4. a patient
      5. a time indicating when the measurement was taken*

      #5 is referring to DiagnosticReport.effective = which is defined as the clinically relevant time - so for many observations directly performed on the patient this definition is ok, but it is misleading for lab results 

       

      Proposed new wording for 5:

      the clinically relevant time (e.g. specimen collection time for lab tests)

       

      In fact we may want to revisit, if we need this in lab, because we will have the specimen collection date/time in the specimen resource that is referenced in the DiagnosticReport

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              RikiM Ulrike Merrick
              Ulrike Merrick
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: