91 answers covering the whole platform — booking a consultation, medical documents, verification, payments, privacy, and the clinician side of the app.
What the platform is, who it is for, and how the apps fit together.
Medee is a holistic healthcare platform that connects patients with licensed clinicians through a fully digital care journey — from the first consultation request through diagnosis, prescriptions, lab orders, and lifelong records management. It is built for the Philippine market.
You open the Medee app, describe your symptoms (for yourself or a dependent), pay or redeem a coupon, and book a consultation. A clinician receives your request, chats and video-calls with you, and can issue prescriptions, lab requests, lab results, assessments, and certificates. Everything issued is verified, stored permanently on your record, and shareable through a secure link or QR code.
Medee (the patient app) for the general public on iOS, Android, and web; Medee Clinic (the provider app) for doctors, nurses, and other clinicians on iOS, Android, and web; and the Medee website, which is the public face of the platform and the place where shared medical documents can be verified without installing anything.
Yes. Both the patient app and the clinician app run on iOS, Android, and the web from a single codebase, so your account and records are the same wherever you sign in.
Requesting a consultation, being matched to a clinician, and closing the case.
A guided wizard walks you through five steps: who the care is for (you or a dependent), your chief complaint and how severe it is, payment (a saved method, a new one, or a coupon code), your preferred consultation date and time, and a final review before you confirm.
Payment comes before booking on purpose. A coupon issued by a specific clinician locks your request to that clinician, so the booking step can then show you that clinician's real availability instead of a generic calendar.
Requests reach clinicians through a staggered matching queue. Your request is first offered to one on-duty clinician; the pool of clinicians who can see it widens every 30 seconds, and after three minutes it becomes visible to all clinicians. More urgent requests are sorted higher in the clinician's queue.
Rather than going stale, an unhandled request pauses itself. You are told it has paused and can choose to keep searching, which puts it straight back into the queue. You can also opt out of auto-pausing.
Pending while you wait, paused if nobody has picked it up, accepted once a clinician takes it, cancelled if you withdraw it, resumed if you send a paused request back to the queue, and completed once the clinician closes the case.
When a clinician accepts your request it becomes a medical case — the central record that ties together your clinician, your conversation (chat and calls), any collaborating clinicians or office staff, every document issued, and the reason the case was eventually closed.
Yes. After a case is completed you can leave a star rating with sentiment chips describing what went well or badly.
Every document issued during the case is aggregated into one consolidated patient record entry for that episode of care, which you can browse any time in the patient app.
Requesting care for a child, an elderly parent, or a ward.
Yes. Every care request carries a care subject — the person the care is actually for. By default that is you, but you can choose a registered dependent such as a child, an elderly parent, or a ward.
You do. Documents, triage, and analytics all describe the dependent, while ownership, payment, and access stay with you as the guardian.
Register them under your account with their name, birthdate, sex, and relationship to you. You can hold up to 100 dependents, and the booking wizard then offers a subject picker at the first step.
Yes. The clinician app labels such cases with the relationship and a badge naming the person being cared for, so the clinician always knows who they are treating.
Prescriptions, lab requests, lab results, assessments, and certificates.
Five types: prescriptions, lab requests, lab results, medical assessments, and medical certificates. All of them are issued from inside the case and land on your record.
Medicines with structured dosing — dose, frequency, timings, duration, quantity, and route, each of them optional — or a written dose in the clinician's own words when structured fields do not fit. Every prescription carries the clinician's digital signature.
The clinician orders the tests, sets an urgency, and adds notes. Tests are grouped up to four labs per group, with one printed page per group, so you can hand the right page to the right laboratory.
Fit-for-work, sick leave, attendance, disability, or a custom certificate, with the date range it covers and the reason for it — ready to show an employer or a school.
The clinician's diagnosis (with ICD codes), treatment plan, and recommendations. Clinicians can also capture it as free-text clinical notes when that suits the consultation better.
Yes. Every document previews in the app and exports as a themed PDF you can download, print, or share. You can also share it as a secure link that anybody can open without the app.
Document content is stored under your own patient record, file attachments in secure cloud storage, and a queryable mirror backs the public verification pages. Templates a clinician saves stay scoped to that clinician.
Yes. Any document can be saved as a reusable template in the clinician's forms library — medication protocols, standard test panels, or standard certificate wording — and reloaded into a new document in one tap.
The seal that proves a document is genuine — and how anyone can check it.
Medeefy is Medee's verification seal: the mark that a medical document is genuine, legitimate, and attested by the clinician who issued it. Documents written inside Medee by a verified clinician are sealed automatically the moment they are issued.
Yes. A clinician can digitize a physical document: Medee reads it, matches the issuer's name against the clinician attesting to it, extracts the content, and then seals it as verified, pending, or rejected.
Every document can be shared as a link or QR code. Opening it shows a read-only page with the verification banner — no app, no sign-in, nothing to install. A pharmacist can check a prescription, HR can verify a certificate, and a specialist can review a lab result.
The document identifier in the link is encrypted, so the URLs are not guessable — you cannot find someone else's document by trying variations. The pages are strictly read-only, and the underlying database is never opened to anonymous visitors.
It shows the document's current state — verified, pending, or revoked — so a recipient can trust what they are looking at rather than taking a screenshot at face value.
Chat inside a case, and everywhere else on the platform.
Every case has its own conversation thread. All chat and calls for that consultation happen there, so nothing is scattered across other channels.
Text, images, audio, and file attachments, with delivery and read receipts. Audio messages can be recorded and played back in-app.
Yes. You can reply to a specific message — the quote travels with your reply and tapping it jumps to the original — react with an emoji, and @-mention someone by name.
You can delete your own messages. Because chat happens in a medical context, deletion keeps an auditable trail rather than erasing the fact that a message existed.
Yes. Full-text search runs across your conversations and messages, scoped strictly to the threads you are actually a participant in.
Your case conversation with your clinician, one-on-one and group chats, dedicated conversations for collaborating clinicians and office staff, support conversations, and chats with Medee's AI assistants.
Multi-participant calling with native incoming-call ringing.
Anyone in the conversation taps Call. Medee creates the room, issues short-lived credentials, and rings the other participants. People can be invited mid-call, and entry to the room is guarded so nobody joins uninvited.
Yes. Calls ring natively — a full-screen incoming-call screen on iOS and a call-style notification on Android — so you do not miss a consultation because the app was closed.
Yes, calls are multi-participant, and additional people can be invited while the call is already running.
The provider workspace: queue, cases, patients, and tools.
The Lounge — a dashboard summarizing the care-request queue by category, active cases with unread indicators, an on-duty toggle, compliance notices, and quick tiles for the document makers and clinical calculators.
Up to five active cases. The cap is enforced when a clinician tries to accept a new one, so nobody over-commits and leaves patients waiting.
The Patients tab lists their complete, deduplicated patient roster. Cases are grouped by who the care was actually for — name and birthdate — so guardians, dependents, and walk-in subjects all resolve into accurate per-person histories.
Yes. A records tool creates a case for a consult that happened outside Medee, with no patient account attached. Such cases have no chat, are never billed, and do not count against the active-case cap.
A recurring weekly routine plus one-off overrides for individual weeks. Availability is validated when a patient tries to book, so you never receive a booking outside your hours.
Six: ABG, BMI, dosage, DVT/PE (Wells), kidney function (eGFR/CKD-EPI), and SIRS. Availability of each is rolled out gradually.
The Contacts hub combines a professional connection graph — request, accept, decline, disconnect — with an opt-in public directory that can be searched by name, specialty, role, or location.
Building a real-world clinic team inside Medee.
A clinic lets a clinician build their real-world practice inside Medee: an owner, invited staff, and shared jurisdiction over care. It is offered as a recurring subscription.
The owner (the creator, permanently), admins who manage details and members, secretaries, and physicians. A clinic can hold up to five invited staff, and pending invites count toward that cap.
A guided tour walks you through the benefits, completing your profile, your subscription, your clinic details (name, specialties, address, contacts, logo), staff invites, and finally your private legal documents such as business registration and permits.
There are deliberate cooldowns: a member cannot be removed within seven days of joining, and cannot be re-invited within seven days of being removed. Leaving voluntarily bypasses the cooldown. Removal also cleans up the member's clinic-bound availability.
Yes. Every clinic action lands in an immutable activity log that managers can read in the clinic management page.
When more than one clinician is involved in a case.
Yes. A case can involve more than one clinician through a single accept-or-decline handshake that covers reassignment, referral to another clinician, and invitations to collaborate.
The clinician being referred to has to accept. Once they do, they become the main clinician on the case and the referring clinician stays on as an adviser. Every reassignment is recorded in the case's history.
No. Collaborating clinicians and office staff work in their own dedicated conversations and do not have visibility into your chat with your main clinician.
Yes. Every material action taken on a case is written to an immutable case action log, readable in context.
How Medee confirms a clinician is who they say they are.
Yes. Before a clinician can accept cases they submit a government ID and PRC license documents plus a selfie assessment. A reviewer inspects the documents, the automated checks, name similarity, and their credentials and signature before approving them.
Pending, more-information-required if the reviewer needs extra documents, and then approved or rejected. Approval unlocks the features that require a verified clinician.
Yes. Clinicians submit their BIR Certificate of Registration and TIN, which is masked in storage. Submissions keep a full upload history and are verified by Medee before payouts are released.
Signing in, linking providers, email, and your devices.
Your phone number with an SMS one-time code is the primary method. Google and Apple sign-in are available too, and you can link or unlink providers later from Manage Authentication in Settings.
No. When you add a phone number that belongs to an older, data-rich account, Medee recovers that older account rather than stranding it — checking that the accounts genuinely belong to the same person before merging your social login onto the account that holds your history.
It is optional. You can add one or more emails and verify them individually, and the onboarding step can be skipped. Email is not used as a sign-in method.
Yes. Settings lists your signed-in devices with their name, platform, versions, and last activity, and lets you terminate a session you do not recognize.
Yes. You can request account-data deletion from Advanced Settings. The request goes into a queue that Medee staff work through, and you can cancel it while it is still pending.
Both are versioned documents rendered inside every Medee app, and they are published on this website as well.
What you pay, when you are charged, and how refunds work.
Medee places a hold on your payment method when you create the request, and only captures the fee once the clinician completes your case. If the consultation does not happen, the hold is released or the amount refunded.
The consultation fee is configured by Medee, with a default of ₱500.
Cards, e-wallets such as Maya and GrabPay, and direct online banking, processed through PayMongo. You can save a method for one-tap reuse next time.
The hold on your payment method is voided, or — if the fee had already been captured — refunded.
Medee issues discount coupons that you redeem in the booking wizard; a 100% coupon skips the payment step entirely. Credential-approved clinicians can also issue single-use coupons bound to themselves — redeeming one locks your request to that clinician and shows you their availability.
How clinicians accrue and claim what they have earned.
Medee collects the consultation fee from the patient, and the treating clinician accrues their share of it when the case is fulfilled. Earnings sit in an immutable ledger that neither side can edit directly.
Clinicians claim by submitting a payout invoice in a weekly Monday-to-Thursday window. Unclaimed windows are swept by a forfeit cycle that leaves a dispute path open for ten days.
Yes. Clinicians register a payout account, which Medee verifies before releasing money. Every finance action is written to an immutable audit trail.
The accrual is reversed automatically when the underlying payment is refunded, so the ledger always reflects what was actually collected.
How Medee reaches you, and on which device.
Every feature that needs your attention — a clinician accepting your request, a new message, a document issued to you, an incoming call — writes a notification that arrives as a push and appears in your in-app feed, so the two never disagree.
No. Notifications meant for one app are delivered only to that app, so a clinician who also has the patient app installed does not receive clinician alerts there.
Call ringing deliberately bypasses the normal notification pipeline so it can ring natively and immediately, even when the app is not running.
The clinician feed, events, jobs, and forms.
A feed for clinicians, filterable by type and sortable by date or relevance, carrying posts, announcements, events, and job listings.
Yes. Webinars and trainings publish into the feed with interest and RSVP, and job listings follow the same shape. Events also appear on this website.
It is a mutual handshake — you request, the other clinician accepts or declines, and either side can disconnect later. Connections are what gate referrals and collaboration invites.
Books are Medee's dynamic content engine: clinician-built intake and consent forms with branching questions, educational content, and forms published into the feed. Books carry translations, so a reader sees the edition in their language where one exists.
Points and achievements for real product milestones.
Yes. Real product milestones — completing your onboarding profile, reaching a verification level, your first consult, accepting a collaboration — award experience points, redeemable points, and achievements, which appear in an achievements widget.
No. The app records that a milestone happened, and Medee's server is the only thing that decides and grants the reward.
Getting help, and reporting something that went wrong.
Open a support ticket from the app. You then chat in a dedicated support conversation, where the staff side always appears as "Medee Support". Patients can also reach support directly from an active case.
Yes. You can report another user, a system failure, or content. The first entry point is the report action in the case conversation, and reports land in a queue that Medee staff review.
What the AI does, and what it is never allowed to see.
Two assistants: Medee Bear, a general assistant that can answer questions about the app, and Jose, a case companion a clinician can open from inside a case. AI also triages incoming requests so urgent ones sort higher in the clinician queue, and summarizes a case once it closes.
No. Free text is de-identified before any AI call — and when a case is for a dependent, it is the dependent's identity that is removed. The AI works on de-identified text only.
No. The AI can pre-fill a document for the clinician to review, but a clinician writes, signs, and issues every document.
No. All AI runs on Medee's servers, behind privacy controls and spending limits, with a kill switch Medee can use to turn it off entirely.
Who can read what, and how Medee enforces it.
You, and the clinicians on your case. Access is scoped per participant and per role, and the sensitive parts of the platform can only be changed through Medee's server — apps cannot write to them directly.
No. The only public reads on the platform are the document links you deliberately share, and the public clinician directory that clinicians opt into.
No. Product analytics are Medee's own, held in Medee's own database, with a retention window after which events are cleaned up.
Your deletion request is queued for Medee staff, and the analytics rows that describe you are redacted as part of processing it.