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

Additional topic for known issues and request for additional guidance on timestamps/transforming of time elements

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • US C-CDA on FHIR (FHIR)
    • 1.2.0-ballot
    • Cross-Group Projects
    • STU
    • Known Issues
    • Hide

      If you don't have structured data input, you don't know what to put in the structured data output. That element is null.

      Wrt inferring time from Concern, that time is intended to be the "concern" time, not the clinically relevant time.

      Not persuasive.

      Show
      If you don't have structured data input, you don't know what to put in the structured data output. That element is null. Wrt inferring time from Concern, that time is intended to be the "concern" time, not the clinically relevant time. Not persuasive.
    • Jay Lyle/Michelle Currie: 10-0-0

    Description

      In C-CDAs in the wild there are often missing or nulled time stamps on/in every of the PAMI+ domains.

      Guidance on how to handle when timing/timestamps is/are missing or as is the most common case missing (or nulled) in the entries , but present in the section text. This is particularly common with medications where the only detail is in the Sigs (text reference).

       

      Another place where timestamps are commonly nulled is on Problem entries - where the only time present is on the concerns act. The Problem mapping in this IG does not take into consideration the Concern act. The same is true of allergy and allergy concern act timing.

      Missing time heuristic should be added per each PAMI+

      Attachments

        Activity

          People

            Unassigned Unassigned
            GDolin Gay Dolin
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: