Scheduled AI briefing

On a schedule you set, a job reads the key numbers from your Power BI model and drafts a short email, sent from your Outlook. We build it in your environment, work through the numbers and the wording with you, and leave it running there. It's a fixed-scope project. Once it's live, it runs on its own schedule. You can have the briefing on its own, or include it in the monthly retainer.

  1. Query. A scheduled job reads your Power BI model.
  2. Draft. The AI service writes a short email from those numbers.
  3. Send. The email goes out from your Outlook.

By default, the briefing uses aggregated indicators only. Patient-level data is used only with a signed Business Associate Agreement, an explicit need, and an eligible API. The design is HIPAA-eligible with a signed BAA and the correct configuration. A BAA does not replace your own compliance program. The briefing runs in your Microsoft environment, under your contracts and the rules of your tenant.

We choose the path on the Reporting Review call.

Path A. Everything in your Microsoft tenant.

The query, the AI draft, and the email run in Copilot Studio and Power Automate. Data stays in your tenant. This path needs Copilot Credits during testing and at go-live. Without credits, the flow can be designed. It will not publish, and it will not run. The no-charge messages that come with Microsoft 365 Copilot do not cover this scheduled trigger. Path A goes live only when Copilot Credits are in place.

Path B. An enterprise AI API, with a compliance filter in the middle.

The query and the outbound email stay in your tenant. Only a minimal extract of aggregated measures, after a compliance filter, goes to an enterprise AI API that has a signed BAA. The draft comes back and is sent from your Outlook. We do not keep your numbers. Execution logs stay in your tenant. If you are already on Microsoft, the usual first choice is Azure OpenAI in your own Azure subscription. The other eligible options are Claude's enterprise API with a signed BAA, or the xAI enterprise API after a BAA, and only on the Zero Data Retention endpoint. We only use enterprise AI services that sign a BAA. Consumer AI apps are never used. The filter allowlists measures. It strips names, medical record numbers, NPIs, claim IDs, and addresses. It suppresses small cells that could identify a person. If the filter fails, the AI is not called and an alert is raised. A named person reviews the wording at the start, until you choose otherwise. Path B goes live with patient-level data only when there is a signed BAA and an eligible API.

Platform costs. You pay Microsoft or the AI provider, on your own contract.

DDH. A fixed setup covers the review, the build, and test rounds through acceptance. Then there is a monthly fee. If you already have the monthly retainer, the briefing is included. After a minimum term, you can continue month to month or take a handover and run it yourself.

What a setup can include

If you also want the data work set up, a build can include any of these.

  • Data model and Power BI

    10 weeks

    EHR or practice management, billing, bank, and the general ledger land in one model. You keep Power BI or Microsoft Fabric, and an alert names any file that is late.

  • Month-end close setup

    6 weeks

    A close checklist, the P&L matched to the general ledger, and the variance explained.

  • Cash and collections by payer

    6 weeks

    You see what has been collected, what each payer still owes, and cash as it arrives.

  • Provider pay and commissions

    4 weeks

    Provider pay and commissions run from one formula, with a statement each person can check.

After setup, running and supporting the work is a fixed monthly scope.

Start with the free Reporting Review

Send the short form. We reply the same day, find a time for a call, and send you a written assessment of your reporting. It costs nothing, and you keep it whether or not we work together.

Prefer email? contact@ddhbiconsulting.com · Or book a call