Jason Kulatunga

//TODO: replace functionality here with https://github.com/go-gorm/datatypes

Yeah, good point. We should probably skip that one. I just did a cursory search of awesome lists that were relevant, there's probably a couple that I missed.

@justinKocian if you open PR's can you link them to this issue just so we don't get any duplication? Thanks!

oh that's awesome! 😉 Thanks for doing this @cfu288 !

- https://www.healthit.gov/buzz-blog/healthit-certification/getting-ready-for-ehi-export-a-quick-guide - https://smarthealthit.org/electronic-health-information-ehi-export-api/ - https://www.oracle.com/a/ocom/docs/industries/healthcare/cerner-certified-health-it-transparency-and-disclosure.pdf -  - https://bulk-data.smarthealthit.org/?dur=0&m=10000&page=1000000&stu=4

Apologies for the delay @Eschguy I'm trying to figure out the best way to tweak the integration to use the `epic-legacy` provider, without breaking it for everyone else.

Hopefully you wont have to be patient much longer. We made a bunch of changes to the Epic provider that should be rolling out in Jan. related https://github.com/fastenhealth/fasten-sources/issues/76

@hkamran80 good callout, though I'm not sure if it means much if the international health systems don't provide patient access API endpoints. --- On a different note, I was playing...

Sweet. One "hacky" but potentially quick solution I was thinking about was just throwing CCDA input and the Aidbox FHIR output at ChatGPT, and seeing if it could generate liquid...

basically: `existing templates` + `CCDA input` = `crappy FHIR output`. How can we change the `templates` so that `new templates` + `CCDA input` = `aidbox FHIR output`