I was speaking to a physician friend of mine who mentioned that his colleagues sometimes have a hard time inputting the proper formatted inputs into Dr Chrono. Everyone has their own syntax or spin, capitalization may be different, or they may spell out a unit of measurement instead of insert it in shorthand. This makes any sort of data aggregation, export, or statistics that much more challenging when there is no standardization. EZChrono is the answer to this problem.
What it does
EZChrono is basically a glorified front end for Dr Chrono. But it provides a really simple and unified interface for physicians, to help ensure that everyone is on the same page and that data is put into Dr Chrono in a standardized fashion. Because the page flows in a certain direction, this also helps physician be on the same page about practices and procedures.
How I built it
Challenges I ran into
It was a bit challenging at first to get all the data I needed into the page through the different API calls. It was also difficult to try and line things up in a way that wouldn't break if an existing office wanted to use this solution but didn't already have standardized inputs. Finally, it was difficult to make state management work without a web-app-friendly framework such as React. This was an oversight on my part but it was too late to turn around once I started going down the rabbit hole.
Accomplishments that I'm proud of
I love simple solutions. And I believe this interface represents that. Without even needing a single database (since everything is driven by the Dr Chrono API), physicians can automate their day-to-day workflow while also standardizing input across the organization. The fact that there is no database means it is also already a candidate to be HIPPA-friendly.
What I learned
There is a whole lot of information that physicians need to gather for each visit. Dr Chrono is a fantastic tool for them to use, but I was getting confused with the number of inputs and outputs on each page. Long story short, physicians have a really difficult job and we should be thankful they're able to take care of us at all!
What's next for EZChrono
If people like this solution, I would migrate the frontend to React. This would make expanding on the user flow much simpler. Ideally this could be a paid product for businesses using Dr Chrono.