search

databrickslabs / dbignite

Other
24 stars 11 forks source link

difference in schema definition between FHIR R4 and dbingite resources. #39

Closed aashish-sapkota-abacus closed 5 months ago

aashish-sapkota-abacus commented 8 months ago

As per the comparison between the FHIR R4 and dbignite schema, we have found the differences in following resources :

Composition

Encounter

MedicationStatement

Please refer to the detailed schema comparison in the attachment: FHIR vs dbignite schema comparision.xlsx

zavoraad commented 7 months ago

Hi @aashish-sapkota-abacus , can you describe what differences you are seeing and the expected values?

e.g. I see Encounter.class defined as an Array in both Spark & HL7 International schemas. Composition.identifier as an Array in both Spark & HL7 International schemas. Same with MedicationStatement.informationSource.

HL7 international referenced schema is here

zavoraad commented 5 months ago

Hi @aashish-sapkota-abacus , closing this issue given no response. If it is still an issue we can reopen and get more detail.

aashish-sapkota-abacus commented 5 months ago

Thank you Aaron,

-aashish

From: Aaron Zavora @.> Sent: Thursday, April 4, 2024 5:52 AM To: databrickslabs/dbignite @.> Cc: Aashish Sapkota -Nepal @.>; Mention @.> Subject: Re: [databrickslabs/dbignite] difference in schema definition between FHIR R4 and dbingite resources. (Issue #39)

Hi @aashish-sapkota-abacushttps://github.com/aashish-sapkota-abacus , closing this issue given no response. If it is still an issue we can reopen and get more detail.

— Reply to this email directly, view it on GitHubhttps://github.com/databrickslabs/dbignite/issues/39#issuecomment-2035831982, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BFZTJDXFXZOY4OBJ5DVHUBDY3SKV3AVCNFSM6AAAAABCWVLG42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVHAZTCOJYGI. You are receiving this because you were mentioned.Message ID: @.***>

Alert: This email is from outside of Abacus Insights. Please examine closely before clicking links or opening attachments. When in doubt, report in the #phishing slack channel

IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.