Journal systems: what they are, what they need to do, and how to choose
A journal system is the digital platform where a social care or health service records, stores and shares information about the people it works with. It brings case notes, medication, care plans, records of the support delivered and the access log together in one place — so several practitioners can work on the same case without the history falling apart.
This page covers what a journal system needs to do in social care, the requirements it has to support, what switching costs, and the questions worth putting to a supplier before you commit.
Jump to: What it is · Requirements · By service type · Legal duties · How to choose · Cost · Switching · FAQ
What is a journal system?
Journal systems are used across health and social care, but the three main categories solve very different problems. The distinction is worth knowing before you read any supplier's material — a system built for one category rarely fits another.
Electronic patient records
Used in hospitals and general practice. Built around treating illness: diagnoses, investigations, referrals and prescribing.
Electronic care records
Used in municipal home care and elderly care. Built around commissioned services, visits and functional ability.
Journal systems for social care services
Used in supported housing, residential care, social psychiatry and addiction treatment. Built around support and progress: goals, care plans, daily observations and evidence of what was actually delivered.
All three share requirements for security and traceability, but they document different things. If you need to evidence a social care intervention to a commissioner or an inspectorate, the third category is the one to look at.
What a journal system needs to do
The list below is written as a specification you can take to any supplier — not as a description of one particular system. These are the points that tend to make the difference in day-to-day use.
Case notes with version history
Who wrote what and when — and what was changed afterwards. Without version history you cannot evidence a case retrospectively.
Medication management
Lookups against an approved medicines reference, a history of as-needed doses, and a medication chart that can be read during a busy evening shift.
Care plans with goals and review
So the support and its results live in the system rather than in a spreadsheet alongside it.
Progress and outcome measurement
Change has to be visible over time — both when things improve and when they do not.
Access control and an audit trail
Who has viewed whose records. This is both a security requirement and what turns a subject access request into a manageable task.
Secure communication
With service users, families and partner agencies, without sensitive information ending up in an ordinary inbox.
Rotas and time recording
Only relevant if it replaces a system you already pay for. When it does, it removes double entry.
Data export in an open format
The feature nobody thinks about until the day they need to switch. Ask to see an actual export, not a description of one.
European hosting and a data processing agreement
Processing special category data sets requirements for where data sits and on what terms.
Journal systems by service type
Documentation requirements are not the same across social care. Four service types, and what typically sets them apart:
Supported housing
Here the daily log and a shared view of the whole house carry the weight. Handovers, medication, appointments and observations need to be readable at a glance by whoever comes on shift. Read more about rotas inside the journal system.
Social psychiatry
Care plans and slow progress matter most. Goals need to be traceable across months, and small changes need to be visible in context. Read about digital care plans in social psychiatry.
Residential care
Residential services document both the pedagogical work and the practical day, and they are closely inspected. Traceability and completeness matter more than the length of the feature list.
Addiction treatment
Treatment episodes, medication and outcome evidence have to hang together, and the results need to be presentable to the authority that made the referral.
Legal and documentation requirements
A journal system has to support the duties you already carry — it does not discharge them. These five areas are the ones your choice of system actually affects:
The duty to plan the support and review it. The system must be able to show goals, actions and follow-up together.
Record-keeping duties for registered health professionals, if you employ nurses or other registered staff. What must be recorded, and when, applies unchanged in a digital system.
The GDPR. Health data is special category data, which sets requirements for access control, logging, erasure and a data processing agreement. We have written more about GDPR in a journal system.
Inspectorate documentation requirements. The Danish social services inspectorate looks at whether the support is described and reviewed — not at which system you use, but the system decides how easily you can show it.
Joint municipal requirements where a local authority commissions the placement. Read about KKR requirements for journal systems.
New statutory requirements are built in as they arrive. Ask a supplier how they handle regulatory change — and whether it costs extra.
How to choose a journal system: seven steps
The order matters. Most services that regret a decision skipped step 4, 5 or 7.
Map what you use today
Every system, spreadsheet and paper process — and what each costs you per year. That is the figure a new system has to be measured against.
Write down what you actually have to evidence
Start from the commissioner's specification and your latest inspection report, not from supplier feature lists.
Work out who will use it
A system the night shift cannot navigate will not get used, however well it demos.
Ask for pricing in writing
Including setup, training, support and what future modules cost. Get the price adjustment terms in writing too.
Ask how you get your data back out
In what format, how long it takes and what it costs. Get the answer in writing.
Run a trial on real cases
With the staff who will use it daily — not only with the management team.
Read the licence terms before signing
Particularly the sections on ownership, termination, and what happens to your data if the supplier changes hands.
What does a journal system cost?
Pricing in this market follows three models: per user, per service user, or a flat licence independent of numbers. Which is cheapest depends entirely on the ratio between staff and places — a small service with many part-time staff and a large one with few full-time staff get very different answers from the same price list.
The biggest difference between quotes is rarely the headline price but what is included: setup, data migration, training, support, and the modules you discover you need six months in. We have compared four Danish systems that publish their prices, and the gap was wider than expected.
Switching journal systems without losing your history
Moving the data itself usually takes days, not months. It is configuration and training that take time. Plan for a period where the old system is still available for reference, and agree up front how long that access lasts.
The decisive question is whether your current supplier can produce a complete export — service users, case notes, documents and history — in a format that can be read in elsewhere. Read more about switching journal systems and getting your data out safely.
Shared hosting or your own server?
Most services run Validi on shared hosting: you log in through a browser, and we handle servers, security and updates. If you have your own IT department, or a requirement that the system sits with you, Validi also runs on your own server in Denmark or the EU at a fixed price.
Want to see it in practice?
We would rather show Validi against your own workflows than on a demo account — so you can judge whether it fits the way you already work.
Book a walkthroughFrequently asked questions about journal systems
- What is the difference between a journal system and an electronic patient record?
- An electronic patient record is used in hospital care and is built around treating illness: diagnoses, investigations and prescribing. A journal system for social care is built around support and progress: care plans, goals, daily observations and evidence of what was delivered. The two share requirements for security and traceability, but they document different things, and a patient record system rarely fits a supported housing service.
- What documentation will the commissioning authority expect?
- The authority is buying an intervention and wants to see that it was delivered. In practice the system needs to show the plan's goals, what was done to meet them, and how it went. On top of that come joint municipal requirements covering traceability and data exchange. Requirements are worded differently from one authority to the next, so work from your own specification rather than a generic list.
- How long does it take to switch journal systems?
- Moving the data usually takes days. Configuration, tailoring and training are what take time — expect weeks rather than months if the supplier has done it before. Make sure you keep reference access to the old system for a period afterwards, and get the length of that access agreed in writing.
- Can we get our data out if we want to switch again?
- That should be a requirement, not a question. Ask to see an actual export in an open format before you sign — not a description of one. Ask what the export costs and how much notice the supplier needs.
- What does a journal system cost?
- Pricing follows three models: per user, per service user, or a flat licence. Which is cheapest depends on the ratio between staff numbers and places. Most of the difference between two quotes usually sits in what is included — setup, data migration, training and support — rather than in the monthly price itself.
- Does the system have to be hosted in Denmark?
- There is no absolute requirement for Danish hosting, but processing special category data sets requirements for where and on what terms it is stored, and a data processing agreement is mandatory. Danish or European hosting makes it simpler to evidence that those requirements are met.