Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
FHIR Core (FHIR)
-
R5
-
Patient Care
-
Condition
-
-
Rob Hausam / Stephen Chu : 5-0-0
-
Enhancement
-
Non-compatible
-
R5
Description
Review Condition.recordedDate and recorder RIM mappings given
FHIR-27808Clarification is needed on definition and use of RecordedDate - Jira (hl7.org)FHIR-34392Condition.recordedDate rationale - Jira (hl7.org)FHIR-34394Condition recordedDate (first) and recorder (last) definitions are not aligned - Jira (hl7.org)- 2020 Sept WGM Patient Care Agenda and Minutes - Patient Care - Confluence (hl7.org)
- David: FHIR Condition.recorder element should not be populated for Condition instances derived from C-CDA documents
- Lisa: I thought we had a proposal to work through both an option to offer mapping from C-CDA to FHIR Condition.recorder (and the similar FHIR Allergy-Intollerance.recorder) WHILE STILL RESPECTING the prior guidance given by Patient Care about not mapping authors associated with the nested observation in the Problem Concern or Allergy Concern clinical statement patterns. I thought we agreed to provide guidance on the use in C-CDA of a single Provenance Author on the primary act of these Concern clinical statement patterns to hold the recorder for the Condition or Allergy-Intolerance respectively. I thought we agreed to add a JIRA ticket to recommend adding a [0..1] Conformance statement saying you MAY include a Provenance Author template on the primary Concern act to represent the actual recorder
Attachments
Issue Links
- relates to
-
FHIR-39602 Condition.participant is an anti-pattern
- Triaged