Coordinate the next care step.
Share what each role requires.
Connect care coordination events with the patient's situation, the recipient's role and the approved conditions for sharing. Begin with one bounded handover and make its processing and delivery traceable.
For care-network coordinators and healthcare IT teams, developed with clinical, information-security and privacy owners.
Connected Care Coordination
One network. Clear agreements for each participant.
A referral or handover can require repeated calls, manual status checks and separate access decisions. Each organisation needs different information for its contribution. An executable processing agreement can define which event triggers which permitted update and who handles an exception.
Patient or authorised representative
Has interests and applicable choices reflected in the agreed processing context.
Referring provider
Initiates the handover and supplies the information required for the agreed purpose.
Receiving care team
Receives information according to its verified role and relevant treatment relationship.
Coordination service
Routes acknowledgements and exceptions while limiting access to the fields required for its task.
Processes to connect
Bring processing to the data your services already use.
Keep the relevant personal context, purpose, rules and destinations in an approved definition. Connected operations use that definition as new events arrive.
Referral status to acknowledged handover
Connect a referral update to the receiving service and return an acknowledgement to the responsible coordinator.
Role change to access decision
Check the recipient's current authority and purpose before a configured disclosure, and route unclear authority to review.
Missing information to follow-up
Detect missing required fields and request a correction through the agreed channel without distributing an incomplete handover.
Example operation
See how an agreement becomes an outcome.
The same input, relevant context and approved rule version produce the same rule-based result. Changed facts or agreements can change the next result, with the applied version recorded.
1. trigger
A provider requests a status update for a patient handover.
2. context
Identify the patient reference, receiving organisation, requesting professional's role, treatment context and required information.
3. rule
Evaluate the approved sharing conditions. If authority or a required condition cannot be established, withhold the disclosure and route the request to the responsible reviewer.
4. outcome
Send only the permitted status fields to the authorised endpoint and track its acknowledgement. Clinical decisions remain with the responsible care professionals.
5. evidence
Record who requested what, the purpose and authority evaluated, the rule version and the disclosure or refusal, with access controls and an agreed evidence-retention period.
Validate late or duplicate events, unavailable destinations and rule changes before activation. Historical evidence explains the earlier decision; a new action must meet the conditions that apply when it is executed.
Rules in context · EU and Netherlands
Turn applicable requirements into explicit processing conditions.
The responsible organisation determines the applicable obligations and approves their translation into executable rules. These sources guide that work; they are not a certification of the solution.
Confidentiality and treatment context
Define the applicable basis and confidentiality conditions with the care provider. KNMG distinguishes directly involved treatment professionals from other recipients; consent is not a universal substitute for that assessment.
KNMG: medical records and confidentialityLogging requirements
Map the operation's logging and review needs to applicable requirements, including NEN 7513 where relevant. A decision trail is evidence to assess, not a claim of certification.
NEN 7513:2024EHDS readiness
EHDS implementation is phased, with key application milestones in 2029 and 2031. Assess the relevant exchange and system obligations for the intended service rather than treating the whole framework as already applicable.
European Commission: EHDS timelineSource review: 20 September 2026. Confirm the applicable requirements for your service and jurisdiction when defining the operation.
Business value
Measure the work you can remove.
Build the business case from the integrations, manual work and evidence preparation this process actually replaces. Include platform fees, implementation, validation and remaining operating costs.
Coordination effort
Measure time spent checking whether a handover arrived and chasing missing information.
Interface maintenance
Reuse agreed purpose and field rules within the participating network. Compare configuration and validation effort with the existing process.
Evidence preparation
Make disclosure and delivery decisions inspectable together. Measure the time required to review a sample with the responsible care organisation.
Start small, then expand
Prove the value in one bounded process.
Develop one referral-status handover with a healthcare partner. Begin with synthetic data, validate identity and sharing rules, then agree the conditions for a bounded operational pilot. Keep diagnosis and treatment automation outside this first scope.
This is a proposed coordination solution to validate with a healthcare partner, not a claim of a certified clinical product. Assess health-data safeguards, security standards, relevant Dutch exchange requirements and any medical-device classification for the intended use before deployment.
Define your first processAgree the baseline and acceptance criteria
- Staff time and manual contacts per handover
- Missing-field, unauthorised-request and delivery exceptions
- Time to acknowledgement and exception resolution
- Time to reconstruct a disclosure decision for review
Compare a representative period before and after. Expand only after the responsible owners accept the processing behaviour, evidence and measured value.