Cognixoft
Talk to us
MenuClose
Explore Cognixoft

Products, people & possibilities.

Let’s move forward

Have something in mind?

Talk to us
Person-directed products / Cognixoft Access

Cognixoft Access

Help organisations respond to the person.

A receiving-side direction for acknowledging selected preferences and assigning agreed actions. Local examples must preserve the person’s sharing choices and organisation boundaries.

Open the local example Discuss this direction

Working names and proposed scope. Local examples use fictional information; planned modules are not implemented or offered for delivery.

01
Local prototype

Preferences receiving workspace

Receive only the preference view the person authorised for the intended recipient.

Example output
A local received view with source and access state.
First scope
Review an explicitly selected fictional profile view and acknowledge receipt through the local foundation.
Readiness
Local access example only. Server-side permissions and revocation must be tested; no external recipient is contacted.
Try this workflow
02
Local prototype

Adjustment delivery tracker

Record a response, a responsible role and the person’s review of an agreed arrangement.

Example output
A fictional adjustment action and review record.
First scope
Move one shared sample request through acknowledged, planned and reviewed states with clear responsibilities.
Readiness
Local workflow example. It does not guarantee an arrangement, determine entitlement or replace a service’s responsibilities.
Try this workflow
03
Planned module

Accessible journey builder

Create maintained previews for a defined clinic, campus, venue or service journey.

Example output
A sourced arrival-to-departure preview with an update owner.
First scope
Build one fictional journey with optional images, contact details and maintenance dates.
Readiness
Planned. Real environments need verified content, rights, testing and update responsibilities.
04
Planned module

Accessible content studio

Prepare reviewed plain-language, visual, audio and printable versions of owned information.

Example output
A linked format set with review and source details.
First scope
Create two versions of an owned non-clinical notice and retain the original for comparison.
Readiness
Planned. Assess meaning, rights and accessibility with intended users before publishing.
05
Planned module

Integration toolkit

Connect approved preference and adjustment workflows to existing systems using explicit permissions.

Example output
A proposed field map, permission contract and test plan.
First scope
Map a small fictional preference selection to a mock receiver without external connectivity.
Readiness
Planned. No live API, institutional integration or interoperability certification is supplied.

Related existing concepts.

The existing software family keeps its own purpose and availability.