Enterprise DNA

Instead of Salesforce Health Cloud

Stop renting Salesforce Health Cloud. Own your credential desk.

We build your version around credential renewals, evidence checks and site reviews, map your Salesforce records and run it for you.

Health Cloud Sales & Service Core lists US$350 per user per month, billed annually: US$4,200 per user per year. This is the base-platform price; confirm provider-management entitlements in your quote.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The bill behind the register

A broad healthcare platform for a focused evidence desk

Salesforce Health Cloud includes far more than credential records. If your job is collecting certificates, checking renewals and preparing site decisions, compare that specific work with a system you own.

group

A licence for each platform user

The listed base price is US$350 per user per month with annual billing. Work out which people need the wider platform and which only review credential evidence.

storage

A wider healthcare record model

Health Cloud covers clinical and insurance records. This free base concentrates on practitioners, credentials and site appointments.

fact_check

Provider-management setup

Provider relationship management includes licences, facilities and related evidence. Your local country rules and site requirements still need to be fitted to your process.

assessment

Reports for the credential meeting

Your meeting needs renewals, missing documents and a named owner for each gap. Those answers are built into the free version.

rule

Your approval process

Your committee decides who is approved for a site. Keep its evidence reference, reviewer and decision beside the credential checks.

description

The work of bringing records across

Export detail reports, map the relevant records and reconcile the links. Enterprise DNA handles that work in the customised version.

Own the credential desk

Evidence, renewals and decisions connected

RENEWALS

See what expires before it becomes a scramble

Review the next sixty days alongside the owner and the latest check.

  • check An ordered queue includes already overdue credentials
  • check A practitioner file brings the relevant dates together
  • check Overdue evidence requests name their responsible owner
  • check Ask which expiring certificates also have missing indemnity evidence

VERIFICATION

Keep the source behind every check

Record what the operator actually checked, when and against which source.

  • check Keep registration references and document references together
  • check A renewed credential waits for a fresh verification
  • check Conditions need a recorded scope review
  • check Distinguish an Australian expiry-date query from a finding about registration status

SITE REVIEW

Prepare the committee pack from current records

See the gaps before recording the committee decision.

  • check Each site defines its documentary evidence requirements
  • check Missing mandatory registration requirements remain visible
  • check Recorded decisions retain their reviewer and evidence reference
  • check Ask which previously approved appointments have developed new gaps

OWNERSHIP

Keep the history and change the questions

Your records stay in your database as your group changes.

  • check Retain the original imported rows for reconciliation
  • check Draft credential files and renewal requests with your business name
  • check Export the records, source rows and action history together
  • check Ask which owners carry overdue requests across several sites

Make it yours

Design your own Salesforce Health Cloud replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Salesforce Health Cloud. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Salesforce Health Cloud replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Salesforce Health Cloud data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Provider Credentials for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Provider Credentials for Claude Code

Connected to your own database

Which credential renewals should we review first?

CR-103

Provider
Tane Rowe
Owner
Jo Bennett
Kind
nz-apc
Reference
DEMO-NZ-102
Expires on
2026-10-11
Days left
-5
Verification result
current

CR-104

Provider
Alex Morgan
Owner
Priya Shah
Kind
au-registration
Reference
DEMO-AU-103
Expires on
2026-10-13
Days left
-3
Verification result
current

CR-101

Provider
Mara Ellison
Owner
Jo Bennett
Kind
nz-apc
Reference
DEMO-NZ-101
Expires on
2026-11-20
Days left
35
Verification result
current

Ask it anything

Ten questions across your credential records

These questions run against the fictional demo today. Your own evidence rules and reporting questions can be fitted to your version.

chat_bubble Which sites have the most gaps before their next committee review?
chat_bubble Which providers have a practising certificate due within sixty days?
chat_bubble Which Australian registrations need a live register check after the recorded expiry?
chat_bubble Which site appointments have no indemnity evidence?
chat_bubble Who owns overdue requests for credential evidence?
chat_bubble Which pending appointments have completed their recorded checks?
chat_bubble Which approved appointments have developed new record gaps?
chat_bubble Which credentials have never been independently checked?
chat_bubble Which providers appear at more than one site?
chat_bubble Which register conditions still need a recorded scope review?

Switching

How to switch from Salesforce Health Cloud

