Healthcare · Managed platform (RLDatix)

Policy Management

One current, approved version of every hospital policy, with proof staff have read it

Overview

What you are buying

Moraph resells, implements and runs RLDatix's policy management platform as the single place your hospital keeps its policies and procedures. The platform routes each new or revised policy through the approvals your governance requires, prompts owners when a review falls due, and collects staff attestations. Moraph migrates your existing documents, configures the approval routes and review cycles, keeps the platform running, and prepares the evidence surveyors and auditors ask for.

The problem it solves

Hospital policies often live in shared drives, intranet pages and binders, with several versions of the same document in circulation. Staff cannot tell which one is current, owners miss their review dates, and approvals are tracked by email. When a surveyor asks for the policy in force on a given date, who approved it and whether staff were told about the change, the policy office spends days reconstructing the answer.

  • Several versions of the same policy are in circulation and staff cannot tell which is current
  • Review dates are missed because nobody is prompted
  • Approvals happen by email and are hard to evidence later
  • There is no reliable record that staff read and acknowledged a changed policy

Who uses it

  • Policy coordinators and accreditation managers at hospitals and health systems
  • Compliance, quality and risk leaders who answer for policy governance
  • Department leaders and policy owners who write and review policies
  • Medical staff offices and committees that approve clinical policies
  • Nurse leaders who need staff to know and follow current procedures

Requirements it supports

CMS Conditions of Participation for Hospitals (42 CFR Part 482)The Joint Commission accreditation standards for leadership and policy managementDNV NIAHO hospital accreditation requirementsHIPAA Privacy Rule policies and documentation (45 CFR 164.530(i) and (j))HIPAA Security Rule policies and documentation (45 CFR 164.316)State hospital licensing regulations

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

RLDatix provides the policy management platform, Moraph configures and runs it for your policy program, and your organization writes, approves and owns every policy.

AreaMoraphRLDatixYour organization
LicensingResells the subscription and tracks user counts, modules and renewals with youSets licence terms and editionsAgrees scope and signs the order
Platform availabilityMonitors service health and tells you about disruptions that affect staff access to policiesOperates the hosted platform under its own service commitmentsKeeps a downtime copy of critical policies under your business continuity plan
Policy contentMigrates documents and applies formatting standardsProvides the authoring and version control toolsWrites, reviews and owns every policy and its accuracy
Approval routesConfigures approval routes and committees from your governance rulesProvides the workflow capabilitiesDecides who approves each kind of policy
Review cyclesSets review intervals and reminders and watches for overdue reviewsSends reminders and tracks review datesOwners review on time and the policy office follows up
AttestationsConfigures attestation campaigns and audiences on requestDelivers attestations and records acknowledgmentsDecides which policies require attestation and from whom
Identity and accessConnects single sign-on and maintains roles from your approvalsProvides the sign-on and permission modelOwns the identity provider and approves who holds editing and approval rights
Incident responseInvestigates access, sign-on and configuration problems and restores the service configurationResolves platform defects and outagesDecides on business impact and communication to staff
Changes and updatesMakes configuration changes through a reviewed process and tests your setup against platform updatesDelivers platform releasesApproves configuration changes
User supportHandles second-line questions from policy owners and coordinatorsSupports the platform itselfProvides first-line help to staff through your service desk or policy office

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of RLDatix itself, which belongs to its vendor.

  1. Step 1

    Migration tracker

    During onboarding, Moraph tracks every source document from inventory to migration, with each owner's decision recorded.

    DepartmentDocuments foundOwner decisionsMigratedStatus
    Nursing (sample)214214188In progress
    Pharmacy (sample)969696Done
    Infection prevention (sample)58413517 awaiting owner
    Environment of care (sample)737360In progress
    Human resources (sample)4400Owner not assigned
    During onboarding, Moraph tracks every source document from inventory to migration, with each owner's decision recorded.
  2. Step 2

    Configuration baseline review

    Each approval route is written down and checked against your governance documents before go-live.

    Clinical policies · System-wide

    Applies to
    Clinical policies affecting more than one facility
    Steps
    Owner's director, then nursing practice council, then medical executive committee
    Review interval
    As set in your governance document
    Attestation
    Decided per policy by the policy coordinator
    Governance source
    Policy on policies (fictional sample)
    Check
    Council delegate not yet named

    Review notes

    • Route matches the policy on policies
    • Committee approval records the meeting date
    • Delegate needed for absences of the council chair
    Each approval route is written down and checked against your governance documents before go-live.
  3. Step 3

    Change requests

    Configuration changes are tested and approved by your policy coordinator before Moraph applies them.

    RequestChangeTestedApprovalStatus
    CR-0412Add facility-specific route for Example Community Hospital (fictional)PassedApprovedApplied
    CR-0418New template for procedure documentsPassedApprovedScheduled
    CR-0421Reassign 32 policies from departed ownerPassedPendingAwaiting approval
    CR-0425Change review interval for formsNot startedPendingNeeds governance decision
    Configuration changes are tested and approved by your policy coordinator before Moraph applies them.
  4. Step 4

    Access problem triage

    When staff cannot reach the policies they need, Moraph investigates, restores access and records what happened.

    Night shift unable to open policy links from intranet

    1. Problem reported by house supervisorService desk
    2. Links traced to a changed sign-on setting after an identity provider updateMoraph platform administrator
    3. Setting corrected with your IT identity teamMoraph platform administrator
    4. Access confirmed from three unitsPolicy coordinator
    5. Ticket closed and noted for the monthly reviewMoraph service manager
    When staff cannot reach the policies they need, Moraph investigates, restores access and records what happened.
  5. Step 5

    Monthly service review

    Each month Moraph reports on the state of the policy program and the service behind it.

    Monthly service review · Fictional sample month

    Policies published or revised
    38
    Reviews overdue
    27, up from last month
    Approvals waiting longer than your rules set
    9
    Attestation campaigns open
    3
    Changes applied
    5
    Platform notices
    1 scheduled maintenance

    For decision

    • Overdue reviews concentrated in one department after an owner left
    • Proposal to remind owners earlier before review dates
    • Upcoming platform release changes the approval screen
    Each month Moraph reports on the state of the policy program and the service behind it.
  6. Step 6

    Survey evidence

    Ahead of a survey, the history of a policy shows each version, who approved it and whether staff acknowledged it.

    VersionApproved byEffectiveAttestationStatus
    4Medical executive committeeFictional date C1,204 of 1,231Current
    3Medical executive committeeFictional date BNot requiredArchived
    2Chief nursing officerFictional date ANot requiredArchived
    1Unknown, migratedBefore migrationNot recordedArchived
    Ahead of a survey, the history of a policy shows each version, who approved it and whether staff acknowledged it.

