Clinical Collaboration

Principal workflows

• Provision: Moraph assesses your Microsoft 365 tenant, agrees a clinical configuration baseline with your privacy and security teams, and applies it to Teams and the services Teams depends on.
• Collaborate: Care teams work in Teams structured for clinical use: unit and service-line teams, care team chats, and channels with membership that follows your directory groups.
• Consult: Virtual consults with patients and outside clinicians run as Teams meetings with policies for lobbies, guests, recording and transcription that your organization has approved.
• Run: Moraph operates the environment day to day: monitoring configuration and service health, handling changes and access requests, and reporting on drift and use.

Who uses it

• Health systems, hospitals and physician groups that license Microsoft 365
• CMIOs, CNIOs and clinical informatics teams planning virtual care
• Privacy and security officers who answer for PHI in collaboration tools
• IT teams that want Teams run to a documented baseline without adding headcount
• Ambulatory and behavioral health practices that offer video visits

Reporting

• Baseline compliance and configuration drift
• Changes applied, with approvals
• Guest access and team ownership reviews
• Moraph administrative access reviews
• Incidents and requests by type and age
• Virtual visit use by department

Features

• Clinical configuration baseline: A documented set of Teams, meeting, guest, file and retention settings for clinical use, approved by your privacy and security leads and kept under change control.
• Business associate coverage: Moraph signs a business associate agreement with you, and we confirm that the Microsoft services carrying PHI are covered by Microsoft's own BAA terms for your agreement.
• Virtual visit meetings: Teams meeting templates for patient visits, with the lobby, presenter, chat and recording settings your policy sets, and browser join for patients.
• Care team structure: Teams and channels by unit, service line or program, created from templates, with membership driven by your directory groups.
• Guest and external access controls: Who can invite outside clinicians, which external organizations can chat with your staff, and how guest access is reviewed and expired.
• Recording and transcript governance: Where recordings and transcripts are stored, who can see them, and how long they are kept, configured to your policy and documented.
• Retention and holds: Retention policies for chats, channels and recordings set in Microsoft Purview to your schedule, with legal holds applied on request from your legal team.
• Sensitivity labels and sharing rules: Where your licensing includes them, labels and sharing restrictions applied to clinical teams and files so PHI is not shared outside approved groups.
• Conditional access and device policy: Sign-in conditions and app protection for Teams on phones and shared workstations, configured through Microsoft Entra ID and Intune where licensed.
• Configuration drift monitoring: Regular comparison of live settings against the approved baseline, with every difference corrected or explained and recorded.
• Change and access requests: A single route for new teams, policy changes, guest requests and exceptions, each with your approver recorded.
• Service reviews: Regular reviews of use, changes, incidents, drift and open risks with your IT, privacy and clinical informatics leads.

Integrations

• Microsoft Entra ID: Sign-in, multi-factor authentication, conditional access and the groups that drive team membership, managed in your tenant.
• Microsoft Purview: Retention, holds, sensitivity labels and audit search for Teams content, configured where your licensing includes them.
• Microsoft Intune: App protection and device policies for Teams on phones, tablets and shared clinical workstations, where licensed.
• Electronic health record: Where your EHR vendor supports launching Teams visits from the scheduled appointment, Moraph configures the Teams side and works with your EHR team on the rest.
• Microsoft Bookings and virtual appointments: Scheduling of patient virtual appointments and reminders, where your licensing includes them.
• Your service desk: Requests and incidents raised by your staff can be routed to Moraph's service desk, or Moraph's records linked to your own tool.
• Security monitoring: Teams and Microsoft 365 audit events can be forwarded to your security information and event management tool.

Deployment

• Your Microsoft 365 tenant, managed by Moraph: Teams runs in your organization's tenant; Moraph configures and operates it for you under a managed service agreement.
• With licenses bought through Moraph: Moraph resells the Microsoft licenses you need and manages them alongside the service, subject to Microsoft's terms.
• Alongside other Moraph services: Run with Moraph's Secure Messaging, Single Sign-On or Identity Governance services so clinical communication and access are managed together.

Security and privacy

• Single sign-on: Your staff sign in through Microsoft Entra ID under your multi-factor and conditional access policies, and Moraph's staff sign in to Moraph systems through Moraph's own identity provider.
• Role-based access: Clinicians see the teams they belong to, and Moraph's service team works on configuration rather than content.
• Controlled privileged access: Moraph's administrative roles in your tenant are granted by your IT team, used only for approved work, and keys and credentials cannot be used without explicit, time-bound authorization.
• Complete audit trail: Every change Moraph makes is recorded in the service records with the request and approval behind it, and Microsoft's audit log records actions in the tenant.
• Independent audits: Moraph's operations are audited under SOC 2 Type II and ISO/IEC 27001. Microsoft's own compliance reports for Microsoft 365 are available from Microsoft under its terms.
• Data residency: Teams content stays in the Microsoft 365 data location of your tenant, and Moraph's service records are held in the United States, United Kingdom or Australia region you choose.

Limitations

• Moraph is not Microsoft. Teams and Microsoft 365 belong to Microsoft, and Microsoft's own service commitments, roadmap, maintenance and outages apply to them.
• Licenses are subject to Microsoft's terms, and some controls described here, such as sensitivity labels, advanced retention or virtual appointment features, depend on the licenses you hold.
• Business associate coverage for Microsoft services comes from your agreement with Microsoft. Moraph's BAA covers Moraph's services, not Microsoft's.
• Teams is a communication tool, not your medical record. Clinical documentation, orders and results belong in your EHR.
• Moraph does not make privacy, retention or clinical policy decisions. Your organization approves them and remains responsible for HIPAA compliance.
• Patient-side experience depends on the patient's device, browser and connection, which neither Moraph nor Microsoft controls.
• State telehealth, licensure, consent and recording rules vary, and legal advice on them is not part of the service.
• Moraph does not routinely read chats, files or recordings, so the service does not detect inappropriate content unless you configure and review tools for that purpose.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/clinical-collaboration. Purchasing routes and company information: www.moraph.com/how-to-buy.