A rich text editor that keeps health data in your own systems
Clinical notes, discharge letters, care plans and internal policies are written in health-sector software every day. RichTextEditor runs inside your application, and content goes only where your own code sends it. Nothing goes to Richscripts.
Where it is used
Clinical notes and letters
Structured headings, tables and content templates for recurring documents such as referral or discharge letters.
Care plans and policies
Long documents with tables, collapsible headings and tracked review before a policy is published.
Patient-facing information
Readability statistics help keep leaflets and portal text at a plain-language level.
Internal knowledge bases
Mentions, bookmarks and templates for team documentation that stays on your intranet.
Features that matter here
All of these are in every license. Each card links to the documentation, so you can check how it works before you commit.
Self-hosted runtime
The editor is a script in your application. There is no required cloud service, telemetry endpoint or Richscripts proxy.
Security and procurement →Uploads to your storage
Images and attachments go to your own upload handler, with type and magic-byte checks, size limits and per-user folders.
Image storage →AI only with a provider you choose
AI is off until you connect a resolver. You can point it at a model hosted on your own network, so no text leaves your infrastructure.
AI usage and pricing →Content templates
Predefined documents (letters, note structures) that authors start from, so required sections aren’t forgotten.
Content templates →Readability statistics
Grade level and reading-ease scores computed in the browser for patient-facing text.
Readability statistics →HTML sanitization
Pasted and loaded content is cleaned through a configurable sanitizer before it reaches your database.
Configuration reference →What the editor does not do for you
We would rather you find the limits here than during an audit.
- RichTextEditor is a software component, not a regulated medical device or a compliance product. HIPAA, GDPR and national health-data rules apply to your whole system: hosting, access control, logging, retention and agreements with any AI provider.
- Richscripts does not sign business associate agreements, because no patient data reaches Richscripts.
- If you connect a cloud AI provider, its terms and data-retention policy apply to the text you send. Use a self-hosted model or keep AI off where that isn’t acceptable.
- No independent security certification or VPAT is currently published. Send your security questionnaire, and we will say which controls ship and which are your responsibility.
Evaluation checklist
Confirm with your security team that content is only sent to your own endpoints (watch the network tab during a test).
Configure the sanitizer and upload validation for your storage.
Keep AI off, or point it at a provider covered by your data-processing agreements.
Review the security overview and send your questionnaire.
For a full evaluation plan, see the evaluation checklist.
Customer stories
We only publish customer stories that the customer has agreed to, and none from this sector is published yet. If you use RichTextEditor in healthcare, tell us how. We will write it up with you and publish it only after you approve it.
Related
Security and procurement · Production operations · Enterprise licensing · Other sectors: Education, Government
Try it with your own documents
Perpetual licenses from $129, one-time. Every feature in every license.