Workflows

The principal workflows

  1. Write and revise

    Owners draft new policies and revisions in the platform, from your templates, with the earlier version kept and changes visible to reviewers.

    • Owner starts a new policy or a revision from the current version
    • Draft follows your template and formatting standard
    • Changes from the previous version are marked for reviewers
    • Related policies and referenced standards are linked
    • Draft submitted into its approval route
  2. Approve

    Each policy follows the approval route your governance sets, by department, policy type or committee, and the approvals are recorded with names and dates.

    • Route selected from policy type and scope
    • Each approver reviews, approves or returns with comments
    • Committee approvals recorded with the meeting date
    • Approved version published and the previous version archived
    • Effective date and next review date set
  3. Communicate and attest

    When a policy that staff must know changes, an attestation is sent to the people it affects, and acknowledgments are tracked until complete.

    • Policy office decides whether the change needs attestation
    • Audience selected by department, role or facility
    • Staff read the policy and acknowledge it
    • Outstanding acknowledgments followed up through managers
    • Completion recorded for evidence
  4. Review and evidence

    Owners are prompted when a review falls due, overdue reviews are escalated, and the policy office can show any policy as it stood on a past date.

    • Reminder sent to the owner ahead of the review date
    • Owner confirms no change or starts a revision
    • Overdue reviews escalated to the policy office and owner's leader
    • Moraph reports review status in the monthly service review
    • Version history and approvals exported for surveys

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Staff member

Any employee, contractor or medical staff member

Finds and follows the current version of the policies that apply to their work.

Sees

  • Current approved policies for their facility and system-wide
  • Attestations assigned to them
  • Their own attestation history

Does

  • Searches and reads policies
  • Acknowledges policies sent for attestation
  • Sends feedback on a policy to its owner where enabled

Cannot

  • See drafts or archived versions
  • Edit or approve a policy
Approvals
Nothing they do needs approval.
Notified about
Attestations assigned to them and reminders when they are outstanding.

Policy owner

Department director, nurse manager, pharmacy director, infection prevention lead

Keeps the policies they own accurate, current and reviewed on time.

Sees

  • Their policies in every state: draft, in approval, published and archived
  • Review dates and comments from approvers
  • Attestation progress for their policies

Does

  • Drafts new policies and revisions
  • Submits drafts into their approval route
  • Responds to approver comments
  • Completes scheduled reviews or starts a revision
  • Requests attestation for a changed policy

