hackathon-check-in-app
0.9.1 - ci-build
hackathon-check-in-app - Local Development build (v0.9.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: https://hl7.no/fhir/ig/hackathon-check-in-app/ImplementationGuide/hackathon-check-in-app | Version: 0.9.1 | |||
| Draft as of 2026-11-10 | Computable Name: HackathonCheckInApp | |||
This page describes the FHIR R4 (4.0.1) data model for an event roster and attendee check-in. It documents the FHIR resources, profiles, extensions, terminology and examples used to represent those records. See Business architecture for the event use cases and the business-layer process view.
The profiles distinguish people registered for the event from people who have arrived:
ExpectedParticipant profiles Person and represents an attendee or
organizer registered for the event.CheckedInParticipant profiles Practitioner and represents an attendee or
organizer who has checked in. Practitioner is used here as an
event-specific demonstration model; it does not imply healthcare employment
or a professional credential.ExpectedParticipant uses Person for the event's advance roster. Each record
has an event-specific identifier, a name, an email address and an affiliation.
The primary track is optional. The Affiliation and PrimaryTrack extensions
carry event details that are not part of the base Person resource.
CheckedInParticipant uses Practitioner for a registered person who has
arrived. It carries the same identifying and event details as the expected
participant and requires an event role in Practitioner.qualification. The
role codes distinguish attendees from track leads; they are event roles, not
professional qualifications.
When a person checks in, Person.link.target can reference the corresponding
CheckedInParticipant. The shared event-specific participant identifier
supports identification across the two resources.
EventList is the base profile for event lists. It requires a current,
working list with an identifier, purpose and date.
RosterList represents registered people. Each entry references an
ExpectedParticipant, and List.entry.flag records the person's event
role.CheckinList represents arrivals. Each entry references a
CheckedInParticipant, and List.entry.date records the check-in time.
ManualRegistration can mark an entry that was registered manually.The relationships between the profiles are:
RosterList.entry.item ------> ExpectedParticipant (Person)
RosterList.entry.flag ------> ParticipationRole
ExpectedParticipant.link ----> CheckedInParticipant (Practitioner)
CheckinList.entry.item ------> CheckedInParticipant (Practitioner)
CheckinList.entry.date ------> Check-in time
The guide defines code systems and value sets for list purposes, participation roles and event tracks. The examples illustrate roster entries, checked-in participants and the links between them. Published examples use synthetic information only; real participant details and event records must remain private.
The Demo application page links to a browser-only version of the check-in app that uses these examples as its data.