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

Immunization (and others?) DateTime Mapping Guidance

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Low Low
    • US C-CDA on FHIR (FHIR)
    • 1.2.0-ballot
    • Cross-Group Projects
    • CF-immunization
    • C-CDA to FHIR Immunizations
    • Hide

      apply changes as described

      Show
      apply changes as described
    • Jay Lyle/John D'Amore: 16-0-6
    • Clarification
    • Non-substantive

    Description

      In C-CDA, there is not a clear guidance on using a single timestamp or a date range:

      SHALL contain exactly one [1..1] effectiveTime (CONF:1198-8834).

      It would be good to add a similar comment as allergies like "effectiveTime/high should not be mapped within occurrenceDateTime".

      Perhaps going even further, the fact that this could be in `effectiveTime/@value` or `effectiveTime/low/@value` should be mentioned either here or in the generic CDA <-> FHIR Time/Dates. Something like "Some CDA timestamp can be either a single point-in-time or an interval range. When mapped to a fire dateTime or instant datatype, the value should be taken from either @value or low/@value. If mapped to a FHIR period, effectiveTime/low maps to period.start and effectiveTime/high maps to period.end." 

      Attachments

        Activity

          People

            benjamin Benjamin Flessner
            benjamin Benjamin Flessner
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: