Wound up on this app development project!🚀Wound up on this app development project!🚀
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Dusko's avatar
Role-based access across patients, doctors, and pharmacists in one app is the hard part here — curious how you scoped permissions between the appointment booking and prescription views, since a pharmacist and a doctor need pretty different slices of the same booking data.
Sushil's avatar
Great question — this was one of the key architecture decisions in MediCodio.
We implemented role + resource-based access across patients, doctors, and pharmacists. Instead of duplicating data, we kept shared entities (appointments/prescriptions) and applied role-specific policy...
Saad's avatar
Filtering at the API layer instead of the client is the right call, it means a compromised client can't just widen its own query. One thing worth adding on top: audit the write side per role too, a pharmacist's dispense update and a doctor's prescription amendment should hit...
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started