Enterprise DNA

Instead of Salesforce Life Sciences Cloud

Stop renting Salesforce Life Sciences Cloud. Own your medical-information desk.

We build your administrative desk around how your team handles requests, bring the agreed Salesforce history across and run your version. Clinical content and specialist safety systems remain under your qualified team.

Salesforce lists Core at US$350 per user per month, billed annually. Customer Engagement is listed separately at US$150 per user per month.

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

What the subscription covers

A broad platform around a focused desk

Salesforce sells a life sciences suite. If the work you need to own is request administration, compare that workflow with the wider package before renewing. This free base covers the desk described here.

groups

Core seats

Core is priced at US$350 per user per month with annual billing. Start your comparison with the people licensed for the work.

layers

Customer Engagement access

The published Customer Engagement add-on is US$150 per user per month. Salesforce lists it among the requirements for Medical Inquiries.

database

A wider life sciences record

The platform serves more than medical requests. Separate the wider capabilities you use from the request records you want to own.

assignment

Request capture and routing

Medical Inquiries records questions and routes them to a medical owner. An owned desk can keep the administrative handover visible.

description

Response traceability

Approved response workflows connect a request to its sources. Keep your document references, reviewer evidence and delivery record together.

bar_chart

Reporting and record access

Your administrator can export a Details Only report. Agree the fields and evidence that must carry across before changing systems.

What you own

The request, the evidence and the next responsible person

Request desk

Know who owes the next reply

Read the open work by product, owner and due date. Specialist concerns have a separate handover record.

  • check Triage open requests before the weekly review
  • check See replies due within the next seven days
  • check Find overdue work by its current owner
  • check Cross-check missing request evidence against product and owner

Controlled references

Keep the approved source version attached

Hold the reference to the controlled document and the evidence of its review. Your medical team owns the actual content.

  • check Record a distinct reference for each source version
  • check Match the source product to the request
  • check Block response recording against expired or withdrawn sources
  • check Find source versions nearing review with linked requests

Review record

Keep preparation and approval visible

A prepared response reference goes to an independent reviewer before delivery is recorded. Typed names are records of responsibility, not identity checks.

  • check Keep the preparer and reviewer labels separate
  • check Record approval or rejection evidence
  • check Return an undelivered response for a fresh review
  • check Produce internal response cover sheets with the review history

Specialist handover

See which handoffs need an acknowledgement

Your safety and quality processes remain authoritative. The desk records their case references and receipt evidence.

  • check Separate medical requests from operator-classified safety and quality work
  • check Flag missing specialist acknowledgements
  • check Require acknowledged handoffs before administrative closure
  • check Review retention dates alongside closed work and evidence gaps

Make it yours

Design your own Salesforce Life Sciences 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 Life Sciences 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 Life Sciences 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 Life Sciences 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 Medical Information for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Medical Information for Claude Code

Connected to your own database

Which medical requests need a reply this week?

Approved document request

Product
Demo Product Alpha
Owner
Mira
Due on
2026-10-15
Days late
5

Source renewal follow-up

Product
Demo Product Alpha
Owner
Noah
Due on
2026-10-17
Days late
3

Reference version request

Product
Demo Product Beta
Owner
Noah
Due on
2026-10-22
Days late
-2

Ask it anything

Ten questions your medical-information desk answers

These questions run on the working demo. Your team can adapt them to its own fields and review process.

chat_bubble Which owners have overdue medical replies?
chat_bubble Which products have unanswered requests with missing request evidence?
chat_bubble Which source versions expire in the next month with linked requests?
chat_bubble Which approved replies refer to an expired or withdrawn source?
chat_bubble Which specialist handoffs still lack an acknowledgement?
chat_bubble Which products generate both medical and specialist work?
chat_bubble Which closed records have reached their retention review date?
chat_bubble Which requests are ready but have no recorded response?
chat_bubble How much imported history awaits reconciliation by source status?
chat_bubble Which owners carry work across more than one product?

Switching

How to switch from Salesforce Life Sciences Cloud

