The next level will be formatting said data for instant physician consumption. We ingest data in particular visual formats specifically for each medical specialty.
Discussion
Yeah, imagine the power of the interface design if each dev can focus entirely in just one role inside the system.
https://www.are.na/a-j-lnwvmzy-t_4/check-this-interface interface ninja strikes again and disappears
Yup, I am working on a handler to take care of all the json (structured data handling). After that, I want to domain experts to take over. As I mentioned on the call, I am not in the app-building business (as you can see from my crappy interface). What I am good at is generalizing domain-specific requirements into infrastructure capability requirements. IMHO, #nostr is the only game in town where I can do both.
Filling out scutsheets ain’t rocket science…once you find a template. I used FOSS itextpdf libraries to make a pdf programmatically (https://itextpdf.com) of a medfools scutsheet (https://www.medfools.com/)
My strong recommendation: make a proof of concept app filling out this scutsheet (https://www.medfools.com/downloads/medicine.pdf) before pitching the backend to a potential buyer. Anyone in the field will understand the power instantly and intuitively.
A good deal of medicine is info management and that’s mostly database reporting.
Happy to connect dots / answer questions to help you understand the content of scutsheets