Private beta preparation

Medical documentation that is easier to create, verify, and share.

MDSW brings patient records, clinical notes, doctor verification, secure collaboration, insurance context, and care-team communication into one connected platform.

Join the early-access list Explore the platform

Patient-centered Records organized around the person receiving care.

Verification-ready Doctor review, OTP, QR, and accountable workflows.

Built for teams Patients, doctors, clinics, hospitals, and staff.

MDSW patient dashboard showing notes, doctors, hospitals, and account activity metrics

✓

Note verifiedClinical review recorded

🔒

Controlled accessRole and relationship based

Clinical Notes Doctor Verification Patient Access Clinic Workflows Insurance Context Secure Messaging

Understand your medical records

From medical terminology to language you can understand.

Medical notes are written for clinical documentation. MDSW helps patients understand what those notes mean.

BEFORE Original Doctor's Note

Clinical terminology

Chief Complaint (CC)

DOE, intermittent CP, and worsening BLE edema x2 weeks.

Assessment

1. Acute on chronic HFrEF with mild volume overload.

2. Persistent AF with adequate ventricular response.

3. Poorly controlled T2DM.

4. Stage 3 CKD, stable baseline renal function.

5. Essential HTN, suboptimal control.

Clinical abbreviations Medical terminology Dense documentation

→ Simplified

✓

AFTER MDSW Simple Medical Note

Plain language

Why you were seen

You have been getting more short of breath, sometimes having chest pain, and having increased swelling in both legs for about two weeks.

What your doctor found

Your heart failure symptoms have gotten somewhat worse and you are retaining extra fluid.
You have an ongoing irregular heartbeat called atrial fibrillation.
Your diabetes is not well controlled.
You have stage 3 chronic kidney disease, but your kidney function is currently stable.
Your blood pressure is higher than your doctor would like.

✓ Plain English ✓ Key information ✓ Easier to understand

Example only. Simplified explanations are intended to help patients understand clinical documentation and are not a substitute for medical advice from a qualified healthcare professional.

The product

One medical workspace. Multiple care relationships.

MDSW is being built to reduce fragmented documentation and give every authorized participant a clearer view of the information, verification status, and next action that matters.

Structured medical notes

Create patient-centered notes with encounter details, diagnoses, severity, status, and supporting context.

Primary and supporting diagnoses
Draft, review, and verified states
Encounter history and accountable edits

Doctor verification

Route documentation for clinical review with clear approval, correction, and rejection workflows.

QR and OTP access

Use expiring verification links, one-time passcodes, and QR workflows to reduce manual friction.

Care-team collaboration

Connect patients, doctors, clinics, hospitals, and authorized staff without losing record context.

Insurance information

Associate policies, coverage information, plan details, and verification status with the patient record.

Operational visibility

Dashboards and activity metrics help users understand notes, provider relationships, connected facilities, diagnoses, and recent account activity.

Connected workflow

From documentation to trusted clinical record.

Each step is designed to preserve context, make responsibility visible, and keep final clinical decisions under human control.

Capture

A patient, provider, or authorized staff member creates or receives documentation.

Organize

The record is connected to the correct patient, encounter, diagnosis, clinic, and policy context.

Review

Assigned clinicians inspect the note, review changes, and request corrections when necessary.

Verify

Approval status, reviewer, time, and verification evidence are recorded in the audit trail.

Collaborate

Authorized participants can communicate and act from the same patient-centered context.

AI-assisted, not AI-autonomous.

Planned AI capabilities are intended to help summarize, organize, and flag information. Clinical decisions and record approval remain with authorized healthcare professionals.

Designed around each role

The right tools and visibility for every authorized user.

Patient workspace

Understand and manage your medical information.

View notes, connected doctors and hospitals, diagnoses, policy information, messages, and verification status in one account.

Patient-centered record timeline
Doctor and facility connections
Secure access and notifications
QR and OTP verification experiences

Recent note Follow-up consultation Doctor verified

Care team 2 connected providers Access based on relationship

Security and accountability

Designed for sensitive healthcare information.

MDSW is being engineered around layered safeguards, controlled access, auditable activity, encrypted data, and explicit verification workflows.

Compliance status

MDSW is preparing its infrastructure, policies, vendor agreements, and operational controls for production healthcare use. Final compliance claims will only be made after required legal and security reviews are complete.

Encrypted information

Encryption in transit and at rest, with additional protection planned for sensitive identity fields and secrets.

Role-based access

Permissions are scoped by role, organization, care relationship, and approved purpose.

Auditability

Important access, changes, verification actions, and administrative events are designed to be traceable.

Secure verification

Time-limited tokens, OTP, QR, and clinician approval workflows help reduce unauthorized actions.

Human clinical control

Automated tools do not replace licensed professional judgment or independently approve clinical records.

Cloud and AI security

Secure cloud infrastructure with privacy-first AI architecture.

MDSW is designed to run on a hardened Google Cloud environment with security controls intended to protect sensitive healthcare information and support HIPAA-aligned operations.

Google Cloud Run

Application services are designed to run in Google Cloud Run, providing a managed, containerized execution environment with controlled service access, identity-based permissions, and scalable infrastructure.

Cloud Armor protection

Google Cloud Armor is planned as part of the edge-security layer to help protect public-facing services from malicious traffic, application-layer attacks, and other unwanted requests.

Defense-in-depth cloud security

Security is applied across identity, networking, application access, encryption, secrets management, logging, monitoring, least-privilege permissions, and controlled administrative access.

HIPAA-focused architecture

The platform is being engineered with HIPAA requirements in mind, including appropriate access controls, auditability, encryption, data protection, vendor controls, and administrative safeguards. Formal HIPAA compliance claims will only be made after the required legal, security, and operational reviews are complete.

Zero-retention AI data design

MDSW is designed so that sensitive medical information sent for AI-assisted processing is not retained as training data or stored in a separate AI data store. AI processing should be configured for zero data retention, subject to the capabilities and contractual terms of the selected AI provider.

AI-assisted, not AI-autonomous

AI capabilities are intended to assist with summarization, organization, and information understanding. Clinical decisions, verification, and final record approval remain under authorized healthcare professional control.

Security and compliance commitment

MDSW is being designed for healthcare environments where privacy, security, and accountability are essential. Production deployment will require appropriate Google Cloud configuration, access controls, monitoring, vendor agreements, HIPAA documentation, and a signed BAA where required. This section describes the intended architecture and controls and is not, by itself, a certification or legal determination of HIPAA compliance.

Product direction

Built for today. Architected for what comes next.

Launch scope focuses on reliable documentation and verification. Later releases will expand interoperability, automation, analytics, and organization controls.

Launch foundation

Documentation and verification

Patient records, diagnoses, notes, provider relationships, secure workflows, and account activity.

Operational intelligence

Improved review prioritization, change summaries, reporting, alerts, and financial visibility.

Future

Interoperability and scale

FHIR/HL7 integrations, white-label clinic deployments, APIs, and broader enterprise administration.

Early access

Help shape a better medical documentation experience.

Join the launch list for product updates, private beta invitations, and partnership opportunities.

info@mdsaidwhat.com New York, NY

Name Email address I am interested as a... By submitting, you agree to receive launch-related communications. No medical information should be submitted through this form.