Appointment / Reservation Event
Represent a proposed, held or confirmed allocation of time, capacity, service, place or resource among participants without owning availability, actual encounter, service order or payment lifecycles.
Bundle → Layer → Finding → Questions Filled
6 bundles · 12 layers · 24 findings · 72 questions
Booking definition, identity and boundary Defines the scheduled allocation and its authoritative identity.
Concept, type and instance identity
Separates appointment and reservation semantics from each booking instance and representation.
Appointment, reservation, hold, event and encounter distinction
Definition, inclusion and exclusion rules, planned allocation kind and external actual-occurrence reference.
- What identity, type, role, scope, version and values define appointment, reservation, hold, event and encounter distinction? identity
- Which authority, source, observation, evidence and event or effective time support appointment, reservation, hold, event and encounter distinction? evidence
- How is appointment, reservation, hold, event and encounter distinction validated, shared, changed, contested, corrected and retained? validation
Booking identifier, type, version, channel, source and lineage
Authoritative booking ID, local and external IDs, class, profile version, booking channel, source system and predecessor or successor.
- What identity, type, role, scope, version and values define booking identifier, type, version, channel, source and lineage? definition
- Which authority, source, observation, evidence and event or effective time support booking identifier, type, version, channel, source and lineage? authority
- How is booking identifier, type, version, channel, source and lineage validated, shared, changed, contested, corrected and retained? interoperability
Purpose, request and preferences
Captures why allocation is sought and the bounded request that preceded it.
Requester, purpose, service need, priority and request event
Requester reference, stated purpose, requested service or resource, priority, referral or order reference and request provenance.
- What identity, type, role, scope, version and values define requester, purpose, service need, priority and request event? relationship
- Which authority, source, observation, evidence and event or effective time support requester, purpose, service need, priority and request event? temporal
- How is requester, purpose, service need, priority and request event validated, shared, changed, contested, corrected and retained? access
Preferred time, location, participant, resource and flexibility
Requested windows, time zone, acceptable locations, participants, resources, duration, flexibility and alternatives.
- What identity, type, role, scope, version and values define preferred time, location, participant, resource and flexibility? requirement
- Which authority, source, observation, evidence and event or effective time support preferred time, location, participant, resource and flexibility? decision
- How is preferred time, location, participant, resource and flexibility validated, shared, changed, contested, corrected and retained? exception
Time, recurrence, availability and capacity Defines the promised interval and references the external availability from which it was allocated.
Temporal commitment and recurrence
Represents one interval or a recurrence template with explicit exceptions.
Start, end, duration, time zone, window and deadline
Planned start and end, duration, offset, named time zone, permissible window, arrival window, hold expiry and response deadline.
- What identity, type, role, scope, version and values define start, end, duration, time zone, window and deadline? ownership
- Which authority, source, observation, evidence and event or effective time support start, end, duration, time zone, window and deadline? provenance
- How is start, end, duration, time zone, window and deadline validated, shared, changed, contested, corrected and retained? privacy
Recurrence template, occurrence identity, exception and override
Series ID, recurrence rules and dates, occurrence ID, excluded instances, overrides and series versus occurrence changes.
- What identity, type, role, scope, version and values define recurrence template, occurrence identity, exception and override? classification
- Which authority, source, observation, evidence and event or effective time support recurrence template, occurrence identity, exception and override? quality
- How is recurrence template, occurrence identity, exception and override validated, shared, changed, contested, corrected and retained? security
Schedule, slot, capacity and conflict
References availability evidence and preserves the allocation decision that consumed it.
Schedule, slot, availability observation and freshness reference
External schedule and slot IDs, availability result, query constraints, source revision, observed time and freshness.
- What identity, type, role, scope, version and values define schedule, slot, availability observation and freshness reference? composition
- Which authority, source, observation, evidence and event or effective time support schedule, slot, availability observation and freshness reference? measurement
- How is schedule, slot, availability observation and freshness reference validated, shared, changed, contested, corrected and retained? validation
Capacity, quantity, hold, allocation, overbooking and conflict
Requested and allocated quantity, unit, capacity class, hold, remaining capacity observation, overbooking flag and conflict result.
- What identity, type, role, scope, version and values define capacity, quantity, hold, allocation, overbooking and conflict? state
- Which authority, source, observation, evidence and event or effective time support capacity, quantity, hold, allocation, overbooking and conflict? lifecycle
- How is capacity, quantity, hold, allocation, overbooking and conflict validated, shared, changed, contested, corrected and retained? retention
Parties, resources, service and place Binds external actors and allocatable subjects to booking roles.
Organizer, requester, provider and participants
Separates booking responsibility, beneficiary and participation obligations.
Organizer, provider, requester, customer, beneficiary and booking agent
External party references, role, authority, on-behalf-of relationship and contact endpoint.
- What identity, type, role, scope, version and values define organizer, provider, requester, customer, beneficiary and booking agent? identity
- Which authority, source, observation, evidence and event or effective time support organizer, provider, requester, customer, beneficiary and booking agent? evidence
- How is organizer, provider, requester, customer, beneficiary and booking agent validated, shared, changed, contested, corrected and retained? validation
Participant role, requirement, status, response, delegation and attendance claim
Participant or actor reference, required or optional role, response requirement, accepted or declined status, delegation and separately sourced attendance assertion.
- What identity, type, role, scope, version and values define participant role, requirement, status, response, delegation and attendance claim? definition
- Which authority, source, observation, evidence and event or effective time support participant role, requirement, status, response, delegation and attendance claim? authority
- How is participant role, requirement, status, response, delegation and attendance claim validated, shared, changed, contested, corrected and retained? interoperability
Reserved subject, service, resource and location
States what is allocated and the conditions needed for use.
Service, product, activity, order, referral and fulfilment target
Reserved or scheduled subject, requested service, product or activity, external order or referral and intended fulfilment target.
- What identity, type, role, scope, version and values define service, product, activity, order, referral and fulfilment target? relationship
- Which authority, source, observation, evidence and event or effective time support service, product, activity, order, referral and fulfilment target? temporal
- How is service, product, activity, order, referral and fulfilment target validated, shared, changed, contested, corrected and retained? access
Resource, place, virtual endpoint, accessibility, equipment and preconditions
External resource and location references, room or device, online endpoint, attendance mode, accessibility needs, equipment and prerequisites.
- What identity, type, role, scope, version and values define resource, place, virtual endpoint, accessibility, equipment and preconditions? requirement
- Which authority, source, observation, evidence and event or effective time support resource, place, virtual endpoint, accessibility, equipment and preconditions? decision
- How is resource, place, virtual endpoint, accessibility, equipment and preconditions validated, shared, changed, contested, corrected and retained? exception
Negotiation, confirmation, lifecycle and change Represents proposals, responses and append-only booking transitions.
Proposal, response and confirmation
Preserves the revision each party saw and the basis on which the booking became confirmed.
Proposal, offer, counterproposal, revision, sequence and expiry
Proposed allocation, proposing actor, revision and sequence, response deadline, expiry and relation to previous proposal.
- What identity, type, role, scope, version and values define proposal, offer, counterproposal, revision, sequence and expiry? ownership
- Which authority, source, observation, evidence and event or effective time support proposal, offer, counterproposal, revision, sequence and expiry? provenance
- How is proposal, offer, counterproposal, revision, sequence and expiry validated, shared, changed, contested, corrected and retained? privacy
Participant response, confirmation basis, commitment and pending party
Response actor, role and revision, accepted, declined, tentative or needs-action state, confirmation rule and outstanding responses.
- What identity, type, role, scope, version and values define participant response, confirmation basis, commitment and pending party? classification
- Which authority, source, observation, evidence and event or effective time support participant response, confirmation basis, commitment and pending party? quality
- How is participant response, confirmation basis, commitment and pending party validated, shared, changed, contested, corrected and retained? security
State transition, reschedule and outcome assertion
Keeps plan lifecycle separate from observations of what happened.
Proposed, held, pending, confirmed, waitlisted, arrived and checked-in event
Typed status event, prior and next state, actor, authority, reason, event time, effective time and evidence.
- What identity, type, role, scope, version and values define proposed, held, pending, confirmed, waitlisted, arrived and checked-in event? composition
- Which authority, source, observation, evidence and event or effective time support proposed, held, pending, confirmed, waitlisted, arrived and checked-in event? measurement
- How is proposed, held, pending, confirmed, waitlisted, arrived and checked-in event validated, shared, changed, contested, corrected and retained? validation
Modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event
Change scope, prior and new values, authority, reason, original time, release action, no-show or fulfilment assertion source, successor and notification.
- What identity, type, role, scope, version and values define modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event? state
- Which authority, source, observation, evidence and event or effective time support modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event? lifecycle
- How is modify, reschedule, cancel, expire, no-show, fulfil, correct and supersede event validated, shared, changed, contested, corrected and retained? retention
Terms, commerce, communications, evidence and provenance Records booking-specific terms and traceability while referencing external commerce, message and evidence masters.
Terms, fees, payment and entitlement references
Connects the booking to the terms that govern confirmation, use and release.
Booking, hold, cancellation, no-show, change and refund terms
Applicable policy versions, acceptance, hold deadline, cancellation window, change rules, no-show terms, refund rule and jurisdiction.
- What identity, type, role, scope, version and values define booking, hold, cancellation, no-show, change and refund terms? identity
- Which authority, source, observation, evidence and event or effective time support booking, hold, cancellation, no-show, change and refund terms? evidence
- How is booking, hold, cancellation, no-show, change and refund terms validated, shared, changed, contested, corrected and retained? validation
Price, deposit, payment, refund, ticket, membership and entitlement reference
Quoted price and currency, external price specification, deposit, payment, refund, ticket, membership and entitlement IDs and status observations.
- What identity, type, role, scope, version and values define price, deposit, payment, refund, ticket, membership and entitlement reference? definition
- Which authority, source, observation, evidence and event or effective time support price, deposit, payment, refund, ticket, membership and entitlement reference? authority
- How is price, deposit, payment, refund, ticket, membership and entitlement reference validated, shared, changed, contested, corrected and retained? interoperability
Communications, evidence, quality and provenance
Makes notices, source observations and transformations attributable.
Invitation, confirmation, reminder, change, cancellation and delivery receipt
External message references, audience, purpose, channel, sender, requested response, sent, delivered and acknowledged times and errors.
- What identity, type, role, scope, version and values define invitation, confirmation, reminder, change, cancellation and delivery receipt? relationship
- Which authority, source, observation, evidence and event or effective time support invitation, confirmation, reminder, change, cancellation and delivery receipt? temporal
- How is invitation, confirmation, reminder, change, cancellation and delivery receipt validated, shared, changed, contested, corrected and retained? access
Source observation, evidence, provenance, confidence, conflict and quality
Source system and revision, responsible agent, generation or derivation activity, observation and knowledge times, confidence, conflict and validation result.
- What identity, type, role, scope, version and values define source observation, evidence, provenance, confidence, conflict and quality? requirement
- Which authority, source, observation, evidence and event or effective time support source observation, evidence, provenance, confidence, conflict and quality? decision
- How is source observation, evidence, provenance, confidence, conflict and quality validated, shared, changed, contested, corrected and retained? exception
Interoperability, access, retention and agent operations Provides loss-aware projections and guarded autonomous operations.
Validation, concurrency and interoperability
Checks semantic integrity and maps only under pinned profiles.
Availability, capacity, participant, time-zone, transition and concurrency validation
Validation checks, expected head or sequence, idempotency key, stale response detection, conflict resolution and structured errors.
- What identity, type, role, scope, version and values define availability, capacity, participant, time-zone, transition and concurrency validation? ownership
- Which authority, source, observation, evidence and event or effective time support availability, capacity, participant, time-zone, transition and concurrency validation? provenance
- How is availability, capacity, participant, time-zone, transition and concurrency validation validated, shared, changed, contested, corrected and retained? privacy
FHIR, iCalendar, JSCalendar, Schema.org and TMF646 crosswalk
Pinned source and target versions, field and state mappings, recurrence behavior, omissions, conflicts and round-trip class.
- What identity, type, role, scope, version and values define fhir, icalendar, jscalendar, schema.org and tmf646 crosswalk? classification
- Which authority, source, observation, evidence and event or effective time support fhir, icalendar, jscalendar, schema.org and tmf646 crosswalk? quality
- How is fhir, icalendar, jscalendar, schema.org and tmf646 crosswalk validated, shared, changed, contested, corrected and retained? security
Views, access, retention and safe agent operation
Separates audience views and controls mutation, deletion and evidence retention.
Public, participant, requester, provider, operator, auditor and agent view
Audience, purpose, authority, included fields, redactions, contact and endpoint protection, freshness and expiry.
- What identity, type, role, scope, version and values define public, participant, requester, provider, operator, auditor and agent view? composition
- Which authority, source, observation, evidence and event or effective time support public, participant, requester, provider, operator, auditor and agent view? measurement
- How is public, participant, requester, provider, operator, auditor and agent view validated, shared, changed, contested, corrected and retained? validation
Retention, legal hold, disposition, agent authority, idempotency and audit
Retention trigger, hold, disposition authority, minimum tombstone, delegated operation, expected revision, rollback and audit evidence.
- What identity, type, role, scope, version and values define retention, legal hold, disposition, agent authority, idempotency and audit? state
- Which authority, source, observation, evidence and event or effective time support retention, legal hold, disposition, agent authority, idempotency and audit? lifecycle
- How is retention, legal hold, disposition, agent authority, idempotency and audit validated, shared, changed, contested, corrected and retained? retention
Classifiers Filled
- Family
- World Models
- Category
- Activities and processes
- Entry kind
- aggregate
- Navigation path
- NAV.ACT.APT
- Domain
- ACT.APT
- Industry
- Cross-industry
- Tags
- appointmentreservationeventact.apt
What it is Filled
Owns booking identity and lineage, request purpose and preferences, planned interval and recurrence, allocation references, booking-scoped party roles and responses, proposals and confirmation basis, booking lifecycle events, terms references, booking-specific communications and evidence, projections, access and retention. Party, resource, service, schedule, slot, place, order, payment, entitlement, message, encounter, generic evidence and audit masters remain external.
In scope
- Appointment and reservation identity, request, proposed or held allocation, participants, service or resource references, time, recurrence and capacity observation
- Proposal, response, confirmation, waitlist, modification, reschedule, cancellation, expiry, no-show and fulfilment assertions with authority and lineage
- Terms and commerce references, communications, provenance, validation, role views, privacy, retention, interoperability and safe agent operations
Out of scope
- Party, resource, service, location, schedule, slot, order, payment, entitlement, message, encounter, generic evidence or audit-log master lifecycle
- Proving actual attendance, service performance, resource availability, payment settlement, legal entitlement or party identity merely from booking status
- Implementing scheduler, optimization, routing, conferencing, payment, messaging or sector-specific protocol engines and claiming lossless cross-format equivalence
Why it exists Filled
Represent a proposed, held or confirmed allocation of time, capacity, service, place or resource among participants without owning availability, actual encounter, service order or payment lifecycles.
Distinguishing features Filled
- Models the commitment to meet or use a resource at a planned time, not the availability slot or the actual encounter.
- Separates temporary holds, acceptance, confirmation, attendance and fulfilment as distinct states.
- Keeps reschedules and cancellations as appended events with lineage.
- References orders, payments and messages instead of owning them.
What robots and AI may and may not do Filled
Must not
- Confirm a booking without the required participant or provider acceptance.
- Hold slots indefinitely or block others' access to scarce resources.
- Record a no-show or fulfilment without evidence.
- Rewrite a past booking instead of appending a change.
- Disclose booking details that reveal health, legal or other sensitive purposes.
Only with a human decision
- Cancelling bookings that carry fees, penalties or care consequences.
- Overbooking or prioritising between competing requesters for scarce resources.
May
- Search availability and place a temporary hold for a requester.
- Propose times and collect participant responses.
- Send reminders and confirmations through approved channels.
- Release expired holds.
Moral aspects Filled
- Booking purpose can reveal health, legal or personal matters and needs protection.
- Allocation of scarce slots must be fair and not favour automated bookers over people.
- Missed appointments can harm patients or clients; cancellations need clear notice.
Who is affected
- People who book and attend
- Service providers and staff
- Others waiting for the same resources
Owners Filled
Steward
Dimension identity, owner, booking governance authority and schedule, privacy and records stewards
Roles
- Booking owner or requester
- States need, preferences and authorized change or cancellation requests.
- Organizer or provider
- Owns allocation confirmation, delivery coordination and source-qualified outcome assertions.
- Participant or beneficiary
- Responds for an authorized role and receives minimum necessary booking details.
- Schedule and resource steward
- Maintains external availability, capacity, holds and release integrity.
- Booking service operator
- Maintains booking state machine, concurrency, notices and recovery.
- Privacy and records steward
- Controls protected details, retention, legal hold, disposition and auditability.
- Interoperability steward
- Owns pinned projections, mappings, loss reports and compatibility tests.
Links to other meta-models Filled
references
- Party, Person, Organization, Agent and Role models - Resolve requester, customer, beneficiary, organizer, provider and participant identities and authority.
- Service, Resource, Place, Schedule, Slot and Availability models - Resolve the allocatable subject and source-qualified capacity without importing its master lifecycle.
- Order, Payment, Entitlement, Message, Encounter, Evidence and Audit models - Connect commerce, notices, actual occurrence and provenance while preserving ownership boundaries.
aligned
- HL7 FHIR R5 Appointment, AppointmentResponse, Schedule and Slot - Project healthcare scheduling roles, lifecycle, recurrence and availability semantics.
- iCalendar, iTIP, JSCalendar, Schema.org and TMF646 - Project calendar, reservation and service-appointment representations with declared loss.
neighbor
- Schedule / Slot / Availability - The booking references source-qualified availability and allocated slots; schedules and slots keep their own identity, capacity and availability lifecycle.
- Encounter / Event occurrence - The booking describes planned allocation; an actual encounter or real-world event keeps separate observations and outcome evidence.
- Order / Payment / Entitlement - The booking can reference commercial or authorization records, but confirmation does not itself settle payment or grant entitlement.
- Party / Resource / Service / Place - Booking-scoped roles and allocation references are owned here; external subject masters and their lifecycles are not copied.
- Calendar message / Notification - The booking owns the intended state and records communication references; delivery of an invitation or confirmation is not acceptance.
parent
- WM-ACT-018
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Authoritative master-system booking or reservation identifier qualified by source and booking class.
- Governed globally resolvable calendar UID or reservation identifier with source authority.
- Dimension UUID when no authoritative or governed global identifier exists.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Filled
- A booking has a requester, participants, a planned time interval, a service or resource and a status.
- It is confused with an available slot, a calendar entry, an order or the encounter that took place.
Capabilities and actions required Filled
- Create booking request: Record a bounded request for a scheduled service, resource or place.
- Search and observe availability: Query external schedules and preserve the result and its freshness without owning availability.
- Place or release temporary hold: Record a time-limited capacity hold and later confirmation, release or expiry.
- Propose, respond and counter: Exchange revision-qualified proposals and participant responses.
- Confirm booking: Commit the allocation after required responses, terms and capacity checks.
- Modify or reschedule booking: Create a successor revision for time, participant, resource, service or location changes.
- Cancel, expire or release booking: Apply a terminal or hold-expiry transition and release allocated capacity under terms.
- Record arrival, no-show or fulfilment assertion: Attach a source-qualified observation about participation or outcome without treating status as proof by default.
- Project booking loss-aware: Map a booking to a pinned interoperability profile with explicit omissions and conflicts.
- Validate, correct, retain and audit: Run semantic checks or create a correction and authorized disposition with preserved lineage.
Hazards and failure modes required Filled
- Double booking of a resource or person.
- Time zone or daylight saving errors shifting appointments.
- Lost cancellations leaving people without service.
Standards and interfaces required Filled
- IETF iCalendar (RFC 5545) and iTIP (RFC 5546).
- IETF JSCalendar (RFC 8984).
- schema.org Reservation and Event.
- ISO 8601 date and time format.
Context of use required Filled
- Cancellation rights, deposits, refunds, no-show terms, accessibility obligations, retention and emergency access depend on jurisdiction and sector.
- Healthcare terminology and workflow from FHIR are useful structural inputs but do not make the model healthcare-specific.
- Schema.org and calendar formats support discovery and exchange but do not establish allocation authority, capacity truth or contractual effect.
Sources Filled
- FHIR R5 Appointment - Health Level Seven International
- FHIR R5 Slot - Health Level Seven International
- FHIR R5 Schedule - Health Level Seven International
- FHIR R5 AppointmentResponse - Health Level Seven International
- Internet Calendaring and Scheduling Core Object Specification - Internet Engineering Task Force
- iCalendar Transport-Independent Interoperability Protocol - Internet Engineering Task Force
- JSCalendar: A JSON Representation of Calendar Data - Internet Engineering Task Force
- Date and Time on the Internet: Timestamps with Additional Information - Internet Engineering Task Force
- Reservation - Schema.org Community Group
- Event - Schema.org Community Group
- TMF646 Appointment Management API REST Specification - TM Forum
- PROV-O: The PROV Ontology - World Wide Web Consortium
Open questions
- Review the current TM Forum appointment management specification, including any v5 profile, against the SRC-011 v4.0.1 material and reconcile state, hold and capacity semantics.
- Enumerate the field-level and state-level crosswalk between FHIR R5 Appointment and AppointmentResponse, RFC 5545 and 5546, RFC 8984 JSCalendar, Schema.org Reservation and TMF646, with a round-trip test corpus and a declared loss class per direction.
- Define a redaction and pseudonymization rule for personal data embedded in append-only proposals, responses, communications references and status events, reconciled with legal hold, tombstone minima and jurisdictional erasure rights.
- Adjudicate cross-participant disclosure: whether a participant may see other participants' response state, delegation chain, contact endpoints or virtual location, grounded in ITIP and JSCalendar participant visibility semantics.
- Specify waitlist enrollment, position, promotion, lapse and notification operations, and split the hold lifecycle authority explicitly between the booking aggregate and the slot or schedule steward.
- Develop sector booking profiles for transport, lodging, dining, healthcare procedures, court hearings and workforce dispatch, and derive the precedence rules for a confirmed booking coexisting with stale availability, a participant decline, a failed payment or a provider-side cancellation.
- Add an explicit source row for the base timestamp standard enforced by artifact_rules and confirm that named time-zone intent survives recurrence expansion after time-zone rule changes.
- No successful independent Claude or Grok result was available; later scheduling, travel, hospitality, healthcare and legal review is required before canonical promotion.
- No approved relation rows were supplied; proposed links to Encounter and to party, resource, service, location, schedule, order, payment, message, evidence and audit models remain holds.
- Sector-specific booking families such as transport, lodging, dining, healthcare procedures, court hearings and workforce dispatch require separate profiles.
- TMF646 source material used here is v4.0.1; a later TM Forum v5 profile should be reviewed when the full normative artifact is available.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-act-026-appointment-reservation-event/spec.yaml, ver-cy/world-models/card-supplements/wm-act-026-appointment-reservation-event.json