Hi, does anyone know if reference model can support data capture and retrieval via a Rich text editor in the frontend? Or does anyone have experience of this?
A lot of EPRs using proprietary data models will capture progress notes using a Rich text editor.
In terms of persisting the text from the Rich Text Editor, if you can render it as plain text with markup, then it can be persisted the same way as the text from any Entry would be persisted. It’s just text.
Perhaps converting the RTF to MarkDown (trivial, lots of libraries can do this) would be a way to make the Rich Text formatting more portable.
I don’t think the Reference Model has direct provision for RTF or rich text elements, and it probably doesn’t need to have. If you can get the clinical progress note as a text block with a well-known formatting syntax it just persists that. Markdown has been around for 20 years but has gained a huge amount of popularity in recent years because it’s a good middle ground between complex fully formatted text formats and unformatted plain text, and LLMs speak it fluently, without wasting too many additional tokens over it. So as far as I’m concerned MarkDown is the future.
I wrote a thing called Medical Markdown a while ago, not exactly the same as what you’re asking, but aimed at using MarkDown to separate out a single block of free text into sections by parsing section headers.
Source
Demo
Video
Thanks Marcus, these are great resources… will pass this back into some of our developers for comment
There is a similar discussion here: Embedding of HTML in Markdown inside DV_TEXT