Incident summary and billing notification to referring facilities

Purpose

1. Automate generation and delivery of incident summaries and related billing notifications to referring healthcare facilities post air ambulance missions.

2. Ensure rapid, accurate, and regulatory-compliant communication of patient transfer details, service logs, and financial statements.

3. Minimize manual errors, reduce administrative workload, and improve transparency for referrers and partner facilities.

Trigger Conditions

1. Completion of an air ambulance mission and corresponding patient record closure in EMS/dispatch software.

2. Confirmation of billing readiness by accounting department in medical billing system.

3. Reception of new finalized patient care report (PCR) or incident summary approval from clinical supervisor.

4. Assignment of unique invoice/billing ID to a case in finance software.

Platform Variants

1. Salesforce Health Cloud

• Feature/Setting: Flow Builder — Automate sending case details and generating summary docs via outbound messages after mission close.
  
• API: REST API — Create Case, Send Notification (POST /services/data/vX.X/sobjects/Case/).
  

2. Epic

• Feature/Setting: API integration with Clarity — Trigger HL7 message posting incident summaries and billing.
  
• API: /FHIR/DocumentReference (Send PCR PDF to external facility).
  

3. Cerner

• Feature/Setting: Cerner Open Developer Experience — Use SMART on FHIR for eDoc generation, send via outbound event.
  
• API: outboundmessage.create and FHIR DocumentReference.
  

4. Microsoft Dynamics 365

• Feature/Setting: Power Automate Flow — On "Mission Completed" status, send adaptive card summary & invoice as email.
  
• API: PATCH /incidents, POST /emails.
  

5. Twilio SMS

• Feature/Setting: Messaging API — Text notifications with link to download incident/billing documents.
  
• API: POST /Messages.
  

6. SendGrid

• Feature/Setting: Transactional Email API — Email incident summaries and bills as PDF attachments.
  
• API: POST /mail/send.
  

7. DocuSign

• Feature/Setting: Automated Envelope — Send billing or summary documentation for electronic acknowledgment.
  
• API: POST /v2.1/accounts/{accountId}/envelopes.
  

8. AWS Lambda

• Feature/Setting: Event-driven workflow — Generate PDF, invoke external notification APIs.
  
• API: Lambda invoke & SDK for mail/SMS/slack.
  

9. Google Workspace (Gmail)

• Feature/Setting: App Script Automation — Trigger summary email on data update in integrated Google Sheet or form.
  
• API: GmailApp.sendEmail().
  

10. Slack

• Feature/Setting: Incoming Webhooks — Send real-time update to facility’s Slack channel on case completion.
  
• API: POST /api/chat.postMessage.
  

11. PagerDuty

• Feature/Setting: Automated incident notification to facility stakeholders.
  
• API: POST /incidents.
  

12. Zapier

• Feature/Setting: Multi-platform automation — Watch for new PCR/mission, route to facilities via email/SMS/cloud.
  
• API: Zap triggers and actions configurable for all connected services.
  

13. Zendesk

• Feature/Setting: Automated ticket creation and summary file attachment for facility reference.
  
• API: POST /api/v2/tickets.
  

14. ServiceNow

• Feature/Setting: Incident Management Flow — Create integration workflow for notification and document sharing.
  
• API: POST /api/now/table/incident.
  

15. Freshdesk

• Feature/Setting: Trigger new incident notification and attach summary/bill for facility’s support portal.
  
• API: POST /api/v2/tickets.
  

16. Meditech

• Feature/Setting: Interface engine (e.g., Cloverleaf) — Send HL7 ORU with summary/billing extract to facility.
  
• API: HL7 ORM/ORU messages.
  

17. QuickBooks Online

• Feature/Setting: SDK to create/send invoice post-mission to referrer’s contact.
  
• API: POST /v3/company/{companyId}/invoice.
  

18. Xero

• Feature/Setting: Invoice API — Send billing statement as soon as mission metadata appears in platform.
  
• API: POST /api.xro/2.0/Invoices.
  

19. SMTP (Generic email server)

• Feature/Setting: SMTP relay — Email incident summary files to external contacts.
  
• API: RFC 5321 standard (MAIL, RCPT, DATA commands).
  

20. ShareFile (Citrix)

• Feature/Setting: Automated file upload/link sharing — Place summaries and set permissions to notify facility staff.
  
• API: POST /v3/files/upload, POST /v3/Share.
  

Benefits

1. Immediate, error-free summary and billing delivery to external partners improves payment cycles and compliance.

2. Consistent, traceable communication enhances relationship management with referring facilities.

3. Frees clinical, transit, and admin staff from repetitive tasks, focusing resources on core EMS operations.

4. Supports rapid data transfer in high-urgency medical aviation contexts, ensuring post-mission continuity.