Cannot

  • Publish a policy without completing its approval route
  • Approve their own policy
  • Delete an archived version
Approvals
Every new policy and revision goes through the approval route your governance sets.
Notified about
Reviews coming due and overdue, policies returned with comments, and approvals completed.

Approver

Executive sponsor, committee chair, medical executive committee, chief nursing officer

Decides whether a policy is approved for use.

Sees

  • Policies waiting for their approval, with changes from the previous version
  • Policies they have approved before
  • Comments from earlier approvers in the route

Does

  • Approves or returns a policy with comments
  • Records committee approval with the meeting date
  • Delegates approval during absence where your rules allow

Cannot

  • Approve a policy they own or drafted
  • Edit a draft directly while approving it
  • Skip a step earlier in the route
Approvals
Their decisions are the approvals; delegation follows your governance rules.
Notified about
Policies waiting for their approval and reminders when they are waiting longer than your rules set.

Policy coordinator

Policy coordinator, accreditation manager, regulatory readiness manager, quality director

Runs the policy program and is the main contact for Moraph.

Sees

  • Every policy in every state
  • Review and approval status across the organization
  • Attestation campaigns and their progress
  • The audit trail

Does

  • Assigns owners and review intervals
  • Approves changes to approval routes and templates raised with Moraph
  • Runs attestation campaigns
  • Follows up overdue reviews with owners and leaders
  • Prepares survey evidence with Moraph

Cannot

  • Approve policies in place of the designated approvers
  • Edit the audit trail or delete version history
Approvals
Approves configuration changes; route changes for clinical policies are agreed with the medical staff office.
Notified about
Overdue reviews, stalled approvals, attestation progress and change requests needing a decision.

Moraph service team

Moraph platform administrator, migration specialist, service manager

Configures and runs the platform under your change approvals.

Sees

  • Configuration, routes, templates and user roles
  • Policy metadata and status needed to run the service
  • Platform notices from RLDatix

Does

  • Migrates documents and applies templates
  • Configures approval routes, review intervals and attestation campaigns
  • Connects and maintains single sign-on
  • Investigates access and configuration problems
  • Prepares the monthly service review and evidence reports

Cannot

  • Approve or publish policies
  • Change routes or roles without your approval
  • Access the platform outside the scope your organization authorizes
Approvals
Configuration changes are approved by the policy coordinator before they are applied.
Notified about
Approved change requests, access problems reported by staff and platform service notices.

Auditor (read-only)

Internal auditor, compliance reviewer, surveyor support under temporary access

Reviews policies and their governance without changing anything.

Sees

  • Policies and their version history within the scope granted
  • Approval records and attestation results
  • Review status reports

Does

  • Searches and reads policies and history
  • Exports evidence within scope, with each export logged
  • Records review notes where enabled

Cannot

  • Change, approve or archive anything
  • Keep access after it expires
Approvals
Access is approved by the policy coordinator or compliance officer, with a scope and an end date.
Notified about
Nothing by default.

Permissions at a glance

ActionStaffOwnerApproverCoordinatorMoraphAuditor
Read current policiesFullFullFullFullView onlyView only
Complete attestationsOwn work onlyOwn work onlyOwn work onlyOwn work onlyNo accessNo access
Draft and revise policiesNo accessOwn work onlyNo accessFullNo accessNo access
Approve a policyNo accessNo accessApprovesNo accessNo accessNo access
Publish an approved policyNo accessNo accessNo accessFullNo accessNo access
View drafts and archived versionsNo accessOwn work onlyOwn work onlyFullView onlyView only
Run attestation campaignsNo accessOwn work onlyNo accessFullFullNo access
Set owners and review intervalsNo accessNo accessNo accessFullFullNo access
Change approval routes and templatesNo accessNo accessNo accessApprovesFullNo access
Migrate and import documentsNo accessNo accessNo accessApprovesFullNo access
Manage users and rolesNo accessNo accessNo accessApprovesFullNo access
View audit trailNo accessNo accessNo accessView onlyView onlyView only
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Nobody approves a policy they own or drafted, and a policy cannot be published until every step in its route is complete.
  • Approval routes, review intervals and roles are set with you during implementation and follow your governance documents; Moraph changes them only through approved change requests.
  • Staff need no editing account to read policies: they reach the library through single sign-on or a link from your intranet.
  • Moraph staff work under named accounts within the scope your organization authorizes, and every configuration change they make is recorded and reported in the monthly service review.

Features

What it does

Single policy library

