Add appointment table to core data model

[katieclaiborne-duet]

Is your feature request related to a problem? Please describe.
We'd like to adopt Tuva's data model, but rely heavily on appointment data as a preview of encounters and claims to come.

Describe the solution you'd like
I'd love for Tuva's core data model to include an appointment table, which could then be incorporated into downstream data marts as needed.

Describe alternatives you've considered
I suppose we could still adopt Tuva's data model as it exists today, and incorporate our own appointment data model. I'd love any guidance on that approach, if it's one you've seen others in the community take.

Additional context
I didn't see any previous discussion of this issue, but let me know if it's come up before, or if there's a reason an appointment model explicitly hasn't been included to date.

[aneiderhiser]

Hey @katieclaiborne-duet this is a great idea. We've actually seen some other folks add an appointment table on the side of Tuva. Generally speaking you can extend the Tuva data model to add any table you like -- simply build the table into your main dbt project. The Tuva data tables simply become part of your DAG.

If we added an appt table how would you want it designed? Would it mirror the appointment resource in FHIR?

[katieclaiborne-duet]

Yes, I think it'd generally follow the FHIR resource!

[aneiderhiser]

Okay @katieclaiborne-duet we are working on this -- do you have any examples of analytics you want to build on this table that you could share? We have a use case we've worked on previously but would love to understand your use case(s) more specifically.

[katieclaiborne-duet]

Exciting! Our key metrics are weekly appointment volume and no-show rate, with patient type (new vs established) as a dimension.

[aneiderhiser]

@katieclaiborne-duet if you look through the FHIR resource for appointments here, is anything critical missing for you?

We're aiming to get to this in the next couple weeks. In the meantime, not sure if you know this but it is easy to add any custom table to the data model -- just build it like any model in your dbt project.

[katieclaiborne-duet]

if you look through the FHIR resource for appointments here, is anything critical missing for you?

No, the FHIR resource content appears to cover the essentials for us!

We're aiming to get to this in the next couple weeks. In the meantime, not sure if you know this but it is easy to add any custom table to the data model -- just build it like any model in your dbt project.

Yes! Thank you for the reminder.