Getting clinical work out of notes and into Salesforce
Two contracts across a live clinical org: Flow development so physicians and staff could document encounters properly, then Lightning Web Component work spanning multiple objects.
- Practice
- Salesforce, Flow and Lightning Web Components
- Period
- 2025
- Client rating
- 5.0 out of 5
Documentation that clinicians will actually complete
The first brief was to modify and create Flows for physicians and staff to document encounters, medical history, recommendations and products.
Clinical documentation fails on friction. Every extra screen is a note that gets finished later, or not at all, so the Flow work was as much about the order of the questions as the records behind them.
- Encounter documentation for physicians and staff
- Medical history capture against the patient record
- Recommendations and products recorded in the same pass
- the Flow contract alone
Then the components on top
The second contract spanned multiple objects and required development with Lightning Web Components, working with existing data alongside new structures being introduced.
Projects like this fail on the seam between old and new data, so the early work was mapping what each object already carried before writing a component against it.
Consultation before build
The client opened with a consultation to agree scope and next steps rather than handing over a fixed spec. That kept the component set small: every LWC had to justify itself against configuration that already worked.
Outcome
Both contracts rated 5.0, with clinical encounters now documented inside Salesforce rather than around it.
Have a similar problem?
Book a free 30 minute audit. We map what is broken, what it costs you and what the fix takes.
