Capture
Create the controlled record.
Uriyel / 03
Shared architecture
Uriyel Core is the common system logic beneath SiteWorks and Clinical Research. It establishes how identity, responsibility, records, evidence, decisions and reporting remain connected.
System logic
The record only works if responsibility stays attached to it.
Core is designed around a simple premise: information is less useful when identity, authority, ownership and evidence are separated from the action or decision they describe.
Identity
Who is acting or viewing the record?
Role
What authority or responsibility does that person or team hold?
Record
What happened, changed, was observed or now requires attention?
Ownership
Who carries the next action, review or escalation?
Evidence
What authorised information supports the current position?
Decision
What was accepted, rejected, escalated or left open?
Report
What does the authorised viewer need to understand now?
Architecture sequence
One repeatable operating discipline.
Different applications can expose different interfaces without abandoning the same core sequence.
Own
Assign responsibility.
Evidence
Attach support and provenance.
Decide
Record outcome or escalation.
Report
Expose the current position.
Applications
Core stays underneath. Applications stay understandable.
Uriyel does not sell clients an abstract platform and ask them to invent the use case. Each application has a defined operating environment and boundary.
01 / SiteWorks
Projects and facilities.
People, issues, actions, evidence, decisions, handover and reporting around an active project environment.
02 / Clinical Research
Research operations.
Approved study information, workflow actions, controlled updates and provenance for authorised research-team use.
Commercial delivery