Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to send Diagnosis.AnatomicalLocationSite #12

Open
anthonygalba opened this issue Jan 29, 2024 · 2 comments
Open

How to send Diagnosis.AnatomicalLocationSite #12

anthonygalba opened this issue Jan 29, 2024 · 2 comments

Comments

@anthonygalba
Copy link

How do we send the Anatomical Location Site QDM attribute on the UDS+ Diagnosis resource?
I don't see any element on the resource that matches that attribute, and it's also not mentioned on the QDM to FHIR crosswalk (https://fhir.org/guides/hrsa/uds-plus/dataelements.html).

That attribute is used in the logic for the Table 6B Line 11a (CMS-125) Breast Cancer Screening quality measure when determining whether there is a diagnosis for a right or left mastectomy.
Perhaps there needs to be an extension added for anatomical location site that can send the SNOMED codes used by the quality measure?

@nbashyam
Copy link
Contributor

Anthony,

The De-identified Procedure resource has a body site, which can be used to indicate the above data element. Please let us know if this is not sufficient.
https://fhir.org/guides/hrsa/uds-plus/StructureDefinition-uds-plus-procedure.html

@anthonygalba
Copy link
Author

Yes, I see that for procedures, but CMS-125 specifically uses Anatomical Location Site on a Diagnosis template, which should be sent as a UDS+ Diagnosis resource.

Are you saying we should be sending this diagnosis data as a procedure for this one specific case? Because that is definitely diverging from US Core and would need some special handling.

I'd also like to point out the value set used in the binding on Procedure Body Site does not actually contain the two SNOMED codes used for anatomical location site by CMS-125.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants