OHDSI Home | Forums | Wiki | Github

Mapping FHIR CareTeam Resource to OMOP

CDM Builders
#1

Hi all,

Our team is currently working on mapping the FHIR Resource CareTeam to the OMOP CDM. The CareTeam resource encompasses all individuals, teams, and organizations involved in coordinating and delivering patient care. It may consist of members specific to a particular care plan, episode, or encounter. An example can be found here: CareTeam Example

I am seeking guidance on the appropriate OMOP table for this mapping. It seems that the care team concept aligns with the observation domain, and I found a relevant term here: Care Team Concept.

Would this concept be appropriately mapped to the Observation table in OMOP? Any insights or recommendations on this mapping would be greatly appreciated.

#2

Hello @thanapna and welcome to OHDSI!

What are you trying to achieve with mapping “Care Team” to the OMOP CDM? What research question are you trying to answer?

Have you reached out to the FHIR to OMOP WG?

#3

Hello @MPhilofsky,

Thank you for the warm welcome!

I don’t have a specific research question at this time; I’m primarily interested in understanding how we can handle incoming data from the CareTeam resource to ensure that we preserve it effectively within the OMOP CDM.

Additionally, I haven’t reached out to the FHIR to OMOP Working Group yet, but I appreciate the suggestion.

Thank you.

#4

Hello @thanapna,

I am not a FHIR expert, but looking at example you link above highlights the difference between FHIR’s purpose and the OMOP CDM’s purpose. FHIR transmits information for patient care. The OMOP CDM houses data to do observational, person centered research. OMOP is built upon use cases and research questions. The OMOP CDM doesn’t store data to have just in case it might be needed. And the use for these data is patient care, not research. So, I wouldn’t ETL them to OMOP without a use case. ETL is a lot of work, only bring in the data you are going to use.

BUT if you want to do it anyway, then I would put the providers with their specialty in the Provider table. Then add an Observation record with the standard concept you link above.

1 Like
t