Stream: omop + fhir oncology
Topic: Vocabulary alignment
May Terry (Jan 18 2022 at 18:18):
Cutting and pasting into a new topic rather than in housekeeping scheduling and meeting minutes coordination...
@Davera Gabriel said:
Hello @May Terry Is there a link to the mapping work you have underway. Specifically, we in the Terminologies subgroup are interested in the concepts and Value Sets you are finding a challenge to accommodate*_
May Terry (Jan 18 2022 at 18:23):
I'm currently synthesizing the mCODE vocab discrepancies into patterns or types of semantic alignment issues which should be generalized, and apply to multiple IGs, not just cancer-related.
In the meantime, Vocab can address and sync-up how to handle US Core or FHIR base resource value sets? Two examples that you can start considering regardless of cancer or specific to one health domain:
- How is this group going to handle US Core race and ethnicity codes? (specific to US Core)
- Condition.clinicalStatus? (represented in the Condition base resource)
Davera Gabriel (Jan 18 2022 at 18:39):
May Terry said:
I'm currently synthesizing the mCODE vocab discrepancies into patterns or types of semantic alignment issues which should be generalized, and apply to multiple IGs, not just cancer-related.
In the meantime, Vocab can address and sync-up how to handle US Core or FHIR base resource value sets? Two examples that you can start considering regardless of cancer or specific to one health domain:
- How is this group going to handle US Core race and ethnicity codes? (specific to US Core)
- Condition.clinicalStatus? (represented in the Condition base resource)
Something you should do @May Terry is log JIRA tickets for each issue / class of issues. In this way your mission to address each globally and not just in the context of the OMOP + FHIR oncology use case will be achieved.
May Terry (Jan 18 2022 at 19:17):
Log tickets against which HL7 specification or project on jira.hl7.org?
Davera Gabriel (Jan 18 2022 at 19:39):
you are pointing to a good gap... does your subgroup project have a PSS that's been approved by the TSC?
May Terry (Jan 18 2022 at 20:16):
mCODE has a PSS and 2 STU publications under that PSS, however these issues I just mentioned are not specific to mCODE. Subsequently, it makes no sense to put it there because it's not an issue with mCODE but with the HL7-OHDSI partnership in aligning FHIR and OMOP.
A JIRA project of vocabulary issues related to the HL7-OHDSI partnership should be created by the FHIR-OMOP Vocab subgroup - especially if they are to be triaging, synthesizing, and managing issues from multiple FHIR-OMOP use cases. This is similar to what HTA does, but you don't want to put it there because this is likely out of scope to what their charter is.
At minimum, it might make sense for you to create a JIRA project as well as a process of how to submit and track issues. Then advertise it to the rest of the FHIR-OMOP use case teams.
Once this is done then, I can add it there.
Davera Gabriel (Jan 19 2022 at 14:40):
May Terry said:
mCODE has a PSS and 2 STU publications under that PSS, however these issues I just mentioned are not specific to mCODE. Subsequently, it makes no sense to put it there because it's not an issue with mCODE but with the HL7-OHDSI partnership in aligning FHIR and OMOP.
A JIRA project of vocabulary issues related to the HL7-OHDSI partnership should be created by the FHIR-OMOP Vocab subgroup - especially if they are to be triaging, synthesizing, and managing issues from multiple FHIR-OMOP use cases. This is similar to what HTA does, but you don't want to put it there because this is likely out of scope to what their charter is.
At minimum, it might make sense for you to create a JIRA project as well as a process of how to submit and track issues. Then advertise it to the rest of the FHIR-OMOP use case teams.
Once this is done then, I can add it there.
I quite agree with your assertions @May Terry ... I am doing some follow-up this week. More soon
Last updated: Apr 12 2022 at 19:14 UTC
