Start with the actual work
Walk through a de-identified example: what the family is asked to do, which source they need and what a completed handoff would mean.
For pediatric cancer support organizations
A family should not have to become the handoff between every person trying to help.
Your team may help a family find transport, understand where to ask for support or prepare for another visit. Between your conversations, that family still carries the clinic papers, practical requests and decisions about what to share with whom.
See a situation-specific handoff ↓For parents and guardians, and the organizations supporting them.
The relationships your team has built are part of the support. A useful tool should respect that work and the family’s choices, while making one concrete handoff easier to follow—not make you replace a trusted conversation with a new system.
Explore the proposed support ↓How we could help — subject to validation
Let’s test one handoff with your team before promising a platform.
Choose the relationship deliberately
Referring a family, sponsoring access and staff accessing records are separate arrangements. A referral alone grants no access.
Define a bounded pilot together
Agree scope, family permission, appropriate records, adolescent privacy, staff roles and success criteria before any live pediatric use. No integration or organization dashboard is promised here.
Discuss a pediatric cancer pilot →
Let’s discuss fit before sharing records.
Illustrative handoff · Invented people and excerpts
One proposed transport handoff. No assumption of access to oncology records.
Invented family request
We need help getting to the next clinic visit. Please discuss the practical arrangements with us.
Invented support-team coordination note
Confirm which adult is arranging the ride and how the family will hear the result. Record access would require a separate authorized decision.
- The family’s practical request, in their words
- Who would own the next coordination step
- What confirmation the family would receive
What becomes clearer
A family’s request, a named practical responsibility and a confirmation step can be discussed separately from access to clinical records.
Bring a de-identified example to a conversation with Vijay. Do not send child health information. This page is a private partnership concept, not an active pediatric pilot or a signed partner program.
An explanatory example, not a generated record or treatment instruction.
Before you begin
A few good questions.
Does referring a family let our staff see their information?
No. Referral, sponsorship and access are separate. Any access needs appropriate authority, family permission and a supported product path.
Is there a pediatric organization plan or dashboard today?
This page does not promise either. Scope, readiness, commercial terms and any staff-access workflow need to be agreed and validated before a pilot.
Who can see care information?
A referral or family relationship does not grant record access. Record connections and invitations require appropriate authority and scoped permission. Dekona does not contact doctors or pharmacies for you and does not replace your clinicians.
Understand fit first.
Pediatric permissions, adolescent privacy, connections and clinical behavior need validation before a pediatric workflow is offered. No records are requested here. Referrals, sponsorship and record access are separate decisions.
Contact links open your email app. Please leave out child health information.
Helpful resources for this situation
NCI: Support for Families—Childhood Cancer ↗HHS: Personal Representatives and Minors ↗