Thanks for providing your expertise, really great article. You mentioned that there are other creative solutions applications that solve scheduling that don't involve APIs/Data standards. Can you please elaborate on what these are? Also really curious if you can please recommend other people or sources who are writing about this topic. Am keen to learn!
", the dominant (and still existing) method to validate a patient’s identity for Epic’s MyChart is to mail a letter with a passcode to a patient’s known address. "
This isn't true anymore. Many (most?) MyCharts are using Experian to allow new patients to create accounts.
You mention the Slot resource for Epic, but that's only a Read. They're actually using an alternate availability pattern (the Argonaut STU3 Appointment $find)
Thanks for providing your expertise, really great article. You mentioned that there are other creative solutions applications that solve scheduling that don't involve APIs/Data standards. Can you please elaborate on what these are? Also really curious if you can please recommend other people or sources who are writing about this topic. Am keen to learn!
Nice write-up. Couple of minor nitpicky things
", the dominant (and still existing) method to validate a patient’s identity for Epic’s MyChart is to mail a letter with a passcode to a patient’s known address. "
This isn't true anymore. Many (most?) MyCharts are using Experian to allow new patients to create accounts.
You mention the Slot resource for Epic, but that's only a Read. They're actually using an alternate availability pattern (the Argonaut STU3 Appointment $find)