Healthcare
Nedap ONS
Nedap Ons is a software suite supporting the care process — according to the supplier from intake to admission and from recording to billing, on site or on the move. It is used in nursing and home care, disability care, mental health care and domestic support, and comprises components for record keeping, care logistics such as diary, roster and scheduling, administration such as invoicing and chain messaging, and a client portal. Ons occupies a distinct place on this list: every other source here is public, this one is not. It is a care organisation's own system.
Go to the publisher’s websiteWhich products consult this source
ZIA — Reference information
The source is used as a reference.
Availability depends on your organisation’s configuration and access rights.
What this source does not give you
There is nothing in Ons that we can consult on our own initiative. A connection requires separate configuration and authorisation from the care organisation, and that organisation decides in its own access management who may see which data. Without such a connection ZIA at most refers to Ons as the system in which something is recorded; it does not read from it. The data remains the care organisation's — we do not decide which fields are exposed, or to whom.
Frequently asked questions
- Does ZIA read our Ons records by default?
- No. Without an explicitly configured connection there is no link whatsoever between ZIA and a care organisation's record system. Ons appears in our source list as a reference: ZIA can state that a given item belongs in the care record without having seen that item. A connection is a separate, deliberate step taken by the care organisation itself.
- What is needed to establish a connection?
- Two things, and both belong to the care organisation. First, permission: the organisation must want the connection and formally authorise it. Second, configuration: the access management in Ons records which data is made available under which rights. Together these set the scope. We add no access of our own and cannot widen it; whatever is not in the configuration does not exist as far as we are concerned.
- Which sectors is Ons intended for?
- The supplier names four domains: nursing, care and home care; disability care; mental health care; and domestic support. That explains why the system is relevant in our care context: in those sectors it is a widely used place where clinical recording and care logistics sit in the same system.
- What does Ons contain functionally?
- According to the supplier: record keeping with components for the health record, medication, wound care, quality monitoring, clinimetrics and group care; care logistics with diary, roster, scheduling, capacity management and care pathways; administration with a financial dashboard, invoicing, capacity and occupancy and chain messaging; plus mobile use, messaging, a client portal, access management and an employee portal. For a connection the access management is what matters most: that is where the scope is actually set.
- Why does a supplier system sit among public sources?
- Because the source list shows where answers can come from, and not every question in care has a public answer. For a question about a client's situation the record is where the answer lives — not a guideline and not a policy rule. Naming Ons explicitly makes that boundary visible: what comes from a public source we can show and cite; what sits in the record stays with the care organisation unless it configures a connection itself.