Patient ID & Consent
Katie collects the identifiers your practice requires, records who is calling and their stated preferences, and keeps disclosure inside your rules.
Knowing which patient the call is about
A request is only useful if staff know which patient it concerns. Katie asks for the identifiers your practice requires, typically full name and date of birth, along with a callback number. When the caller is not the patient, she records both people and their relationship, so the summary never leaves staff guessing whose chart to open.
Common names make this matter. Two patients with the same name and a similar birth year are a routine hazard in a large group, and complete identifiers in the summary are what keep a message from being attached to the wrong patient. Where your practice wants an extra identifier, such as the patient's home address, Katie asks for that as well.
Capturing, not disclosing
Identification on an inbound call protects the patient as much as it helps staff. Katie does not read out results, diagnoses or details from the chart. Because her job is to capture rather than disclose, a caller who gives someone else's name is not handed that patient's clinical information. Clinical questions go to clinical staff, who apply your usual verification before discussing care.
If a caller asks for information Katie is not permitted to give, the summary notes what was asked, so staff can follow up under your privacy policy.
Preferences the caller states
Callers often state preferences that matter: do not leave a voicemail at this number, text rather than call, speak only with my daughter. Katie records each of these in the structured summary, so staff can update the patient's record under your practice's consent process.
When a patient names someone they want involved, such as a spouse who will call about appointments, the summary records the name and relationship so staff can file whatever authorization your practice requires.
Consent for text messaging, and the forms behind it, remain your practice's policy. Katie captures what the caller says; staff document it in your systems. The AI never changes a chart or a contact preference on its own.
Callers from outside the family
Some calls about a patient come from organizations: a pharmacy, a home health agency, a hospital case manager, an attorney's office asking for records. Katie records the organization, the person's name and role, and what they want. Records requests go to the staff who handle release of information under your policies, and clinical calls from facilities follow your routing rules, often to the physician in pMD.
The safeguards behind each call
Routing physician messages into pMD keeps them inside a secure messaging platform your group already uses for clinical conversations.
- HIPAA compliance verified by Compliancy Group
- A Business Associate Agreement included for every practice
- Summaries sent only to the recipients your rules name, including pMD secure messaging for physicians
- No chart changes made by the AI
Frequently asked questions
- Does Katie verify identity against our records?
- She collects the identifiers your practice requires. Staff match them to your records when acting on the summary.
- Can a caller opt out of texts during the call?
- Katie records the request in the summary, and staff update the patient's preferences in your systems.
- Is a Business Associate Agreement included?
- Yes. Every practice receives one, and our HIPAA compliance is verified by Compliancy Group.
- What if the caller will not give a date of birth?
- Katie records what the caller is willing to share and notes that identity was not confirmed, so staff verify on the callback before discussing anything about the patient.
Ready to route these calls into pMD?
Book a demo to see how Katie answers your calls, and how summaries, consult requests and urgent notifications reach physicians in pMD secure messaging.
Book a Demo →