FHIR Chat · CCD to FHIR mapping · implementers

Stream: implementers

Topic: CCD to FHIR mapping


view this post on Zulip Shaleen Tripathi (Jan 11 2021 at 20:48):

(deleted)

view this post on Zulip Ilayaraja (Jun 10 2021 at 15:26):

Need help on CCDA to FHIR conversion and validation.

view this post on Zulip David Pyke (Jun 10 2021 at 15:27):

What issue are you running in to?

view this post on Zulip Lloyd McKenzie (Jun 10 2021 at 15:28):

There is a specific stream for C-CDA to FHIR - #CCDA / FHIR mapping stream, but you'll need to express the details of your issue(s)

view this post on Zulip Ilayaraja (Jun 10 2021 at 15:32):

Our requirement is, we are trying to convert the existing CCDA approach to FHIR. So I have converted the existing CCDA logic to FHIR version 4.0. Have successfully done the implementation and also validated the fhir json using validator_cli.jar.

Here with attaching the fhir json file for you reference and need to know whether our approach is correct. FHIR_debug.json

view this post on Zulip Lloyd McKenzie (Jun 11 2021 at 03:26):

If the instance is valid against the C-CDA FHIR profiles and you've visually checked that the data has all made it across, then you're probably ok. You won't likely to find someone who'll go through your instance with a fine-tooth comb to verify on volunteer time. (And they'd technically need the original C-CDA document to compare against, plus to be completely sure, you'd need a wide range of test C-CDAs to ensure your conversion process correctly handles the variability that's out there.)

view this post on Zulip Vassil Peytchev (Jun 11 2021 at 03:44):

A couple of things jumped at me - the bundle should be of type document and not collection; the resources have an id even though they don't exist on a FHIR server, and their fullUrl is a UUID.

view this post on Zulip Lloyd McKenzie (Jun 11 2021 at 03:49):

That first thing should absolutely have triggered a fail against the C-CDA on FHIR profile, which suggests that the validate was done against just the base FHIR spec, not the C-CDA on FHIR implementation guide.

view this post on Zulip Ilayaraja (Jun 11 2021 at 10:51):

@Lloyd McKenzie Kindly suggest us the steps to validate against C-CDA on FHIR implementation guide instead of base FHIR spec.

view this post on Zulip Ilayaraja (Jun 11 2021 at 10:52):

Lloyd McKenzie said:

If the instance is valid against the C-CDA FHIR profiles and you've visually checked that the data has all made it across, then you're probably ok. You won't likely to find someone who'll go through your instance with a fine-tooth comb to verify on volunteer time. (And they'd technically need the original C-CDA document to compare against, plus to be completely sure, you'd need a wide range of test C-CDAs to ensure your conversion process correctly handles the variability that's out there.)

You are absolutely correct. :smile:

view this post on Zulip Yunwei Wang (Jun 11 2021 at 14:18):

You can use https://inferno.healthit.gov/validator/ or https://fhirvalidator.org/ or FHIR Validator JAR file

view this post on Zulip Ilayaraja (Jun 11 2021 at 15:50):

@Yunwei Wang Thank you..


Last updated: Apr 12 2022 at 19:14 UTC