The move usually depends less on loading records than on mapping your reports and rules, reviewing the imported data, and running both systems side by side before you stop using the credential desk in Health Cloud.

  1. 1

    Export your credential records

    Export the supported Details Only CSV reports for the credential records you intend to move. Use the documented report layout, and include practitioner, credential, site appointment and evidence request information where the reports support it. Attachments stay in your evidence store, so keep those available and check their references. If your account does not offer the required export, check with Salesforce Health Cloud about what it allows.

  2. 2

    Map and test the reports

    Map report headings, controlled values, dates and relationship links to the supported import layout. The free version accepts supported detail report layouts after this mapping. Run a test import first and review its results before loading records for use. Do not treat an arbitrary Health Cloud backup as a supported import.

  3. 3

    Review import issues

    Check the validation results and any rows reported for reconciliation. Resolve mismatched headings, values, dates or relationship links, then run the import again. Changed source rows stop for explicit reconciliation, while unchanged rows import once. Imported appointments start pending, credentials have no verification, and historic approvals need human review before they become a local decision.

  4. 4

    Run both systems side by side

    Keep Salesforce Health Cloud available while you check the imported records and continue the credential desk work in both systems for a short, agreed period. Compare practitioner details, evidence references, renewals and site decisions. Have the responsible reviewer check current registration, scope and conditions. A recorded approval does not replace that review or your site committee's decision.

  5. 5

    Switch off the moved work

    Once the records and process have been reconciled, stop using Salesforce Health Cloud for the credential desk work you moved. First confirm what else your organisation uses Health Cloud for and which connections still depend on it. This replacement covers provider credentialing, not Health Cloud's wider remit, so only retire the wider system if those other needs have been addressed.

construction

Where the real effort goes

The main work is usually mapping your own fields, controlled values and evidence rules, then deciding how much history to bring and reviewing historic approvals. Attachments remain in your evidence store, and imported credentials need fresh verification. If you have Enterprise DNA run the version, they handle the mapping and customisation with you, based on your records, sites and rules.

Not ready for a call?

Get your Salesforce Health Cloud switch plan by email

We will send you the step-by-step plan for moving your business off Salesforce Health Cloud, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Start with the free version or have yours built

Open source

Do it yourself

Free code; hosting and agent costs are yours

  1. 1 Clone the repo, run npm install, then npm run demo
  2. 2 Open the folder in Claude Code, Codex, OpenCode or Cursor
  3. 3 Inspect the fictional credentials, renewal queue and committee pack
  4. 4 Map the supported Salesforce CSV reports, test a dry run, then import
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your credential types, evidence rules and committee responsibilities
  • check Your Salesforce records mapped, checked and brought across
  • check A web front end or document capture if your team needs it
  • check Your preferred technology and register connections, scoped for your process
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Renewals and evidence gaps ready for your weekly review
  • check Access controls, backups and connections fitted to your group
  • check Changes as your sites and professional requirements change
Book a call

Questions

Instead of Salesforce Health Cloud, answered

Does this replace all of Salesforce Health Cloud? expand_more

It covers the provider credential desk: practitioner records, evidence, renewals and site decisions. Health Cloud has a much wider remit. We agree exactly which work moves and which connections your version needs before switching.

Will our existing credential records come across? expand_more

The free version imports the supported detail-report layouts after their headings, dates and relationship links have been mapped. Do a test run first, then reconcile the records. Original rows are retained. Attachments stay in your evidence store, and historic approvals need human review before becoming a local decision. We handle the mapping in your customised version.

Does a green check mean a practitioner can work? expand_more

It means the recorded checks are complete. The responsible reviewer still checks current registration, scope and conditions. A passed Australian expiry date leads to a public-register review; it does not itself establish that registration has ended. Your site committee remains responsible for its decision.

Can we use our own documents, screens and register connections? expand_more

Yes. The free base produces branded credential files, renewal drafts and committee reviews. Enterprise DNA can build document capture, web screens and register connections into your version, around your access requirements and actual sources.

What does Enterprise DNA charge to build and run it? expand_more

One setup fee, then a retainer. Sam scopes your records, sites, evidence rules and ongoing operation with you. The code is open source and the database is yours.

Show Sam your credential desk

In a 30-minute call, show Sam how you collect evidence, review renewals and approve site appointments. Leave with a clear scope for your version and the records to bring across.

Book a 30-minute call Get the free version

Provider Credentials for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Salesforce Health Cloud?

Get your version built