Stream: cda to fhir
Topic: encompassingEncounter
Christopher Vitale (Jun 24 2020 at 01:18):
Hi FHIR community. We are looking for a reliable way to connect Encounters to clinical instances (e.g., procedure, condition, etc.) when converting CCD to FHIR. It seems that aligning CCD encounter clinical entry dates would not work in most cases and may lead to error. Generating a FHIR Encounter from a CCD encompassing encounter works nicely, but the resulting FHIR Encounter would lack required properties such as class and type, thus requiring a dataAbsentReason. Has anyone considered this approach? From a FHIR standpoint, does it seem reasonable? Thanks for any guidance you can give.
Lloyd McKenzie (Jun 24 2020 at 02:23):
@Brian Postlethwaite This might be a use case for reducing the number of mandatory elements in Encounter...
Keith Boone (Jun 25 2020 at 15:16):
If you are working with a CCD, you don't generally have to have an encompassingEncounter (as encounter is defined in V3), it could just be a summarization over a period of time, or it could be the CCD for a given visit. You might consider aligning based on date from encounter elements in the Encounter section when it is present. Codesystemz for FHIR Encounter type and class are Example and Extensible, so you should be able to find an appropriate code value to use to express a physician encounter that doesn't carry the essential details about setting or specialty.
Vibin_chander (Jul 17 2020 at 06:53):
Hi,
This may sound like a dumb question. Im converting the CCDA to FHIR resources, We wanted to get the problems List section data from CCDA. Im using the Condition resource for this.
What I see is not many CCDA uses the ICD.10 code to capture the problem. Sometime they use the <Translation value> where they mention the ICD codes. Many times in the value section, they have only SNOMED.
Is there a CCDA standard that enforces the EMR to provide both these codes?
Last updated: Apr 12 2022 at 19:14 UTC