One searchable place for current policies and procedures, organized by department, facility and topic, with only the approved version visible to staff.

Version control

The platform keeps every earlier version with its approvals and effective dates, so the policy in force on a past date can be shown.

Approval routes

Moraph configures approval routes by policy type, department and committee from your governance rules, and keeps them current as committees change.

Review reminders

Owners are reminded before a review falls due, and overdue reviews are escalated to the policy office.

Attestation campaigns

Staff acknowledge new and changed policies, with outstanding acknowledgments tracked and followed up through managers.

Standards cross-reference

Policies can be linked to the accreditation standards and regulations they address, so the policy office can find what supports each one.

Document migration

Moraph migrates existing policies from shared drives and intranet pages, removes duplicates with your owners and records each document's current approval status.

Templates and formatting

Your policy template and formatting standard are applied to new policies and to migrated documents.

Multi-facility structure

System-wide and facility-specific policies are kept separately, so each facility sees what applies to it.

Staff search access

Staff find policies through single sign-on or a link from your intranet, without needing an editing account.

Survey readiness

Moraph prepares evidence of approvals, review status and attestations ahead of surveys and on request.

Monthly service review

Each month Moraph reports on overdue reviews, approvals waiting, attestation progress, changes made and platform notices.

Integrations

How it connects to your systems

Connects toHowWhat flows
Single sign-onStaff and owners sign in through your identity provider (SAML), so your password and multi-factor policies apply.In: user identity and group membership for roles.
Intranet and EHR linksLinks to the policy library, or to individual policies, placed on your intranet and other staff-facing systems, where those systems allow it.Out: links to current policy versions.
HR directoryStaff, department and manager data used to target attestations and follow up outstanding acknowledgments.In: workforce directory and reporting lines.
Learning managementAttestations or related training can be assigned through your learning platform, including Moraph's managed Learning Management service.Out: policies needing attestation. In: attestation completions.
Document sources for migrationExisting policies from shared drives, intranet sites and document systems, migrated once during implementation.In: policy documents and their known approval history.
Service deskChange requests and access problems tracked in Moraph's service desk, with your ticketing system connected where agreed.In and out: tickets, status and resolution notes.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Single sign-on

Everyone signs in through your identity provider, so your password and multi-factor policies apply.

Role-based access

Staff see only approved policies; drafts, archived versions and approval comments are limited to the roles that need them.

Controlled Moraph access

Moraph staff use named accounts with the access your organization authorizes, and changes are made through approved change requests.

Audit trail

Edits, approvals, publications and attestations are recorded with who did them and when.

Encryption and keys

Data Moraph holds for the service, such as migration files and evidence exports, is encrypted with keys staff cannot use without explicit, time-bound authorization.

No patient information by design

Policies should not contain patient information, and migration checks flag documents that appear to. Where your use involves protected health information, a business associate agreement is put in place first.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

10 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Operational

Reviews due and overdue

For policy coordinator and owners

Policies with a review falling due or overdue, with the owner, department and days remaining or overdue.

Break down by
Owner, Department, Facility, Due window
Delivered as
Live dashboard; scheduled email
Used for
Getting reviews done before they lapse.

Approvals waiting

For policy coordinator and approvers

Policies in an approval route, the step they are on, who holds them and how long they have waited.

Break down by
Approver, Route, Policy type, Age
Delivered as
Live dashboard; scheduled email
Used for
Moving stalled approvals along.

Attestation progress

For policy coordinator, owners and managers

For each attestation campaign, who has acknowledged the policy and who has not.

Break down by
Policy, Department, Manager, Status
Delivered as
Live view; scheduled email to managers
Used for
Following up outstanding acknowledgments.

Survey and audit

Policy history

For policy coordinator, auditors and surveyors

Every version of a policy with its approvers, approval dates, effective dates and what changed.

Break down by
Policy, Version, Approver, Date range
Delivered as
Live view; PDF export
Used for
Showing the policy in force on a date and how it was approved.

Attestation evidence

For compliance officer and auditors

Completed attestations for a policy version with names and dates.

Break down by
Policy, Version, Department, Period
Delivered as
Live view; PDF and CSV export
Used for
Evidence that staff were told about a policy and acknowledged it.

Standards coverage

For accreditation manager

Accreditation standards and regulations linked to policies, and standards with no linked policy.

Break down by
Standard, Chapter, Owner, Facility
Delivered as
Live view; CSV export
Used for
Finding gaps before a survey.

Policies published and retired

For policy coordinator and compliance committee

Policies published, revised and retired in a period, with their approval dates.

