Clinic direct send
Bring Ember direct send to your clinic.
Patients can already export their report anywhere. When a clinic joins, Ember can add its approved report inbox to the in-app clinic list so the patient can prepare an addressed report.
What changes for the clinic
A consistent report reaches the inbox your team approves.
The patient starts every send
Ember does not transmit reports in the background. The patient reviews their name, prepares the PDF, chooses the email app, and sends it.
Your approved inbox is allowlisted
The app resolves a clinic name to an Ember-owned destination. A link cannot substitute another recipient address.
The PDF is ready to review
The attachment combines the 90-day calendar and chart-style summary, including diary completeness and treatment context.
A useful companion measure
Why Impacted Days sits beside frequency and MIDAS.
Frequency can improve while meaningful activity limits remain. Ember keeps a dated count of functional impact so a clinician can see burden across the treatment window, including partial limitation that may not appear as a fully missed day.
Impacted Days is an Ember-defined longitudinal metric. It has not been independently validated and does not replace MIDAS, another validated instrument, or clinical judgment. It adds day-level context that may support documentation for treatment review and payer requests without guaranteeing coverage.
For an active Botox cycle, Ember schedules its MIDAS reminder six weeks after the most recently logged injection. This places the assessment at the midpoint of the FDA-labeled 12-week retreatment schedule instead of relying only on the end-of-cycle visit. MIDAS still asks about the prior three months, so the score does not isolate Botox response by itself.
Ember reports the source and completeness of the underlying daily logs so clinicians can decide how much weight to place on each trend.
Clinic setup
A short operational checklist.
Choose the report inbox
Ask your IT or compliance team for a monitored address under clinic control. Decide who reviews messages and where the PDF belongs in the chart.
Send Ember the routing details
Provide the clinic display name, report address, operational contact, and confirmation that the inbox is approved for patient-submitted health information. Do not include patient information.
Test the patient flow
Ember adds the clinic to its allowlist and coordinates a test from supported devices. Your team confirms receipt, attachment handling, and internal routing.
Share the workflow with staff
Give scheduling and clinical teams the clinic's report instructions. Patients remain able to save or send their report manually if direct send is unavailable.
Privacy boundaries
The report stays under patient control until they share it.
Health data remains on the patient's device while Ember generates the report. Ember does not receive or retain the PDF when the patient sends it.
Each clinic remains responsible for its inbox, workforce access, retention, and legal review. HIPAA obligations depend on the actual relationship and data flow, so clinic counsel or compliance staff should evaluate the workflow rather than rely on a blanket BAA statement.