Role-aware access
Residents, fellows, attendings, coordinators, chiefs, and directors each have access appropriate to their role. Members can only see the program spaces they belong to.
Security & trust
Trust matters when clinical teams depend on the system.
Meddr is designed for residency and fellowship programs that need calm coordination, role-aware access, and careful handling of sensitive program communication.
Designed with care
Role-aware access
Directors, coordinators, chiefs, residents, fellows, faculty, and alumni have access appropriate to their role.
Encrypted in transit and at rest
Meddr uses secure transport and encrypted storage as part of a security-conscious infrastructure posture.
Not an EHR
Meddr is for program coordination only, not patient records or clinical decision support.
How Meddr is designed
Trust principles.
These are the design commitments that shape how Meddr handles access, data, and program communication.
Secure infrastructure posture
Data is encrypted in transit over TLS and encrypted at rest. Meddr is hosted on infrastructure with a security-conscious operational posture.
Clear separation of program spaces
Program workspaces are isolated. A member of one program cannot browse or access another.
Thoughtful notification design
Notifications are designed to be useful without unnecessarily surfacing sensitive content in lock-screen previews or third-party surfaces.
Audit-minded administration
Administrative actions are performed through structured controls so program coordinators and directors maintain visibility over access.
Not an EHR
Meddr is not an electronic health record, not clinical decision support, and not intended for patient records or protected health information.
Scope
What Meddr is designed to protect.
Understanding what Meddr handles, and what it does not, is important for programs evaluating it for institutional use.
Designed to handle carefully
Program coordination and community
Meddr handles the operational and community layer of a residency or fellowship program: the information that makes the program run, not clinical care information.
- Program announcements and internal communications
- Rotation schedules, block assignments, and events
- Directory information: names, PGY level, contact, and role
- Internal coordination between residents, fellows, and coordinators
- Alumni and member access managed by program administrators
Outside Meddr's scope
Meddr is not designed for patient records, protected health information (PHI), or clinical care documentation.
Meddr is a program coordination and community platform. It should not be used as a substitute for an EHR, a clinical messaging system intended for care coordination, or any system where patient safety depends on the data stored.
If your institution requires a Business Associate Agreement (BAA) for a tool to handle PHI, Meddr is not that tool. It is designed for the program operations layer, not the clinical care layer.
Not for patient records
Not for PHI
Not an EHR
Responsible use
Using Meddr appropriately.
Meddr gives program coordinators and directors the controls they need. Responsible use requires that those in charge set expectations clearly for their teams.
For program coordinators and directors
As the administrator of your program's Meddr workspace, you are responsible for who has access and how the platform is used within your program.
Set expectations early
We recommend setting explicit expectations at onboarding: Meddr is for program coordination, scheduling, announcements, and community, not clinical care discussion involving patients.
For institutional IT and compliance teams
If your institution is reviewing Meddr, we welcome direct conversation about infrastructure posture, data handling practices, and intended scope.
Administration
Who controls what.
Meddr uses a role-based access model that reflects the real structure of residency and fellowship programs.
Program Director & Program Coordinator
Full administrative access: manage the roster, invite and remove members, configure program settings, send announcements, and suspend access.
Chief Resident
Elevated access within the resident cohort: moderate spaces, post program-wide announcements with coordinator approval, and assist with scheduling tasks.
Attendings & Faculty
Access to the program feed, events, and directory. Faculty can participate in designated spaces without roster or settings controls.
Residents & Fellows
Access to their schedule, program feed, relevant announcements, directory, and spaces they belong to.
Alumni
Read-only access to the alumni directory and designated alumni spaces, configured and revocable by coordinators.
Suspended members
Suspended accounts cannot log in or view program content. Access can be reinstated by an admin when appropriate.
Security questions
Questions about security, privacy, or institutional fit?
We welcome direct conversations with program leaders, coordinators, and institutional IT or compliance teams. Reach out and we'll respond personally.