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

Event.recorded is unclear

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • Event Pattern
    • Hide

      Will add the following to the 'comments' for the 'recorded' element:

      Recorded date indicates date the data was placed in the record maintained by the performing practitioner, or of disclosure by patient or RelatedPerson, not a date of record transfer.  If the record is transferred from one system to another (in paper or electronic form), it does not create a distinct recordedDate.  In most cases, performing practitioners will record on the same date the event occurred, but sometimes there are delays.  If information is being relayed second-hand, recordedDate indicates when the system is first made aware of the data.

      RecordedDate is NOT intended to be the same as a database.createdTimestamp - that would be captured as part of resource.meta or possibly Provenance.

      It is possible for the same event to be disclosed to different systems at different times.  E.g. a patient might tell two different clinicians about a historical event at different visits.  If the disclosure is from the patient rather than record transfer from clinician A to B, the recordedDate would be the date each respective clinician put the data in their record.  If the data flowed from clinician A to B, the recorded date would remain the recordedDate as initially set in clinician A's system.

      Show
      Will add the following to the 'comments' for the 'recorded' element: Recorded date indicates date the data was placed in the record maintained by the performing practitioner, or of disclosure by patient or RelatedPerson, not a date of record transfer.  If the record is transferred from one system to another (in paper or electronic form), it does not create a distinct recordedDate.  In most cases, performing practitioners will record on the same date the event occurred, but sometimes there are delays.  If information is being relayed second-hand, recordedDate indicates when the system is first made aware of the data. RecordedDate is NOT intended to be the same as a database.createdTimestamp - that would be captured as part of resource.meta or possibly Provenance. It is possible for the same event to be disclosed to different systems at different times.  E.g. a patient might tell two different clinicians about a historical event at different visits.  If the disclosure is from the patient rather than record transfer from clinician A to B, the recordedDate would be the date each respective clinician put the data in their record.  If the data flowed from clinician A to B, the recorded date would remain the recordedDate as initially set in clinician A's system.
    • John Hatem/Jose Costa Teixeira: 4-0-0
    • Clarification
    • Non-substantive

    Description

      The definition refers to the first time recorded in "the record", but when we're dealing with data sharing, it's not clear which 'record' that means.

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: