FHIR Chat · PrimaryCancerCondition · implementers

Stream: implementers

Topic: PrimaryCancerCondition


view this post on Zulip Alex Goel (Aug 19 2020 at 16:22):

For the Integrating Cancer Reporting use case in the September Virtual Connectathon https://confluence.hl7.org/display/FHIR/Integrating+Cancer+Reporting

We were looking at the PrimaryCancerCondition (http://hl7.org/fhir/us/mcode/StructureDefinition-mcode-primary-cancer-condition.html) and CancerDiseaseStatus (http://hl7.org/fhir/us/mcode/StructureDefinition-mcode-cancer-disease-status.html) profiles and were struggling with a few values.

Does anyone have an idea how to use PrimaryCancerCondition to represent an active an active prostate cancer?

Here’s the example we were trying to build
Example Patient:
assertedDate = YYYY-MM-DD
clinicalStatus = active
bodySite = Prostate (side note: Why is subject in bodySite?)
stage = an AJCC value

We ran into 2 questions:
How do we represent a patient with a progressive disease using CancerDiseaseStatus

How would we store data on the most recent PrimaryCancerCondition and CancerDiseaseStatus? For example if we wanted to be able to find all active Prostate Cancer patients in a list for MIPS measures, where the patients condition is stable (not progressive)?

@May Terry can you or your colleagues help us out?

view this post on Zulip May Terry (Aug 19 2020 at 16:57):

@Alex Goel - thanks for the great questions. Lots to unpack though... :-)

Does anyone have an idea how to use PrimaryCancerCondition to represent an active an active prostate cancer?
we have an mCODE example which shows how one represents an active cancer in the IG, but for lung cancer: http://hl7.org/fhir/us/mcode/Condition-mCODEPrimaryCancerConditionExample01.html

Why is subject in bodySite?
You might be reading it wrong. subject is outside of body site. if you collapse Condition.bodySite, you'll see that subject resides outside of that structure.

How do we represent a patient with a progressive disease using CancerDiseaseStatus?
This is an ongoing discussion. Currently, the scope of CancerDiseaseStatus was related to an overall assessment of the patient. "progression" was considered more of a status specific to a response to treatment and not included in the mCODE 1.0 STU1 release. We should be considering an explicit way to specify "progression" or "remission" for a possible STU2 release. While it's not optimal by far (and clinically ambiguous if one considers wholistic patient care), I suppose you can loosely infer cancer progression as "Patient's condition worsened" in the mcode-condition-status-trend-vs value set until there is a better approach. (cc: Mark Kramer to weigh in if needed).

How would we store data on the most recent PrimaryCancerCondition and CancerDiseaseStatus? For example if we wanted to be able to find all active Prostate Cancer patients in a list for MIPS measures, where the patients condition is stable (not progressive)?
It's possible today in mCODE to represent PrimaryCancerCondition for active prostate cancer patients and a "stable" CancerDiseaseStatus. I think one should be able to create a FHIR REST call with out-of-box search parameters that should be able to return your cohort. Let me see if I or one of our mCODE shr-spec team members can quickly prototype this on our mCODE Logicahealth sandbox instance and show how it can be done.

view this post on Zulip Alex Goel (Aug 19 2020 at 17:43):

Thanks May! This is really helpful to try out making the Prostate sample. I might ask if we can just use the existing Lung example.

And my bad about reading subject wrong!

view this post on Zulip May Terry (Aug 19 2020 at 19:20):

@Alex Goel You can definitely use the existing Lung example currently in the IG. You can inspect the bundle for that patient in our mCODE Logicahealth instance: https://api.logicahealth.org/mCODEv1/open/Patient/16831/$everything

view this post on Zulip May Terry (Aug 19 2020 at 19:22):

We'll still create the prostate cancer example and provide some guidance on the REST call. I have a couple of folks on our team working on this and should have it in the next day or so. They'll post it when it's done.

view this post on Zulip Caroline Potteiger (Aug 21 2020 at 19:00):

@Alex Goel Hi Alex! We uploaded the prostate cancer example to the mCODE Logicahealth instance. These are the ids: PrimaryCancerCondition =17303, CancerPatient=17302, CancerDiseaseStatus=17304

view this post on Zulip Caroline Potteiger (Aug 21 2020 at 19:02):

This is the search to find the Condition resources + the associated Patient resources in one request: https://api.logicahealth.org/mCODEv1/open/Condition?_profile=http://hl7.org/fhir/us/mcode/StructureDefinition/mcode-primary-cancer-condition&clinical-status=http:%2F%2Fterminology.hl7.org%2FCodeSystem%2Fcondition-clinical%7Cactive&code=http:%2F%2Fsnomed.info%2Fsct%7C93974005&_include=Condition:subject

view this post on Zulip Caroline Potteiger (Aug 21 2020 at 19:03):

We're still looking into how to include a CancerDiseaseStatus that is stable in the search, but we wanted to share what we have now.

view this post on Zulip Caroline Potteiger (Aug 31 2020 at 12:26):

And a search for CancerDiseaseStatus that is stable - https://api.logicahealth.org/mCODEv1/open/Observation?combo-value-concept=http://snomed.info/sct|359746009


Last updated: Apr 12 2022 at 19:14 UTC