Skip to content
StaryaAI
PortuguêsEnglish

Interactive example · fictional data

Several tests. One journey that needs to fit.

Explore a test scheduling engine that combines sequence, intervals, site and times, with a separate response for each item.

Conceptual demonstration. It does not represent a customer case or prove available features.

Illustrative journey · no system is accessed

Build a compatible test itinerary and check each booking.

Example options
CENTRAL SITE

Test A

9:00 AM → 9:20 AM

40 min

Interval between items

Fictional minimum: 30 min
SAME SITE

Test B

10:00 AM

Proposed times · no new reservation or confirmation at this stage.

  1. 01Request
  2. 02Rules
  3. 03Itinerary
  4. 04Bookings
  5. 05Confirmation

Step 1 of 5 · Exploring

Confirm the items

The request contains tests A and B. Items extracted from a document must be checked; the example does not select tests or interpret clinical indications.

Example inputs, parameters and limits

Inputs

  • Tests A and B confirmed by the person
  • Catalog and sequencing rules
  • Availability at the site and in the schedules

Fictional parameters

  • A: 09:00–09:20; B: 10:00 or 09:30
  • Fictional minimum interval: 30 minutes after A
  • This is not a clinical protocol or recommendation
  • A reservation, when available, is not a confirmation
Read the full reference journey

The steps below explain a possible scenario; they do not replace the current exploration state.

  1. Request. The request contains tests A and B. Items extracted from a document must be checked; the example does not select tests or interpret clinical indications.
  2. Rules. The fictional catalog requires A before B and a minimum operational interval of 30 minutes after A ends. Preparation rules would come from content validated by the institution.
  3. Itinerary. A ends at 09:20; B starts at 10:00. The 40-minute interval meets the fictional rule and both items are at the same site. The person still needs to accept the proposal.
  4. Bookings. The person accepted the itinerary. The schedule confirmed A, but there is no response for B. The package remains partially confirmed: do not repeat A or announce that everything is booked.
  5. Confirmation. A check at the destination also found confirmation for B. The summary includes both references, the site and recorded instructions. No test was performed by the prototype.

How this work continues

NebulaWorks

Brings together the work, owners, pending items and process artifacts.

NebulaOS and integrations

Supports context, integrations and controls at the points defined by the deployment. Confirmation comes from the destination system.

Starya / FDE

Investigate incompatible combinations and partial confirmations to improve the journey.

Features, rules and integrations must be confirmed for each deployment.

Prepare this workflow with your team →