Longitudinal Women’s Health
SHIORA
Continuous health records and consent-led support connecting women, care teams and services, so information carries across life stages and care transitions.
The Customer Case
The Opportunity
The service must have a clear user and a defined role in the health journey. Any clinical use or health guidance requires its own evidence, responsibilities and regulatory assessment.
Bring a Customer PerspectiveWhat We Are Building
The Product
SHIORA is designing a continuous health-information and programme architecture across women’s life stages. It connects personal context, permissions and authorised care-team information so that transitions between services do not require the health story to begin again.
- Development Focus
- Longitudinal Women’s Health
How It Fits Together
The System
A proposed longitudinal record and support layer links information, programme navigation and care coordination under explicit clinical-safety, privacy and consent boundaries.
Critical Dependencies
- Sensitive health-data privacy and consent
- Information quality and interoperability
- Clinical and regulatory requirements for the intended use
System Architecture
How the proposed elements connect.
Longitudinal Record
Information across life stages forms the proposed record and support layer.
Navigation & Coordination
Programme navigation and care coordination connect the record to a defined user need.
Consent & Clinical Boundaries
Privacy, explicit consent and clinical-safety requirements govern access and intended use.
Conceptual system view. The development questions below set out what needs to be established.
The Next Technical Decisions
Evaluation
Information continuity, permission design and clinical safety require separate evaluation. Any health-related guidance needs evidence for its particular intended use.
Which information and support needs are poorly connected across life stages?
How can longitudinal records remain accurate, understandable and appropriately accessible?
What evidence is required for any proposed health-related guidance or clinical use?
Questions & Answers
SHIORA
FAQs
Technical scope, development requirements and ways to contribute.
Ask About SHIORAWhat Is SHIORA Intended to Connect Across Life Stages?
SHIORA is designing a continuous health-information and programme architecture that connects personal context, permissions and authorised care-team information across women’s life stages. The proposed role is continuity between information and support, so that a transition between services does not require the health story to begin again.
Who Would Use the Proposed Information and Support Layer?
The proposed context includes women managing information and support across life stages, together with authorised care teams that need continuity of context. The initial application still needs a clearly defined user, service transition and information need, with permissions determining what each participant can access.
How Does SHIORA Approach Transitions Between Services?
Transitions are central to the proposed architecture because relevant information and personal context can otherwise become disconnected as services change. SHIORA is designing a longitudinal record and support layer that would connect that context with permissions and care coordination, with accuracy and appropriate access remaining development requirements.
Why Are Personal Context and Permissions Part of the Same Architecture?
The proposed continuity depends on connecting relevant personal context without separating it from the permissions governing access to that information. SHIORA therefore treats consent, privacy and authorised care-team context as part of the architecture, rather than assuming that making a record available makes every use of it appropriate.
How Would Programme Navigation and Care Coordination Fit?
SHIORA’s proposed support layer links a longitudinal record with programme navigation and care coordination. The work is to connect relevant information and authorised care-team context across service transitions, while defining the clinical-safety, privacy and consent boundaries appropriate to that particular use.
What Would Make a Longitudinal Record Useful over Time?
A record needs to remain accurate, understandable and appropriately accessible as a person’s information and care context change. SHIORA’s evaluation asks how those qualities can be maintained over time, while information quality and interoperability are dependencies of the proposed continuity rather than outcomes that can simply be assumed.
How Do Privacy and Consent Shape Access to Information?
Sensitive health-data privacy and consent are explicit dependencies of SHIORA’s proposed information and support architecture, alongside authorised care-team access. The intended use needs to establish which information is appropriate for the relevant context, while access arrangements must be considered together with information quality and clinical-safety boundaries.
Why Is Interoperability Important to SHIORA’s Proposed Role?
The proposed service connects information and support across transitions, making interoperability a dependency alongside the quality of the information being carried forward. A useful assessment would examine whether the relevant context remains understandable and appropriately accessible between services, rather than assuming that a connected record automatically provides continuity.
What Evidence Would Be Required for a Proposed Clinical Use?
The evidence needed would depend on the specific health-related guidance or clinical use being proposed, together with its responsibilities and regulatory assessment. That requires a separate evaluation, so the information architecture alone does not establish clinical validity or support a claim about health outcomes.
What Could a Research or Information Partner Help Clarify?
A useful contribution could identify poorly connected information or support needs across life stages and help define the intended user or care context. Further discussion would need to address information quality, interoperability, consent and the evidence required for the proposed use, rather than assuming access to sensitive health data.
Engagement
Work on SHIORA
Choose the route that fits your contribution. Your enquiry will carry this venture’s name into the conversation.
Enquire About SHIORABuild the Company
Founders and venture leaders: bring the experience to own the business, product or a critical operating function.
The Founder PathwayExplore an EIR Assignment
Investigate a customer problem, product requirement or development decision. Propose a defined piece of work and a useful outcome.
Discuss an EIR AssignmentContribute a Capability
Research and industry partners: bring a test method, specialist facility, manufacturing process or real customer requirement.
Partnership PathwaysDiscuss Capital
Review the venture’s development plan, evidence, intellectual-property position and financing requirements.
Capital Partner Information