Getting started with Clinical Collaboration

Moraph provisions Microsoft Teams for clinical use under a business associate agreement, configured for care team chat, virtual consults and the handling of protected health information. We set up the tenant controls, meeting policies, retention and guest access your privacy and security teams approve, and then run the environment as a managed service. Your clinicians use Teams; your organization keeps control of who can do what and of every policy decision.

What it is for

Many health systems already license Microsoft 365, and clinicians already use Teams, but often in a configuration built for office work rather than patient care. Guest access, external meetings, recording, file sharing and retention are set once by IT and rarely reviewed against HIPAA. Virtual visits run on a mix of tools, care team chats sit beside general staff chat, and when privacy asks where a recorded consult is stored or who could join a meeting with a patient, the answer takes days to assemble.

• Teams settings were chosen for office collaboration, not for conversations that contain PHI
• Virtual visits run on several tools with different controls and no common record
• Guest access, recording and external sharing are not reviewed against privacy policy
• Nobody owns the configuration day to day, so changes drift from what was approved

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

Before you start

• Your organization uses Clinical Collaboration as a managed platform from Moraph, under an agreement that covers it.
• Licences for Microsoft Teams, bought through Moraph or under your own agreement with the vendor.
• A Moraph account in your organization for each person who works with Moraph on the service.
• Named technical and security contacts, recorded in the Moraph Portal.

Steps to get started

1. Agree the scope of the managed service for Clinical Collaboration with Moraph, including which environments and teams it covers.

2. Name your administrators, technical contact and security contact in the Moraph Portal under People and access.

3. Review the configuration baseline Moraph proposes for your regulations, and record any changes you need.

4. Confirm how users will sign in, through your identity provider where the platform supports it.

5. Agree the pilot group and the cut-over plan with your Moraph delivery lead.

Where to go next

• Onboard Clinical Collaboration
• Everyday tasks
• Connect your systems
• Security, data and compliance
• Troubleshooting and the support guide
• Product overview on moraph.com