Stream: Death on FHIR
Topic: COD - Condition Contributing
Velan (Aug 17 2021 at 22:16):
Hi Team
In VRDR tool able to assign text value on "ContributingCondition", whereas required practices said, they were multiples consequences lines with interval set. Please let me know how to map those. Note: COD (Cause of Death can't be used for this instance since each been separate COD).
I have attached the UAT result with requirement. Let me know if any more details.
UAT requested : It should look like according to other sample, and practices....
image.png
Thanks
Velan
NYC DOHMH Team
Saul Kravitz (Aug 18 2021 at 19:39):
Hi @Velan
Can you please paste the code snippets in the text . See the help for how to get formatting help using back quotes.
or attach them? I'm having a hard time comparing the images. Also, what is UAT?
Thx
Velan (Aug 18 2021 at 19:48):
@Saul Kravitz
There is no code snippet for the pictures. "UAT" - User acceptance testing.
Real user going to use in production, they said "Causes Of Death" is not having "contributing condition" to specify.
Let me know if any.
-Velan
Saul Kravitz (Aug 18 2021 at 20:08):
Hi @Velan
Can you please provide more context? Multiple Cause-of-Death conditions are certainly allowable, ordered by the VRDR-Cause-of-Death-Pathway (mapping to COD and Interval A-J).
regards,
Saul
Karmen S. (Aug 19 2021 at 00:47):
Hello @Saul Kravitz ,
Perhaps I might be able to provide some context as I was the one inquiring about this.
As is the case with death certificate we have values matching the death certificate. The cause of death section has a Part I line item a, line item b, line item c, line item d. as well as a Part II
would it be valid to reference.
http://hl7.org/fhir/us/vrdr/StructureDefinition/VRDR-Cause-Of-Death-Condition
profile.
for PartI conditions b, c, d, and Part II
or would it be more accurate to represent these items under
http://hl7.org/fhir/us/vrdr/StructureDefinition/VRDR-Condition-Contributing-To-Death
profile.
Thanks,
Karmen
Velan (Aug 19 2021 at 14:15):
You are right, When assigning all these to VRDR.DeathRecord component, "ContributingCondition" property (member) defined as single value string. Not able to represent all Part II (Line b, c, d with interval). Also not valid to represent in COD1A, COD1B, COD1C...
Please let me know where to map these condition values b, c, d.
Thanks
Velan
Saul Kravitz (Aug 19 2021 at 21:47):
@AbdulMalik Shakir is the Author, so I'll ask him to confirm.
Hi @Velan and @Karmen S. ,
You are asking an IG question, right? Or are you asking about the VRDR .NET library?
Assuming you are asking an IG question: The Part I a-d are coded using VRDR-Cause-Of-Death-Condition instances, and their order is established using an VRDR-Cause-of-Death-Pathway instance that references them. Part II is coded using a VRDR-Condition-Contributing-To-Death. See the examples in the IG, e.g. http://build.fhir.org/ig/HL7/vrdr/List-60401545-f1e1-4a80-867f-02384ffed857.json.html .
Karmen S. (Aug 20 2021 at 13:15):
@Saul Kravitz - Yes I was asking an IG question and how we would accurately handle situations where all or parts of COD for Part I a-d should be coded and mapped correctly. thanks for clarifying
Velan (Aug 20 2021 at 18:32):
Hi @Saul Kravitz @Sarah MacAdam or anyone
Cause-of-Death-Pathway refers to the COD1A, COD1B....which are individual to define death causes. we are assigning to these values in VRDR.DeathRecord component, FHIR file is not producing output we expected
VRDR.Component still assign values to the COD1A, COD1B.....
image.png
Karmen request to show in contributing condition details for the COD1A as (LineB - interval, LineC - interval, LineD-interval) which are not part of individual CODs.
Thanks
Velan
Saul Kravitz (Aug 20 2021 at 19:08):
Hi @Velan Can you please attach snippet of code that uses the VRDR .NET library functions that you think indicates that it isn't functioning correctly? and the resulting "unexpected" output? A snippet of code/JSON is worth a thousand words.
Last updated: Apr 12 2022 at 19:14 UTC