Break down by
Period, Department, Change type
Delivered as
PDF; CSV export
Used for
Committee reporting on policy changes.

Management

Policy program summary

For compliance committee and senior leadership

Review status, overdue counts, approval times and attestation completion over time.

Break down by
Facility, Department, Period
Delivered as
PDF; scheduled email
Used for
Oversight of policy governance.

Owner workload

For policy coordinator

Policies per owner, reviews coming due and owners who have left or changed role.

Break down by
Owner, Department, Status
Delivered as
Live view; CSV export
Used for
Reassigning ownership and spreading review work.

Service

Monthly service review

For policy coordinator and compliance officer

Configuration changes applied, access problems resolved, migration progress, platform notices and planned work.

Break down by
Period, Change type, Ticket type
Delivered as
PDF; reviewed in a monthly meeting
Used for
Holding Moraph to account for the service and planning changes.

Exports, access and evidence

  • Reports come from RLDatix's reporting and from Moraph's service records. Moraph sets up the standard set with you during implementation and adjusts it through change requests.
  • Policy history can show any policy as it stood on a past date, with its approvals, for surveys and legal requests.
  • Approvers and owners see reports for their own policies; the policy coordinator and compliance officer see the whole program.
  • Attestation reports can be filtered to a department or manager and sent to them on a schedule.
  • Exports of evidence are recorded in the audit trail with who ran them and when.

Deployment

Where and how it runs

New RLDatix subscription

Moraph resells the subscription and runs the platform from implementation onward.

Your existing subscription

Where you already license the RLDatix platform, Moraph takes over configuration and operation, subject to the vendor's terms.

Alongside other Moraph services

Can be run with Moraph's managed Learning Management service so changed policies are assigned for attestation or training.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Governance workshop

We document your policy governance with the policy office: policy types, owners, approval routes, committees, review intervals and attestation rules.

Inventory and cleanup

We inventory existing policies across drives, intranet pages and binders, and owners decide which are current, which merge and which retire.

Migration

Current policies are migrated with their known approval and review dates, formatted to your template and checked by their owners.

Configuration

Routes, review intervals, roles, facility structure and attestation settings are configured and tested with sample policies.

Sign-on and links

Single sign-on is connected and links are placed on your intranet so staff can reach the library from where they work.

Go-live and handover

Owners, approvers and coordinators are shown their own tasks, old locations are withdrawn by agreement, and the monthly service review begins.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not the vendor. RLDatix owns and operates the platform, and its own service commitments, roadmap and outages apply.
  • Licences are subject to RLDatix's terms, and the features available depend on the edition and modules you license.
  • Moraph does not write, approve or take responsibility for the content of your policies; owners and approvers remain accountable for them.
  • Moraph does not give legal or accreditation advice. Linking policies to standards helps find gaps, but deciding what a standard requires is your organization's judgment.
  • Migration quality depends on the source documents. Approval history that was never recorded cannot be recreated and is marked as unknown.
  • A downtime copy of critical policies under your business continuity plan remains your organization's responsibility.
  • First-line help for staff stays with your service desk or policy office, with Moraph providing second-line support.
  • The service is not an incident reporting or document control system for medical device or laboratory quality systems.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. Take one department's policies and review how they would be inventoried, cleaned up and migrated
  2. Walk a sample policy through your approval route as it would be configured
  3. Check that a staff member can find a current policy from your intranet in a few steps
  4. Ask for a sample policy history and attestation report and compare it with what surveyors ask for
  5. Review the responsibilities table with your policy office, compliance and IT leads
  6. Agree how downtime access to critical policies will be handled

Questions

Frequently asked questions

We already use RLDatix for policies. Can Moraph take over running it?

Yes. Moraph reviews your current configuration against your governance documents and takes over operation, subject to RLDatix's terms for your existing licence.

Who writes and approves our policies?

Your organization does. Moraph configures the routes and reminders, but owners write the policies and your approvers decide.

What happens to our old documents?

They are inventoried and owners decide which are migrated, merged or retired. Old locations are withdrawn by agreement once the library is live.

Can staff read policies during a platform outage?

Platform availability is RLDatix's responsibility. Your business continuity plan should include a downtime copy of critical policies, and Moraph can help you set one up.

How is it priced?

Platform licences are priced by RLDatix's terms, and Moraph's implementation and managed service are quoted separately. See Working with Moraph for what drives a quotation.

Is there a business associate agreement?

Policies should not contain patient information. Where your use of the service involves protected health information, a business associate agreement is put in place first.

Next steps

Evaluate Policy Management

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Policy Management guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Policy Management support guide.