The move involves exporting and mapping your request history, checking a test import, then running both desks side by side briefly before you retire Salesforce Life Sciences Cloud.

  1. 1

    Export your inquiry history

    In Salesforce Life Sciences Cloud, export a configured inquiry report as a Details Only CSV. Include the request records and the columns you need to map to your process. Check with Salesforce Life Sciences Cloud if you are unsure how to configure or export the report. Decide which history you want to bring across before you prepare the file.

  2. 2

    Map and test the import

    Match the report’s column labels and request types to the fields and categories you will use in the new desk. Run the import’s dry run before loading records. It validates the complete file, so you can review problems first. If the import finds a conflict, it rolls back rather than partially loading the file, and it skips identical records.

  3. 3

    Review flagged history

    After loading, check which imported records need reconciliation, including their source status. Imported history remains history until you reconcile it. A record marked Closed in Salesforce does not become a local approval. Confirm that the records and their mapped details match what you intended to bring over, and separately plan for anything the report does not include.

  4. 4

    Run both desks briefly

    Keep Salesforce Life Sciences Cloud available while your team uses the new desk for a short, agreed period. Check that request ownership, dates and the administrative history you brought across are understood, and confirm how your team will handle open work during the overlap. Keep clinical answers and safety reporting with your responsible specialists and their controlled systems.

  5. 5

    Switch off Salesforce

    Retire Salesforce Life Sciences Cloud for this administrative desk only after your team has checked the imported history and can manage its requests in the new desk. Confirm that any remaining open work has an owner and a clear handover. This move does not replace wider clinical, commercial or specialist systems unless you assess them separately.

construction

Where the real effort goes

Most of the work is mapping your field labels, request types and local rules, then deciding how much history to bring and reconciling it. Attachments, signed approvals, permissions and controlled documents need a separate migration plan. If you have Enterprise DNA run the system, they handle the field mapping and history reconciliation as part of setup.

Not ready for a call?

Get your Salesforce Life Sciences Cloud switch plan by email

We will send you the step-by-step plan for moving your business off Salesforce Life Sciences 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

Choose the work you want us to take on

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo and run npm install
  2. 2 Run npm test and npm run demo
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor
  4. 4 Map a Salesforce report, test the import and reconcile your history
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your request fields, review rules and controlled-source references
  • check Your agreed Salesforce history mapped and checked
  • check Your access controls and a web front end if you need one
  • check A different stack and connections to existing systems can be scoped
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 Migration checked against your original request records
  • check Backups, operating checks and agreed connections maintained
  • check Your qualified team retains clinical and reporting responsibilities
Book a discovery call

Questions

Instead of Salesforce Life Sciences Cloud, answered

Does this replace everything in Salesforce Life Sciences Cloud? expand_more

It replaces a defined administrative desk: request ownership, dates, controlled-source references, reviews and handover evidence. We agree the scope against your actual workflow before migration. Wider clinical, commercial and specialist systems stay in place unless separately assessed.

Can our Salesforce history come across? expand_more

Yes, from a configured Details Only report. Field labels and request types need mapping to your process. The free version checks the file before loading and keeps source status as history. Attachments, signed approvals, permissions and controlled documents need a separate migration plan. Enterprise DNA does that mapping and reconciliation as part of setup.

Who writes the medical answer and handles a safety concern? expand_more

Your qualified specialists do. The desk prepares an internal cover sheet and records references to controlled responses. It does not generate medical answers, decide reportability or submit safety reports. Follow the existing specialist process immediately, then record its acknowledgement here.

What happens if a source is withdrawn after approval? expand_more

Recording a response is blocked when its source has expired or been withdrawn. An undelivered response can return for a fresh review with a new source reference. Earlier evidence stays in the history. The owner must act on any response already delivered through the existing medical process.

Can our team have its own screens and permissions? expand_more

Yes. Enterprise DNA can build the screens, verified identities, access rules and connections around your team. The free base is for a controlled operator environment and its typed reviewer labels are not identity checks. We agree the setup and ongoing operation for one setup fee, then a retainer.

Bring the renewal and a sample request

Spend 30 minutes with Sam. We look at your annual software bill, the request workflow your team runs and the records that must come across. You leave with a clear scope for an owned desk and the specialist systems it needs to sit beside.

Book a discovery call Get the free version

Medical Information for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Salesforce Life Sciences Cloud?

Get your version built