Clinical boundary
CORE supplies organisational context; it does not replace qualified clinical judgment or create clinical policy.
Assembling route context
Loading…
Context for Aged care
Care guidance changes with facility, authority and time.
A procedure can be relevant, properly cited and still be wrong for this team today. CGI assembles the organisational state around the question before an AI answer reaches care work.
Illustrative scenarioCORE / private beta
A consequential aged care decision reaches the next corner while authority, effective time and retained conflict shape the evidence packet.
Static motion alternativeAged care / context field
01 / The context failure
Relevance is not enough.
Care organisations do not have one timeless corpus. Facility scope, role, procedure lineage and the moment being asked about all change what “current guidance” means.
What retrieval seesTwo relevant sourcesWhat CGI must resolveScope · authority · time
Interactive scenario / illustrative data
Which source should the AI use?
A team asks for the current escalation threshold after a revised procedure took effect. Both sources mention the same workflow. Which one should survive?
No source selectedRelevance alone cannot settle it.
Choose either source. The evidence path, not visual position, will explain what applies and why.
Conceptual walkthrough using authored example data. Not a customer record, product screenshot or legal determination.
02How CORE assembles it
The organisational state travels with the question.
This is the product logic the scenario activates, not a claim that the workflow is deployed at a named organisation.
- Stage
Infer facility and role
Activate the care domain, requester role, facility boundary and requested date.
- Stage
Retrieve both states
Bring the current candidate and its predecessor together instead of letting wording decide.
- Stage
Read authority and time
Inspect who approved the revision, what it supersedes and when it became effective.
- Stage
Pack with the conflict
Hand off the current instruction while retaining the prior source and reason it did not win.
03Trust before rollout
Three boundaries the pilot must name.
The sector does not supply these answers automatically. The organisation’s accountable people and systems define them.
Permission boundary
Resident, workforce and clinical sources require explicit identity and source-system controls in any pilot topology.
Evidence boundary
The scenario is illustrative. Loriq has an active pilot relationship with an Australian retirement-living community; no product outcome or workflow deployment is represented here.
Design partnership / Aged care
Bring the procedure conflict your team keeps resolving by hand.
Start with one question, a bounded source slice and explicit success, access and claim boundaries.
Build with Loriq