# EDFlow Docs

> Every step of your ED visit, in view. Guides for patients, families, care teams, administrators, developers and hospital IT, on the web, iPhone and Android.

- Full text: https://docs.edflow.space/llms-full.txt

- MCP server: https://docs.edflow.space/api/mcp

- Any page as Markdown: append `.md` to its URL, or send `Accept: text/markdown`.

## English

# Docs

- Getting started
  - [How a visit works](/start/how-a-visit-works): The emergency department visit from arrival to going home, as patients and family see it in EDFlow: every stage, what changes at each one, and what the family view shows.
  - [Choose your guide](/start/choose-your-guide): Find the EDFlow guide for your role: patients, family, nurses, physicians, charge nurses, registration clerks, managers, privacy officers, integration analysts, developers and hospital IT.
  - [Safety](/start/safety): The EDFlow safety model: I feel worse always sends people to staff first, delay notices never identify anyone, results are never shown, and what happens when the phone is offline.
  - [Languages and accessibility](/start/languages-and-accessibility): EDFlow in English and French, safety messages in each hospital's top languages, text up to 200%, screen readers, Dynamic Type and font scale, high contrast, reduced motion and colour-independent status.
  - [Devices](/start/devices): Which phones, browsers and screens EDFlow supports: iOS 17 and later (designed for iOS 26), Android 8 and later, current browsers with no install, and the waiting-room display.
  - [Demo](/start/demo): Try EDFlow with two fictional Ontario hospitals: what each sample visit shows, how to open the demo launcher with an invite code, and what the demo will never contain.
  - [For hospitals](/start/for-hospitals): Evaluating EDFlow for your emergency department: the pilot model, EHR options (Epic, Oracle Health, MEDITECH or manual), what IT provides, the go-live gates and the success metrics.
  - [Glossary](/start/glossary): Emergency department terms used in EDFlow (CTAS, PIA, AVS, LWBS, NPO, disposition, code, boarding) with the plain words patients see and the terms staff use.
  - [Frequently asked questions](/start/faq): Answers to common questions about EDFlow from patients, families, staff, hospital leaders and IT: results, wait times, privacy, costs to staff time, and integration.
- Patients and family
  - Patients
    - [For patients](/patients): Follow your emergency department visit on your phone with EDFlow: see where you are, who is caring for you, your tests and usual waits, ask your care team for things, and share updates with family.
    - [Sign in](/patients/sign-in): How to sign in with my card: scan the QR code on your wristband or visit card, or enter your last name, date of birth and visit code, then confirm it's you. What to do if you're locked out.
    - [App or browser](/patients/app-or-browser): Follow your visit in your phone's browser with nothing to install, or use the EDFlow app. What the first screens say, how notifications work, and what your lock screen shows.
    - [Your visit](/patients/your-visit): What the Visit screen in EDFlow shows: your current step, what happens next, the usual wait for this step, your care team, your tests, quick requests and the latest updates.
    - [Timeline](/patients/timeline): The timeline in EDFlow lists every step of your emergency visit with its time, from checking in to leaving, and what usually comes next.
    - [Care team](/patients/care-team): Who is looking after you in the emergency department: your doctor, a doctor in training, your nurse and specialists, and why some names show only a first name.
    - [Tests](/patients/tests): Follow each of your tests in EDFlow: its steps, the usual wait for this day and hour, and when results are back. You never see the results themselves; your care team talks with you about them.
    - [Wait estimates](/patients/wait-estimates): How EDFlow estimates waits in plain words: a usual range and the time 9 in 10 people are done within, based on past visits on the same day and hour. Why there is no countdown and why times can change.
    - [Delays](/patients/delays): What the delay notice and the busy-department banner in EDFlow mean, why the emergency department sometimes slows down, and what the notices never tell you.
    - [Asking your care team](/patients/requests): Send a request to your care team in EDFlow: a blanket, water, help to the washroom, an interpreter, a question, or to say you're stepping out. What "Seen by" means, reminders, limits and cancelling.
    - [If you feel worse](/patients/if-you-feel-worse): If you feel worse in the emergency department, tell a nurse or staff member in person right away. What the I feel worse button also does, what happens when you're offline or outside, and what to do after you go home.
    - [To do](/patients/to-do): Things your care team needs from you in EDFlow: samples, consent before a test, and restrictions such as nothing to eat or drink. How to mark a task done.
    - [Share with family](/patients/share-with-family): Share a live view of your emergency visit with family or friends in EDFlow: what they can and can't see, how to send the link, the device limit, and how to stop sharing at any time.
    - [Updates and notifications](/patients/updates-and-notifications): Your updates inbox, app notifications and text messages in EDFlow: what we send, what your lock screen shows (never health details), and how to change or stop them.
    - [Hospital info](/patients/hospital-info): Find washrooms, food, Wi-Fi, parking, visitor rules, interpreters and answers to common questions for the hospital you're in, and read education sheets approved by its care team.
    - [Questions for your doctor](/patients/questions-for-your-doctor): Write down questions for your doctor while you wait. The notepad in EDFlow is saved only on your phone, never sent to the hospital, and cleared when your access ends.
    - [Settings](/patients/settings): Change your language, text size, contrast, theme and notifications in EDFlow, lock the app with Face ID or fingerprint, see the phones signed in to your visit, and sign out.
    - [After your visit](/patients/after-your-visit): Your going-home summary, follow-up dates you can add to your calendar, the summary link, the short survey, and when your access to EDFlow ends after you leave the emergency department.
    - [Privacy](/patients/privacy): What EDFlow stores about your emergency visit and for how long, who can see what, why notifications never include health details, and how to keep your visit private on a shared phone.
    - [Troubleshooting](/patients/troubleshooting): Fix common problems with EDFlow during your emergency visit: no connection, information may be delayed, updates are paused, the code doesn't work, you're locked out, or too many devices.
    - [Ask the assistant](/patients/ask-the-assistant): Ask EDFlow questions about your own visit, like how long a step usually takes, who your nurse is, or where the washroom is. What the assistant can and can't do, and how it handles your messages.
  - Family and friends
    - [For family and friends](/family): Someone shared their emergency visit with you in EDFlow. What you'll see (their step, rough waits and who is caring for them), what you won't see (tests, results, location), and why.
    - [Open your link](/family/open-your-link): How to open the visit updates link someone shared with you in EDFlow: tap View updates, choose your language, the 3-device limit, and using the app instead of the browser.
    - [Updates](/family/updates): Get text or app updates when the person you're following reaches a big step, read the update history and hospital information, and use the family helper where the hospital offers it.
    - [When updates end](/family/when-updates-end): Why family updates in EDFlow stop: the person stopped sharing, the time they chose ran out, or they left the emergency department. What you see when updates end or are paused.
    - [Family questions](/family/faq): Answers for family and friends following an emergency visit in EDFlow: why you can't see test results, whether you can call the emergency department, and what to do when the link says too many devices.
- Care team
  - [Sign-in and security](/staff/sign-in-and-security): How staff sign in to EDFlow: accepting an invite, the password policy, two-step sign-in (MFA), Sign in with Microsoft, the idle lock, switching sites, sessions, and the companion app's biometric lock.
  - [Board](/staff/board): The EDFlow live board: stats row, columns, alerts, filters, saved views, bottleneck flags, keyboard shortcuts, the command palette and big-board mode.
  - [Patient detail](/staff/patient-detail): The EDFlow patient detail page: the header, the tabs (overview, tests, tasks, care team, requests, going home, sharing and access, activity), provenance of each fact, audited opening, and confidential and provisional patients.
  - [What patients see](/staff/what-patients-see): The same visit in the EDFlow staff console and on the patient's phone, side by side, so staff can answer patient questions about stages, estimates, tests and requests.
  - [Requests](/staff/requests): The EDFlow request queue: how patient requests are routed, acknowledging and resolving, service levels and escalation, the urgent I feel worse path (Going now, Can't go), the support queue and desktop notifications.
  - [Manual console](/staff/manual-console): Run EDFlow visit states by hand when there is no EHR feed or the feed is wrong: every manual action, the 10-second undo, overrides, back-dating and validation warnings.
  - [Visit cards and sign-in help](/staff/visit-cards-and-sign-in-help): Print a EDFlow visit card at a registered print station, approve staff-assisted sign-in with the patient's pairing code, and reissue a lost card, without staff ever holding a usable patient credential.
  - [Codes and department status](/staff/codes-and-department-status): See active codes and the department volume level in EDFlow, who can call, clear or post a delay notice for a code, and exactly what patients, family and the waiting-room display see.
  - [Companion app](/staff/companion-app): The EDFlow staff companion app on hospital-managed phones: request inbox, my patients, patient card, department, on-shift status, scanning a visit card, and push notifications while on shift.
  - [Privacy at work](/staff/privacy-at-work): PHIPA duties in plain words for EDFlow users: what is audited, confidential patients, never photographing the board, your recent actions, and how to talk to patients about the app.
  - [AI assistance](/staff/ai-assistance): The EDFlow staff AI features: the request queue digest, the handover attention summary and patient message drafts. What each one reads, what you must review, and how they are turned off.
  - [Troubleshooting for staff](/staff/troubleshooting): Fix common EDFlow problems for staff: the EHR feed is delayed or down, a patient says the app is wrong (report a data problem), sign-in and lock problems, missing sounds, and cards that don't print.
  - Nurses
    - [Nurses](/staff/nurses): A nursing shift with EDFlow: going on shift, your zone and your patients, your request queue, tasks and family links, with a printable quick-reference card.
    - [Triage](/staff/nurses/triage): Triage nurses in EDFlow: the waiting-room request pool, reassessment due and overdue, re-triage requests, cards after triage, staff-assisted sign-in, the busy banner, and answering how much longer.
    - [Tasks](/staff/nurses/tasks): Patient tasks in EDFlow: which tasks are created automatically from orders (urine samples, consent, check before eating, nothing by mouth), adding tasks from templates, and confirming tasks patients mark done.
    - [Publishing the going-home summary](/staff/nurses/after-visit-summary): Compose, preview and publish the EDFlow going-home summary from approved templates, mark Cleared to leave, edit or unpublish, and what the patient receives.
    - [Family links](/staff/nurses/family-links): See and revoke a visit's family links in EDFlow, lock sharing, pause updates to break news in person, and understand why sharing is unavailable for some visits.
    - [My metrics for nurses](/staff/nurses/my-metrics): Nurse self-view metrics in EDFlow where the site turns them on: your request first-response times and the alerts you receive per hour, visible only to you.
  - Physicians
    - [Physicians](/staff/physicians): Physicians, residents, nurse practitioners and physician assistants in EDFlow: Assign me, Seen and Seen again, why the seen time matters to the patient's screen, NACRS PIA, and a quick-reference card.
    - [Results and reassessment](/staff/physicians/results-and-reassessment): How result status reaches patients in EDFlow: the site's results display delay, holding and releasing results, all results back, serial tests, reassessment, and the results-back digest.
    - [Calling a code](/staff/physicians/calling-a-code): How to call a code in EDFlow in two steps: pick the type and the patient it's for, review who will be excluded and notified, then confirm. Code categories, who is notified, and the patient delay notice.
    - [Going-home summary rules for physicians](/staff/physicians/after-visit-summary): Content rules for the EDFlow going-home summary for physicians: no diagnosis text from the EHR, the prescriber-attested medicines section, follow-up and red flags from approved templates.
    - [My metrics for physicians](/staff/physicians/my-metrics): Per-physician step metrics in EDFlow: definitions, the private self view against blinded peer ranges, case-mix context, and why there are never ranks.
    - [Your profile](/staff/physicians/your-profile): Control how patients see you in EDFlow: the name display policy, the optional photo, being hidden from patients, linked EHR identities, and your notification settings.
  - Charge nurses
    - [Charge nurses](/staff/charge): Running the emergency department with EDFlow as charge nurse: zones and shifts, codes, department volume, escalations, overrides, feed downtime, analytics and a quick-reference card.
    - [Zones and shifts](/staff/charge/zones-and-shifts): Assign nurses to zones, the triage pool, the support pool, charge and the physician in charge in EDFlow, and how those assignments route patient requests and decide who is on shift.
    - [Department volume](/staff/charge/department-volume): Set the department volume level in EDFlow (normal, busy, very busy, surge), how suggestions are computed, imaging service status, and what patients, family, the entry page and the waiting-room display show.
    - [Codes](/staff/charge/codes): Charge nurses and codes in EDFlow: call, extend, clear and cancel codes, resolve paged codes, post the delay notice, merge and throttle rules, and which categories can notify patients.
    - [Escalations](/staff/charge/escalations): Request service levels and escalation in EDFlow for charge nurses: urgent requests without a response, Going now timers, thinking of leaving, over-the-usual-wait alerts and reassessments overdue.
    - [Overrides and corrections](/staff/charge/overrides-and-corrections): Override EHR data in EDFlow when the feed is wrong, undo a console action, correct a time (including the PIA), reopen a departed visit, cancel a duplicate and link a downtime registration.
    - [When the EHR feed is down](/staff/charge/feed-down): What to do when the EDFlow EHR feed is delayed or down: what patients see, frozen estimates, the downtime procedure and kit, running the manual console, and handing back to the feed.
    - [Department analytics for the charge nurse](/staff/charge/analytics): Department analytics a charge nurse can open in EDFlow: today's flow and bottlenecks, and Ask your data where the site has turned it on, with what it can and can't answer.
    - [Big board and handover](/staff/charge/big-board-and-handover): Big-board mode for the staff station in EDFlow (initials only, auto-paging, no actions, big-board station credentials) and the per-nurse handover summary.
  - Registration clerks
    - [Registration clerks](/staff/clerks): What registration clerks see and do in EDFlow: the limited board, visit cards and the print queue, manual registration, lost cards, sign-in help, and confidential and unknown patients.
    - [Visit cards](/staff/clerks/visit-cards): The EDFlow visit card print queue: automatic printing after triage, the 15-minute reprint window, card layouts and recipients, the print station, and what's printed on the card.
    - [Register a patient](/staff/clerks/register-a-patient): Register a patient by hand in EDFlow at manual-mode sites or during EHR downtime: the fields, the minimal data profile, the duplicate check, triage and the card recipient.
    - [Lost cards and access](/staff/clerks/lost-cards-and-access): Replace a lost or wrongly given EDFlow visit card, sign out a patient's devices, handle This wasn't me alerts and possible wrong-patient sign-ins, and revoke access.
    - [Helping patients sign in](/staff/clerks/helping-patients-sign-in): Help a patient sign in to EDFlow on their own phone: staff-assisted pairing and the five most common sign-in problems, without ever handling their card code.
    - [Confidential and unknown patients](/staff/clerks/confidential-and-unknown-patients): Set or clear the confidential (no-information) flag in EDFlow, confirm a provisional identity for an unknown patient, and what each does to the board, cards and family sharing.
- Administrators
  - [Users and access](/admin/users-and-access): Manage EDFlow staff accounts: invites, roles and the full permission matrix, approvals for privileged roles, deactivation, unlock and MFA reset, bulk import and SCIM, and the quarterly access review.
  - Settings
    - [Site settings](/admin/settings): How EDFlow site settings work: allowed ranges, settings locked in production, privacy-reducing changes, approvals, history and revert, configuration transfer, and the full settings reference.
    - [Hospital information](/admin/settings/hospital-information): Set the hospital information patients and family see in EDFlow: names, address and entrance, phones, Wi-Fi, parking, visitor policies, wayfinding points with maps, the patient portal and co-branding.
    - [Zones, beds and shifts](/admin/settings/zones-beds-and-shifts): Define EDFlow zones with their streams, beds and EHR location codes, treatment-space capacity, shift times and the CTAS reassessment intervals for the waiting room.
    - [Request types](/admin/settings/request-types): Edit the EDFlow request catalogue: enable, reorder and customise request types, routes and pools, FYI-only types, care-flag rules, service-level targets, and the locked I feel worse request.
    - [Code types](/admin/settings/code-types): Configure the EDFlow code-type catalogue: Ontario colour-code defaults, categories and patient notification rules, notice stages and scope, durations, optional templates and paging location filters.
    - [Tests and benchmarks](/admin/settings/tests-and-benchmarks): The EDFlow test catalogue: EHR code mappings, patient-visible names and steps, sensitive and hidden tests, result thresholds per imaging modality, service hours, default benchmarks, estimate settings and historical import.
    - [Patient content](/admin/settings/patient-content): Govern patient-facing content in EDFlow: education sheets, going-home templates, task templates, FAQ and glossary; the draft, clinical review, approval and publish workflow; and AI drafting help.
    - [Languages](/admin/settings/languages): Configure languages in EDFlow: English and French, the site default and active offer of French, up to five safety locales for the safety-critical messages, and translation completeness.
    - [Privacy and retention](/admin/settings/privacy-and-retention): Configure EDFlow privacy and access settings: patient and family access windows, sharing limits, the data profile, youth-confidential ages, results display delay, retention periods and de-identification.
    - [Notifications](/admin/settings/notifications): Configure EDFlow notification channels per site: push, patient and family text messages (Twilio), email (Resend), the generic lock-screen default, rate caps, sending a test, and clinical communication platforms.
    - [Waiting-room display](/admin/settings/waiting-room-display): Set up the EDFlow waiting-room display: public or key access, the official typical wait, slides, language mode, orientation, embedding, and registering big-board and print stations.
  - [Announcements](/admin/announcements): Post, schedule and expire EDFlow site announcements for the entry page, patients, family, the waiting-room display and staff, with approved templates, a 280-character limit and link rules.
  - Analytics
    - [Analytics](/admin/analytics): EDFlow analytics conventions and every metric definition: time zones, T0, percentiles, small-cell suppression, Ontario LOS groups, filters, annotations and exports, generated from the same definitions the computations use.
    - [Flow and bottlenecks](/admin/analytics/flow-and-bottlenecks): Find where ED time is lost with EDFlow: flow segments from arrival to departure, the per-visit bottleneck flag, the period bottleneck ranking by excess minutes, heatmaps, trends and capacity drivers.
    - [Test turnaround](/admin/analytics/test-turnaround): Test turnaround analytics in EDFlow: order-to-result and collection-to-result times per test, hour-by-weekday heatmaps, bucket coverage, the estimate level patients get, and the benchmark job.
    - [Request analytics](/admin/analytics/requests): Request analytics in EDFlow: volume by type, zone and hour, time to first response and to resolve, urgent in-person response, service-level compliance, escalations and alerts per nurse per hour.
    - [Clinician metrics](/admin/analytics/clinician-metrics): Per-physician step metrics in EDFlow: attribution, the blinded and named views, case-mix context, the minimum sample size, governance, and why there are never ranks or league tables.
    - [Feedback](/admin/analytics/feedback): Patient feedback analytics in EDFlow: the five-question post-visit survey, the in-visit pulse, response rates, top-box shares, comments hidden when they may contain personal information, and family feedback.
    - [Adoption and equity](/admin/analytics/adoption-and-equity): Who uses EDFlow in your ED: the activation funnel from card to feedback, broken down by preferred language, age band, arrival mode and platform, and the equity panel that flags gaps over 10 points.
    - [Codes and delays](/admin/analytics/codes-and-delays): Code and volume analytics in EDFlow: the code log, frequency by type and hour, patients notified, the descriptive code impact on waits, and time in each volume level.
    - [Estimate quality](/admin/analytics/estimate-quality): Check that EDFlow wait estimates are honest: coverage of the 9-in-10 ceiling (target 88%), calibration, fallback levels, bucket coverage, the benchmark job and importing historical data.
    - [Ask your data](/admin/analytics/ask-your-data): Ask plain-language questions about ED operations in EDFlow and get charts and reports built from de-identified analytics, with the query shown, plus anomaly alerts. What data it uses and how to review it.
  - [Reports and exports](/admin/reports-and-exports): De-identified exports from EDFlow (visit facts, test turnaround, request facts, feedback, code log), how they are de-identified, the export log, single-use downloads and scheduled reports.
  - [AI](/admin/ai): Turn EDFlow AI features on per site: the six layers that must all allow a feature, the governance gates G-AI-1 to G-AI-6, budgets, conversation retention, the kill switch, and where flagged conversations go.
  - [Pilot playbook](/admin/pilot-playbook): Run a EDFlow pilot in your emergency department: baseline measurement, staff briefing and training mode, posters and QR signage, the first week, the weekly review and the success metrics.
  - [EDFlow Mail](/admin/mail): EDFlow Mail for the company team: shared mailboxes, AI triage of every inbound email, rules, hybrid search, support tickets with auto-acknowledgement, and the rule that mail never carries patient health information.
  - Privacy officers
    - [Privacy officers](/admin/privacy): EDFlow for privacy officers: the audit log and what is logged, per-patient access reports, monitoring alerts A-1 to A-28, exports with second-person approval, incidents, emergency revoke and safety concerns.
    - [Access requests and retention](/admin/privacy/access-requests-and-retention): Answer PHIPA access requests with a EDFlow visit-record export, place and lift legal holds, and understand the retention schedule, care records and de-identification after the operational window.
    - [Message outbox](/admin/privacy/message-outbox): The EDFlow message outbox: every text, email and push attempt with masked recipients and masked links, delivery status, resend, and why invite and reset links are never kept.
    - [Vendor support access](/admin/privacy/vendor-support-access): How time-boxed vendor support access to your EDFlow site works: no standing access, a ticket and reason, read-only or admin scope, at most 4 hours, notifications to managers and a full audit trail.
    - [AI review](/admin/privacy/ai-review): Review flagged EDFlow AI conversations as part of the safety review group: what gets flagged, reason codes, conflict rules, what you see, and resolving safety events.
  - Integration analysts
    - [Integration analysts](/admin/integration): EDFlow for integration analysts: feed health states and what each audience sees, per-source status, heartbeats, event counts, rejections by error code, roster discrepancies and feed alerts.
    - [Sources and keys](/admin/integration/sources-and-keys): Register an EHR source in EDFlow, edit its versioned mapping profile, reveal a signing key once, rotate with two active key versions, and disable a source in an emergency.
    - [Event log](/admin/integration/event-log): Read the EDFlow EHR event ledger: accepted, duplicate, buffered, ignored and rejected events, error codes, the allow-listed payload view, and validating a payload as a dry run.
    - [Unmapped codes](/admin/integration/unmapped-codes): Map unmapped test and location codes from the EHR feed in EDFlow: map to a catalogue test, create an entry or ignore, the zero-unmapped go-live gate, and AI mapping suggestions.
    - [Dead letters](/admin/integration/dead-letters): Handle EDFlow dead letters: buffered events that expired and processing errors, viewing and revealing payloads (audited), replaying after a fix, discarding, and bulk replay.
    - [Data issues](/admin/integration/data-issues): Work the EDFlow Report a data problem queue: what staff report, resolving or closing reports, and how data issues feed the 98% milestone agreement go-live gate.
    - [Simulator](/admin/integration/simulator): The EDFlow EHR simulator for the sandbox and showcase: fire the next event for a visit, run scripted scenarios, autopilot a synthetic department, choose the transport (direct, signed webhook, HL7 v2, FHIR) and control the feed.
- Developers
  - [Quickstart](/developers/quickstart): Create a sandbox app, get an OAuth token, check health, send a heartbeat, an arrival and a triage event, watch the patient appear on the sandbox board, and receive your first webhook, in about 15 minutes.
  - [Concepts](/developers/concepts): How the EDFlow integration model works: sites, sources, encounters and events, facts and derived stages, projections and minimum necessary data, idempotency, ordering and precedence, and the early-arrival buffer.
  - [Authentication](/developers/authentication): Authenticate to the EDFlow Integration API: OAuth 2.0 client credentials with private_key_jwt, client secret or mTLS, short-lived JWT access tokens, scopes, network binding, HMAC source keys for the signed ingest profile, clock skew, lockouts and signing at send time.
  - [Credentials](/developers/credentials): Manage EDFlow API credentials: self-serve in the developer portal or issued by the hospital or the vendor, shown once, rotation with overlap, expiry reminders, revocation, and what to do if a key leaks.
  - API reference
    - [API reference](/developers/api): The EDFlow Integration API reference: base URLs per environment, the pinned API version, conventions for ids, lists and incremental sync, errors, rate limits, the sandbox playground, and the OpenAPI and Postman downloads.
    - Codes
      - [List code alerts](/developers/api/codes/listCodeAlerts): Department code alerts (default: active). `area` is omitted when the site turns `integration.api.includeCodeArea` off.
    - Documents
      - [Get a visit document](/developers/api/documents/getDocument): Fetch a visit document by id (Phase 3). Requires `documents:read` and a token obtained with `private_key_jwt` or mTLS; documents are available for 72 hours.
    - Encounters
      - [Get an encounter's care team](/developers/api/encounters/getCareTeam): The current care team. Zone-derived nurses are computed at read time (`id: null`, `source: zone`). Staff hidden from patients are listed with `hiddenFromPatients: true`.
      - [Get an encounter](/developers/api/encounters/getEncounter): One encounter. `404` for unknown ids, other sites and archived encounters.
      - [List encounters](/developers/api/encounters/listEncounters): Encounters ordered by `(updatedAt, id)`. `updatedSince` gives incremental sync; items updated in the last 10 seconds are held back (settle window).
      - [Look up an encounter by visit number](/developers/api/encounters/lookupEncounter): Resolves an EHR visit number to an encounter without EDFlow storing the number. A miss is `200` with `found: false`. Rate-limited (`lookup`) and audited without the identifier.
    - Fhir
      - [FHIR CapabilityStatement](/developers/api/fhir/getFhirCapabilityStatement): FHIR R4 CapabilityStatement (`kind: instance`). Declares only `batch`, `$process-message` and `$ingest`; there is no FHIR read API.
      - [$ingest OperationDefinition](/developers/api/fhir/getFhirIngestOperationDefinition): The OperationDefinition of `$ingest` (canonical `https://edflow.space/fhir/OperationDefinition/ingest`).
      - [SMART configuration](/developers/api/fhir/getSmartConfiguration): SMART Backend Services configuration: asymmetric client authentication (`private_key_jwt`) for token requests to the push endpoints only.
      - [Ingest a FHIR batch Bundle](/developers/api/fhir/ingestFhirBundle): A FHIR R4 `batch` Bundle only (each entry processed independently). A `transaction` Bundle is refused with `422 transaction_not_supported`; other Bundle types go to `$ingest`. `Accept: application/fhir+json` answers a `batch-response` Bundle.
      - [Ingest another Bundle type ($ingest)](/developers/api/fhir/ingestFhirCustom): `$ingest`: Bundle types FHIR does not allow at the base (`collection`, `searchset`, `history`), including Subscriptions Backport notifications. Handshakes and heartbeats produce no events.
      - [Process a FHIR message](/developers/api/fhir/processFhirMessage): `$process-message`: a `message` Bundle whose first entry is a `MessageHeader`. Synchronous; duplicates (`Bundle.id` + `MessageHeader.id`, 30 days) replay the stored response. Data rejections answer 200 with `fatal-error`; transient failures answer 503 with `Retry-After`.
    - Hl7 v2
      - [Ingest HL7 v2](/developers/api/hl7-v2/ingestHl7v2): Raw mode (`application/hl7-v2`, `x-application/hl7-v2+er7` or `text/plain`, optional `charset` that must agree with MSH-18): one ER7 message, answered with an ACK per the ACK table. JSON mode (`application/json`): `{ messages }` (≤ 50). Transient failures are `503`/`429` with `Retry-After` and no ACK. Site: `?site=`, else resolved from MSH-4 through the mapping profile. Engines must never hold their queue on a EDFlow ACK.
    - Ingest
      - [Get an ingest event](/developers/api/ingest/getIngestEvent): One ledger row of the app's source by the source event id (URL-encoded). Metadata only.
      - [Ingest one event](/developers/api/ingest/ingestEvent): One normalized event (≤ 32 KiB). `accepted`, `duplicate`, `ignored` and `superseded` answer 200; `buffered` and `quarantined` answer 202; a data rejection is `422 event_rejected`; a reused id with another payload is `409 idempotency_conflict`; a processing error is `503` (retry the same event).
      - [Ingest a batch of events](/developers/api/ingest/ingestEventBatch): 1 to 100 normalized events, applied in array order, each atomically and independently. The 200 body is byte-compatible with `/ehr/v1/events`, so an engine can switch transports without changing response handling. A per-event `processing_error` is `retryable`: resend that event (same id).
      - [List ingest events](/developers/api/ingest/listIngestEvents): The ingest ledger of the app's source (30 days), ordered by `(updatedAt, id)`. Metadata only, never payloads.
      - [Dry-run any input](/developers/api/ingest/validateInput): Dry run for any input: nothing is persisted, notified or ledgered. The input kind comes from `Content-Type` (`application/json` events, `application/fhir+json`, `application/hl7-v2`, or JSON `{ messages }` with `?input=hl7v2`). The environment checks (processing id, sandbox tripwire) apply.
    - Metadata
      - [Health](/developers/api/metadata/getHealth): Public liveness. Compare `time` with your own clock. `down` answers HTTP 503.
      - [Identity and configuration](/developers/api/metadata/getMeta): Who the caller is and how the platform is configured for it: app, organization, sites, scopes, pinned version, credential, limits and webhook egress addresses.
      - [OpenAPI document](/developers/api/metadata/getOpenApi): The OpenAPI 3.1 document of this deployment, generated from the operation registry. Identical to the published document except `servers`.
    - Oauth
      - [Get an access token](/developers/api/oauth/createAccessToken): Issues a short-lived (≤ 300 s) ES256 access token (RFC 9068). Cache it and refresh 30 s before `expires_in`. Errors use RFC 6749 bodies; failed client authentication is rate-limited per (client id, source address).
      - [OAuth authorization server metadata](/developers/api/oauth/getAuthorizationServerMetadata): RFC 8414 authorization server metadata. Lists every client authentication method this deployment supports.
      - [Token signing keys](/developers/api/oauth/getTokenSigningKeys): Public keys of the access-token signing keys (ES256). Two keys are published during a rotation.
      - [Revoke an access token](/developers/api/oauth/revokeAccessToken): RFC 7009. Always answers 200, even for unknown tokens. The next request with a revoked token gets `401 token_revoked`.
    - Requests
      - [Acknowledge a request from the EMR](/developers/api/requests/acknowledgeRequest): Marks an open request as seen when a clinician handles it in the EMR. The patient sees the same result as a console acknowledgement: "Seen by {name}" for a linked practitioner, otherwise the generic care-team copy. Already acknowledged answers 200 with the current state; resolved or cancelled answers `409 conflict`. Requires the site's request write-back switch.
      - [Get a request](/developers/api/requests/getRequest): One request.
      - [List requests](/developers/api/requests/listRequests): The requests feed, ordered by `(updatedAt, id)`, with the 10-second settle window. Only requests past the patient's undo window appear.
      - [Resolve a request from the EMR](/developers/api/requests/resolveRequest): Resolves a request from the EMR (acknowledging it first when open). Already resolved answers 200 with the current state; cancelled answers `409 conflict`.
    - Sandbox
      - [Create a patient request](/developers/api/sandbox/sandboxCreateRequest): Creates a patient request on a synthetic encounter as if the patient tapped it (skipping the undo window), to test `request.created` webhooks and write-back.
      - [Get a conformance run](/developers/api/sandbox/sandboxGetConformance): A conformance run and its checks with evidence.
      - [Get fault settings](/developers/api/sandbox/sandboxGetFaults): The app's active fault settings.
      - [Reset the sandbox](/developers/api/sandbox/sandboxReset): Resets the org's sandbox sites: deletes the app's ledger rows and webhook history for those sites.
      - [Run a simulator scenario](/developers/api/sandbox/sandboxRunScenario): Runs a simulator scenario (for example `chest_pain_admit`, `lwbs`) through the chosen transport.
      - [Set fault injection](/developers/api/sandbox/sandboxSetFaults): Makes this app's own requests fail or slow down (`503` with `Retry-After`, `429`, latency, token endpoint down) for ≤ 24 h. Other apps are unaffected. At most 5 faults.
      - [Start a conformance run](/developers/api/sandbox/sandboxStartConformance): Starts a go-live conformance run: `ingest`, `webhooks`, `writeback`, `outage_recovery` (turns on a 30-minute `unavailable` fault), `clock_skew` (±90 s), `backfill_10k`.
    - Signed ingest
      - [Signed ingest: events](/developers/api/signed-ingest/signedIngestEvents): Normalized events signed with the source key (`EDFlow-Source`, `EDFlow-Timestamp`, `EDFlow-Delivery-Id`, `EDFlow-Signature`). An exact replay of a processed delivery returns the stored 200 result.
      - [Signed ingest: FHIR](/developers/api/signed-ingest/signedIngestFhir): A FHIR R4 Bundle signed with the source key; `EDFlow-Site-Code` names the site.
      - [Signed ingest: health](/developers/api/signed-ingest/signedIngestHealth): Unauthenticated health of the signed ingest: `status`, `time` and `specVersions`.
      - [Signed ingest: HL7 v2](/developers/api/signed-ingest/signedIngestHl7v2): JSON-wrapped HL7 v2 messages (≤ 50) signed with the source key; ACKs follow the ACK table.
      - [Signed ingest: validate](/developers/api/signed-ingest/signedIngestValidate): Dry run of any of the three inputs (`EDFlow-Input`); persists nothing.
    - Sites
      - [List sites](/developers/api/sites/listSites): The sites bound to the app, with feed state, volume and the site's capability switches.
    - Tasks
      - [List tasks](/developers/api/tasks/listTasks): Patient tasks ordered by `(updatedAt, id)`, with the 10-second settle window.
    - Webhooks
      - [Create a webhook endpoint](/developers/api/webhooks/createWebhookEndpoint): Creates an endpoint. The URL must pass the destination policy (HTTPS, public host, no private ranges). The `whsec_` signing secret is returned **once**.
      - [Delete a webhook endpoint](/developers/api/webhooks/deleteWebhookEndpoint): Deletes an endpoint and cancels its pending deliveries.
      - [Get a delivery](/developers/api/webhooks/getWebhookDelivery): One delivery with its thin payload and ≤ 10 attempts.
      - [Get a webhook endpoint](/developers/api/webhooks/getWebhookEndpoint): One endpoint. Secrets and header values are never returned.
      - [List deliveries](/developers/api/webhooks/listWebhookDeliveries): Deliveries of an endpoint, newest first (without payloads).
      - [List webhook endpoints](/developers/api/webhooks/listWebhookEndpoints): The app's endpoints (≤ 20).
      - [List webhook event types](/developers/api/webhooks/listWebhookEventTypes): The event catalogue with each type's data schema, sensitivity, expiry and `liveFrom`.
      - [Recover failed deliveries](/developers/api/webhooks/recoverWebhookDeliveries): Redelivers every failed delivery since a time (≤ 14 days). Expired events are skipped unless `includeExpired`.
      - [Redeliver a message](/developers/api/webhooks/redeliverWebhook): A new delivery of the same message (same `webhook-id`). An expired sensitive event needs `allowExpired`.
      - [Rotate the signing secret](/developers/api/webhooks/rotateWebhookSecret): Adds a new secret version; both sign during the overlap (1–168 h, default 24 h). The new secret is shown once.
      - [Send a test message](/developers/api/webhooks/sendWebhookTest): Posts a `webhook.test` message synchronously and returns the attempt.
      - [Update a webhook endpoint](/developers/api/webhooks/updateWebhookEndpoint): Updates an endpoint. Re-enabling an auto-disabled endpoint is `status: enabled`; then `recover`.
      - [A code was called](/developers/api/webhooks/webhook-code.called): A department code is active (after the two-step confirmation). No patient data.
      - [A code ended](/developers/api/webhooks/webhook-code.cleared): A code was cleared, cancelled or expired.
      - [A code changed](/developers/api/webhooks/webhook-code.updated): A code was extended or its patient notice changed.
      - [A patient opened the visit](/developers/api/webhooks/webhook-encounter.access_activated): The first patient session on the visit.
      - [The visit stage changed](/developers/api/webhooks/webhook-encounter.stage_changed): The derived stage changed. Expires after 6 hours or when a newer stage change exists.
      - [Feed state changed](/developers/api/webhooks/webhook-feed.state_changed): A site's feed moved between healthy, delayed and down.
      - [An event was dead-lettered](/developers/api/webhooks/webhook-ingest.dead_lettered): A buffered event expired or a data rejection was dead-lettered; fix the mapping and replay it.
      - [A roster was quarantined](/developers/api/webhooks/webhook-ingest.roster_quarantined): The roster circuit breaker held a department roster for a person to confirm or discard.
      - [A credential is expiring](/developers/api/webhooks/webhook-integration.credential_expiring): Sent 30, 7 and 1 days before a credential expires.
      - [A request was acknowledged](/developers/api/webhooks/webhook-request.acknowledged): From the staff console, the companion app or the API.
      - [A request was cancelled](/developers/api/webhooks/webhook-request.cancelled): The patient cancelled the request.
      - [A patient sent a request](/developers/api/webhooks/webhook-request.created): The request passed the patient's 5-second undo window. Expires after 2 hours, or at once when it is no longer open.
      - [A request was escalated](/developers/api/webhooks/webhook-request.escalated): A step of the escalation ladder. Expires after 1 hour, or when it is no longer open.
      - [A request was resolved](/developers/api/webhooks/webhook-request.resolved): Resolved by staff, by the API, or closed at departure.
      - [A patient completed a task](/developers/api/webhooks/webhook-task.completed): The patient marked a task done.
      - [Staff confirmed a task](/developers/api/webhooks/webhook-task.confirmed): Staff confirmed a patient-completed task.
      - [A communication log is ready](/developers/api/webhooks/webhook-visit.communication_log_ready): At departure when document write-back (Phase 3) is on. Fetch it with `GET /v1/documents/{documentId}` within 72 hours.
      - [Test message](/developers/api/webhooks/webhook-webhook.test): Sent by the portal's Send test button or `POST /v1/webhook-endpoints/{id}/test`.
  - [Webhooks](/developers/webhooks): Receive signed EDFlow webhooks (Standard Webhooks): subscribe, verify signatures, deduplicate on webhook-id, order by version, expiry, retries and auto-disable, authenticating to your gateway, event types, and redelivery.
  - Event reference
    - [Event reference](/developers/events): The EDFlow normalized event contract: the envelope, prohibited fields (the PHI tripwire), identifiers never allowed in ids, shared types, and every inbound event type with JSON Schemas to download.
    - [admission.status_changed](/developers/events/admission-status-changed): Bed flow for an admitted patient waiting in the ED.
    - [careteam.member_assigned](/developers/events/careteam-member-assigned): One care-team member was assigned.
    - [careteam.member_released](/developers/events/careteam-member-released): One care-team member was released.
    - [careteam.snapshot](/developers/events/careteam-snapshot): The authoritative team asserted by this source, limited to rolesCovered.
    - [consult.status_changed](/developers/events/consult-status-changed): A consult was requested, started, completed or cancelled.
    - [department.census_reported](/developers/events/department-census-reported): Aggregate department status with no identifiers.
    - [department.code_called](/developers/events/department-code-called): An emergency code was called.
    - [department.code_cleared](/developers/events/department-code-cleared): A code was cleared.
    - [department.roster_reported](/developers/events/department-roster-reported): The complete list of encounters active in the ED, for reconciliation.
    - [encounter.arrived](/developers/events/encounter-arrived): Registration or arrival at the ED.
    - [encounter.assessed](/developers/events/encounter-assessed): The physician initial assessment or a reassessment.
    - [encounter.cancelled](/developers/events/encounter-cancelled): The registration was voided.
    - [encounter.departed](/developers/events/encounter-departed): The patient physically left the ED.
    - [encounter.departure_cancelled](/developers/events/encounter-departure-cancelled): The discharge was reversed.
    - [encounter.disposition_decided](/developers/events/encounter-disposition-decided): A decision to discharge, admit, observe or transfer.
    - [encounter.location_changed](/developers/events/encounter-location-changed): A bed or area move, leave of absence or return.
    - [encounter.triaged](/developers/events/encounter-triaged): Triage completed, or a re-triage.
    - [order.placed](/developers/events/order-placed): A test or diagnostic order (the full order asserted each time).
    - [order.results_reviewed](/developers/events/order-results-reviewed): A clinician acknowledged the results.
    - [order.status_changed](/developers/events/order-status-changed): The current status of an order, with every timestamp known so far.
    - [patient.merged](/developers/events/patient-merged): Two MRNs were merged.
    - [patient.updated](/developers/events/patient-updated): A demographic or privacy correction.
    - [system.heartbeat](/developers/events/system-heartbeat): Feed liveness.
  - [FHIR R4](/developers/fhir): Send FHIR R4 to EDFlow: batch Bundles, the $ingest operation for collection, searchset and Subscriptions Backport notifications, $process-message, how each resource maps to events, Epic and Oracle Health notes, and a worked example.
  - [HL7 v2](/developers/hl7v2): Send HL7 v2 to EDFlow over HTTPS: supported versions and vendors (Epic Bridges, Oracle Health Millennium, MEDITECH), triggers and the events they produce, result and order status maps, the field map, character sets and escapes, the ACK table, and a worked example stream.
  - [Mapping profiles](/developers/mapping-profiles): The versioned EDFlow site mapping profile: encounter filters and identifiers, locations and beds, CTAS codes, roles and practitioner ids, dispositions, order and consult codes, NPO diet codes, result thresholds, privacy options, and unmapped-code governance.
  - [Sandbox](/developers/sandbox): Create a sandbox app and develop against the EDFlow sandbox: synthetic-only enforcement, fictional hospitals, simulator scenarios, dry-run validation, fault injection, conformance profiles including outage_recovery, and resetting, plus how customer test differs.
  - [SDKs and snippets](/developers/sdks-and-snippets): Code snippets in cURL, TypeScript and Python for every EDFlow API operation, signing helpers for the signed ingest profile with the conformance test vector, the OpenAPI document, Postman collection and typed clients.
  - [AI mapping assistant](/developers/ai-mapping-assistant): Use the EDFlow mapping assistant to draft a site mapping profile from sample HL7 v2, FHIR or CSV: synthetic samples only in the sandbox, allow-list scrubbing, a proposed profile validated against the event schema, and nothing applied without review.
  - [Errors](/developers/errors): Every EDFlow error code: request-level HTTP status on the signed ingest profile, per-event result codes, and REST API problem details (RFC 9457) with retryable flags and the retry action to take first.
  - [Rate limits and retries](/developers/rate-limits-and-retries): EDFlow rate limits per bucket, the RateLimit headers, which errors to retry and how, exponential backoff with jitter, idempotency keys, and batching and size limits.
  - [Versioning and deprecation](/developers/versioning-and-deprecation): How the EDFlow API and event contract are versioned: the URL major version, dated Api-Version pins, specVersion, notice periods for new enum values and event types (60 days) and breaking changes (12 months), Deprecation and Sunset headers, and host migration.
  - [Go live](/developers/go-live): Take a EDFlow integration live: sandbox conformance, the customer-test shadow run and the 98% milestone agreement gate, promotion with four-eyes approval and the PIA attestation, cut-over, and monitoring after go-live.
  - API changelog
    - [API changelog](/developers/changelog): Changes to the EDFlow Integration API and event contract: dated API versions, additive releases, announced enum values and event types, deprecations and sunsets.
  - [Build with AI](/developers/build-with-ai): Point Claude Code, Cursor or another coding assistant at the EDFlow docs: llms.txt, llms-full.txt, a Markdown version of every page, the docs MCP server, and the rules to give your agent.
  - [SMART on FHIR](/developers/smart-on-fhir): The optional SMART on FHIR launch that opens a patient's EDFlow card inside Epic or Oracle Health FirstNet without a second login: the flow, prerequisites per vendor, and why staff access stays invite-only.
  - [EHR write-back](/developers/ehr-write-back): Options for sending EDFlow activity back to the EHR: request write-back through the API, an optional end-of-visit communication log document, and why the pilot stays read-only.
  - [Engine configuration](/developers/engine-configuration): Configure your integration engine for EDFlow: store and forward, a queued destination that never holds the queue on AE or AR, signing and token refresh at send time, surviving a 30-minute outage, heartbeats and rosters, dead letters, and Mirth Connect / OIE templates with Rhapsody and Cloverleaf notes.
  - [FHIR implementation guide](/developers/fhir-implementation-guide): The EDFlow ED Visit Workflow FHIR implementation guide: base profiles on CA Baseline, must-support and prohibited elements, terminology and canonical URLs, the $ingest operation, examples, and validating with the HL7 FHIR validator.
- IT and security
  - [Architecture](/security/architecture): EDFlow system context and runtime containers for hospital reviewers: the web tier, the Convex backend, the mobile apps, the integration engine link, optional providers, environments and what runs where.
  - [Data flow](/security/data-flow): How data moves from the EHR to the patient's screen in EDFlow, what crosses each boundary and what never does, and the data inventory by privacy class with retention.
  - [PHIPA roles and privacy](/security/phipa): EDFlow under Ontario's PHIPA: the hospital as custodian, the vendor as agent and electronic service provider, voluntary HINP duties, minimum necessary, consent for family sharing, patient access, breach notification, and PIA and TRA support.
  - [Controls](/security/controls): The EDFlow controls matrix: authentication and MFA, server-side authorization and projections, token hashing, encryption, rate limits, audit, log redaction, security headers and CSP, supply chain, vulnerability management and penetration testing.
  - [Threat model](/security/threat-model): A summary of the EDFlow threat and risk assessment: attacker models, STRIDE threats per component, the top risks and their mitigations, and residual risks.
  - [Data residency](/security/data-residency): Where EDFlow stores hospital data: AWS ca-central-1 with disaster recovery in ca-west-1, backups in Canada, RPO and RTO, the web tier in Montréal, and which environments hold synthetic data only.
  - [Subprocessors](/security/subprocessors): Every EDFlow sub-processor with its purpose, whether health information can reach it, the data categories, its location and when it applies, from the single list shared with the privacy page and the security review pack.
  - [Accessibility](/security/accessibility): EDFlow accessibility conformance for hospital reviewers: WCAG 2.2 AA on every surface, how it is tested (axe in CI, keyboard, screen readers, Dynamic Type and font scale), the conformance report, and known issues.
  - [Identity and SSO](/security/identity-and-sso): Staff identity in EDFlow: Microsoft Entra ID setup, MFA policy per role, the session policy table, SCIM provisioning and deprovisioning, and how patient and family access differs.
  - [Network requirements](/security/network-requirements): Hosts and ports to allow for EDFlow: web, the realtime WebSocket, push notifications, integration-engine egress to the API, the waiting-room display kiosk, and guest Wi-Fi guidance for patients.
  - [Devices and device management](/security/devices): Devices for EDFlow: staff phones under MDM and the managed-device requirement, shared workstations, print and big-board stations, the waiting-room kiosk, and patients' own phones.
  - [Availability and incidents](/security/availability-and-incidents): EDFlow service levels: the support severity matrix with 24/7 P1 response within 30 minutes, the 24-hour breach notice, maintenance windows and notice, SLOs and the HA topology they depend on, RPO and RTO, DR drills and the status page.
  - [Audit logging](/security/audit-logging): What EDFlow records in its audit log, the record format, append-only storage with a daily hash chain, proactive monitoring rules, per-patient access reports and SIEM export.
  - [AI governance](/security/ai): How EDFlow governs AI: models and providers, zero data retention and no training, data classes C0 to C3, what leaves the tenant, human approval, the medical-device boundary, enablement gates G-AI-1 to G-AI-6, the kill switch and opting a visit out.
  - [Vulnerability disclosure](/security/vulnerability-disclosure): How to report a security vulnerability in EDFlow: scope, safe-harbour rules, what to include, what never to do with patient data, response times, and security.txt.
  - [Compliance documents](/security/compliance-documents): What EDFlow publishes, what is shared under NDA (the security review pack, PIA and TRA inputs, penetration test summary, questionnaire answers), the SOC 2 position stated accurately, and how to request documents.
  - [Privileged access](/security/privileged-access): How EDFlow vendor staff can and cannot reach production: no standing access, audited time-boxed support access, break-glass with approval and session recording, two-person deployments, personnel security, and data return and destruction.
- Brand
  - [Hospital communications](/brand/hospital-communications): Posters, QR signage, visit cards, the waiting-room display and co-branding rules for hospitals running EDFlow, with the safety messages every piece must carry.
  - [Writing patient content](/brand/writing-patient-content): Voice, tone and word choices for hospital authors writing EDFlow patient content (education sheets, going-home templates, FAQ, announcements), with French typography rules and the words never to use.
  - [Press kit](/brand/press-kit): EDFlow logos, a curated screenshot pack captured from fictional sample data, and boilerplate text for articles, hospital newsletters and announcements.
- Release notes
  - [Release 1.2](/releases/1-2-0): EDFlow 1.2: the Integration API and developer portal, signed webhooks, the documentation site with automated screenshots, brand configuration and co-branding, email and SMS delivery, and AI features that stay off until a site approves them.

## Français

# Docs

- Pour commencer
  - [Le déroulement d'une visite](/fr/start/how-a-visit-works): La visite à l'urgence, de l'arrivée au retour à la maison, telle que les patients et leur famille la voient dans EDFlow : chaque étape, ce qui change à chacune et ce que montre la vue famille.
  - [Choisir votre guide](/fr/start/choose-your-guide): Trouvez le guide EDFlow qui correspond à votre rôle : patients, familles, infirmières, médecins, infirmières responsables, commis à l'inscription, gestionnaires, responsables de la vie privée, analystes en intégration, développeurs et TI de l'hôpital.
  - [Sécurité](/fr/start/safety): Le modèle de sécurité de EDFlow : « Je me sens plus mal » dirige toujours d'abord vers le personnel, les avis de retard n'identifient jamais personne, les résultats ne sont jamais affichés, et ce qui se passe quand le téléphone est hors ligne.
  - [Langues et accessibilité](/fr/start/languages-and-accessibility): EDFlow en anglais et en français, les messages de sécurité dans les principales langues de chaque hôpital, du texte agrandi à 200 %, les lecteurs d'écran, Dynamic Type et l'échelle de police, le contraste élevé, la réduction des animations et des états qui ne dépendent pas de la couleur.
  - [Appareils](/fr/start/devices): Les téléphones, navigateurs et écrans pris en charge par EDFlow : iOS 17 et plus récent (conçu pour iOS 26), Android 8 et plus récent, les navigateurs actuels sans installation, et l'affichage de la salle d'attente.
  - [Démo](/fr/start/demo): Essayez EDFlow avec deux hôpitaux ontariens fictifs : ce que montre chaque visite d'exemple, comment ouvrir le lanceur de démo avec un code d'invitation, et ce que la démo ne contiendra jamais.
  - [Pour les hôpitaux](/fr/start/for-hospitals): Évaluer EDFlow pour votre urgence : le modèle de projet pilote, les options de DME (Epic, Oracle Health, MEDITECH ou manuel), ce que fournissent les TI, les critères de mise en service et les indicateurs de réussite.
  - [Glossaire](/fr/start/glossary): Les termes de l'urgence utilisés dans EDFlow (ÉTG, EIM, résumé de départ, PSV, à jeun, orientation, code, attente d'un lit) avec les mots simples que voient les patients et les termes qu'utilise le personnel.
  - [Questions fréquentes](/fr/start/faq): Réponses aux questions fréquentes sur EDFlow posées par les patients, les familles, le personnel, la direction des hôpitaux et les TI : résultats, temps d'attente, vie privée, temps du personnel et intégration.
- Patients et proches
  - Patients
    - [Pour les patients](/fr/patients): Suivez votre visite à l'urgence sur votre téléphone avec EDFlow : voyez où vous en êtes, qui s'occupe de vous, vos examens et les attentes habituelles, faites des demandes à votre équipe de soins et partagez des mises à jour avec votre famille.
    - [Se connecter](/fr/patients/sign-in): Comment vous connecter avec votre carte : balayez le code QR de votre bracelet ou de votre carte de visite, ou entrez votre nom de famille, votre date de naissance et votre code de visite, puis confirmez que c'est bien vous. Quoi faire si l'accès est bloqué.
    - [Application ou navigateur](/fr/patients/app-or-browser): Suivez votre visite dans le navigateur de votre téléphone sans rien installer, ou utilisez l'application EDFlow. Ce que disent les premiers écrans, comment fonctionnent les notifications et ce qu'affiche votre écran verrouillé.
    - [Votre visite](/fr/patients/your-visit): Ce que montre l'écran Visite dans EDFlow : votre étape actuelle, ce qui vient ensuite, l'attente habituelle pour cette étape, votre équipe de soins, vos examens, les demandes rapides et les dernières mises à jour.
    - [Chronologie](/fr/patients/timeline): La chronologie de EDFlow énumère chaque étape de votre visite à l'urgence avec son heure, de votre arrivée à votre départ, et ce qui vient habituellement ensuite.
    - [Équipe de soins](/fr/patients/care-team): Qui s'occupe de vous à l'urgence : votre médecin, un médecin en formation, votre infirmière et des spécialistes, et pourquoi certains noms montrent seulement un prénom.
    - [Examens](/fr/patients/tests): Suivez chacun de vos examens dans EDFlow : ses étapes, l'attente habituelle pour ce jour et cette heure, et le moment où les résultats sont prêts. Vous ne voyez jamais les résultats eux-mêmes; votre équipe de soins vous en parle.
    - [Estimations d'attente](/fr/patients/wait-estimates): Comment EDFlow estime les attentes, en mots simples : un intervalle habituel et le délai dans lequel 9 personnes sur 10 ont terminé, selon les visites passées le même jour et à la même heure. Pourquoi il n'y a pas de compte à rebours et pourquoi les durées peuvent changer.
    - [Retards](/fr/patients/delays): Ce que veulent dire l'avis de retard et la bannière d'urgence achalandée dans EDFlow, pourquoi l'urgence ralentit parfois, et ce que les avis ne vous disent jamais.
    - [Faire une demande à votre équipe de soins](/fr/patients/requests): Envoyez une demande à votre équipe de soins dans EDFlow : une couverture, de l'eau, de l'aide pour aller aux toilettes, un interprète, une question, ou dire que vous sortez un moment. Ce que veut dire « Vu par », les rappels, les limites et l'annulation.
    - [Si vous vous sentez plus mal](/fr/patients/if-you-feel-worse): Si vous vous sentez plus mal à l'urgence, dites-le immédiatement à une infirmière ou à un membre du personnel en personne. Ce que fait aussi le bouton Je me sens plus mal, ce qui se passe hors ligne ou à l'extérieur, et quoi faire après votre retour à la maison.
    - [À faire](/fr/patients/to-do): Ce dont votre équipe de soins a besoin de votre part dans EDFlow : des échantillons, un consentement avant un examen, et des restrictions comme ne rien manger ni boire. Comment indiquer qu'une tâche est faite.
    - [Partager avec la famille](/fr/patients/share-with-family): Partagez une vue en direct de votre visite à l'urgence avec votre famille ou vos amis dans EDFlow : ce qu'ils peuvent voir ou non, comment envoyer le lien, la limite d'appareils, et comment arrêter le partage en tout temps.
    - [Mises à jour et notifications](/fr/patients/updates-and-notifications): Votre boîte de mises à jour, les notifications de l'application et les textos dans EDFlow : ce que nous envoyons, ce qu'affiche votre écran verrouillé (jamais de détails de santé), et comment les modifier ou les arrêter.
    - [Renseignements sur l'hôpital](/fr/patients/hospital-info): Trouvez les toilettes, la nourriture, le Wi-Fi, le stationnement, les règles pour les visiteurs, les interprètes et les réponses aux questions fréquentes de l'hôpital où vous êtes, et lisez les fiches d'information approuvées par son équipe de soins.
    - [Questions pour votre médecin](/fr/patients/questions-for-your-doctor): Notez vos questions pour votre médecin pendant que vous attendez. Le bloc-notes de EDFlow est enregistré seulement sur votre téléphone, n'est jamais envoyé à l'hôpital et s'efface quand votre accès prend fin.
    - [Paramètres](/fr/patients/settings): Changez la langue, la taille du texte, le contraste, le thème et les notifications dans EDFlow, verrouillez l'application avec Face ID ou une empreinte digitale, voyez les téléphones connectés à votre visite, et déconnectez-vous.
    - [Après votre visite](/fr/patients/after-your-visit): Votre résumé de départ, les dates de suivi à ajouter à votre calendrier, le lien vers le résumé, le court sondage, et le moment où votre accès à EDFlow prend fin après votre départ de l'urgence.
    - [Vie privée](/fr/patients/privacy): Ce que EDFlow conserve sur votre visite à l'urgence et pendant combien de temps, qui peut voir quoi, pourquoi les notifications ne contiennent jamais de détails de santé, et comment garder votre visite privée sur un téléphone partagé.
    - [Dépannage](/fr/patients/troubleshooting): Réglez les problèmes courants avec EDFlow pendant votre visite à l'urgence : pas de connexion, information peut-être retardée, mises à jour suspendues, code qui ne fonctionne pas, accès bloqué ou trop d'appareils.
    - [Poser une question à l'assistant](/fr/patients/ask-the-assistant): Posez à EDFlow des questions sur votre propre visite, comme la durée habituelle d'une étape, le nom de votre infirmière ou l'emplacement des toilettes. Ce que l'assistant peut faire ou non, et comment il traite vos messages.
  - Famille et amis
    - [Pour la famille et les amis](/fr/family): Une personne vous a partagé sa visite à l'urgence dans EDFlow. Ce que vous verrez (son étape, des attentes approximatives et qui s'occupe d'elle), ce que vous ne verrez pas (examens, résultats, emplacement) et pourquoi.
    - [Ouvrir votre lien](/fr/family/open-your-link): Comment ouvrir le lien de suivi de visite qu'une personne vous a partagé dans EDFlow : touchez Voir les mises à jour, choisissez votre langue, la limite de 3 appareils, et l'application au lieu du navigateur.
    - [Mises à jour](/fr/family/updates): Recevez un texto ou une notification de l'application quand la personne que vous suivez franchit une grande étape, consultez l'historique des mises à jour et les renseignements sur l'hôpital, et utilisez l'aide pour la famille là où l'hôpital l'offre.
    - [Quand les mises à jour prennent fin](/fr/family/when-updates-end): Pourquoi les mises à jour pour la famille dans EDFlow s'arrêtent : la personne a cessé de partager, la durée choisie est écoulée ou elle a quitté l'urgence. Ce que vous voyez quand les mises à jour prennent fin ou sont suspendues.
    - [Questions de la famille](/fr/family/faq): Réponses pour la famille et les amis qui suivent une visite à l'urgence dans EDFlow : pourquoi vous ne voyez pas les résultats d'examens, si vous pouvez appeler l'urgence, et quoi faire quand le lien indique trop d'appareils.
- Équipe de soins
  - [Sign-in and security](/fr/staff/sign-in-and-security): How staff sign in to EDFlow: accepting an invite, the password policy, two-step sign-in (MFA), Sign in with Microsoft, the idle lock, switching sites, sessions, and the companion app's biometric lock.
  - [Board](/fr/staff/board): The EDFlow live board: stats row, columns, alerts, filters, saved views, bottleneck flags, keyboard shortcuts, the command palette and big-board mode.
  - [Patient detail](/fr/staff/patient-detail): The EDFlow patient detail page: the header, the tabs (overview, tests, tasks, care team, requests, going home, sharing and access, activity), provenance of each fact, audited opening, and confidential and provisional patients.
  - [What patients see](/fr/staff/what-patients-see): The same visit in the EDFlow staff console and on the patient's phone, side by side, so staff can answer patient questions about stages, estimates, tests and requests.
  - [Requests](/fr/staff/requests): The EDFlow request queue: how patient requests are routed, acknowledging and resolving, service levels and escalation, the urgent I feel worse path (Going now, Can't go), the support queue and desktop notifications.
  - [Manual console](/fr/staff/manual-console): Run EDFlow visit states by hand when there is no EHR feed or the feed is wrong: every manual action, the 10-second undo, overrides, back-dating and validation warnings.
  - [Visit cards and sign-in help](/fr/staff/visit-cards-and-sign-in-help): Print a EDFlow visit card at a registered print station, approve staff-assisted sign-in with the patient's pairing code, and reissue a lost card, without staff ever holding a usable patient credential.
  - [Codes and department status](/fr/staff/codes-and-department-status): See active codes and the department volume level in EDFlow, who can call, clear or post a delay notice for a code, and exactly what patients, family and the waiting-room display see.
  - [Companion app](/fr/staff/companion-app): The EDFlow staff companion app on hospital-managed phones: request inbox, my patients, patient card, department, on-shift status, scanning a visit card, and push notifications while on shift.
  - [Privacy at work](/fr/staff/privacy-at-work): PHIPA duties in plain words for EDFlow users: what is audited, confidential patients, never photographing the board, your recent actions, and how to talk to patients about the app.
  - [AI assistance](/fr/staff/ai-assistance): The EDFlow staff AI features: the request queue digest, the handover attention summary and patient message drafts. What each one reads, what you must review, and how they are turned off.
  - [Troubleshooting for staff](/fr/staff/troubleshooting): Fix common EDFlow problems for staff: the EHR feed is delayed or down, a patient says the app is wrong (report a data problem), sign-in and lock problems, missing sounds, and cards that don't print.
  - Personnel infirmier
    - [Nurses](/fr/staff/nurses): A nursing shift with EDFlow: going on shift, your zone and your patients, your request queue, tasks and family links, with a printable quick-reference card.
    - [Triage](/fr/staff/nurses/triage): Triage nurses in EDFlow: the waiting-room request pool, reassessment due and overdue, re-triage requests, cards after triage, staff-assisted sign-in, the busy banner, and answering how much longer.
    - [Tasks](/fr/staff/nurses/tasks): Patient tasks in EDFlow: which tasks are created automatically from orders (urine samples, consent, check before eating, nothing by mouth), adding tasks from templates, and confirming tasks patients mark done.
    - [Publishing the going-home summary](/fr/staff/nurses/after-visit-summary): Compose, preview and publish the EDFlow going-home summary from approved templates, mark Cleared to leave, edit or unpublish, and what the patient receives.
    - [Family links](/fr/staff/nurses/family-links): See and revoke a visit's family links in EDFlow, lock sharing, pause updates to break news in person, and understand why sharing is unavailable for some visits.
    - [My metrics for nurses](/fr/staff/nurses/my-metrics): Nurse self-view metrics in EDFlow where the site turns them on: your request first-response times and the alerts you receive per hour, visible only to you.
  - Médecins
    - [Physicians](/fr/staff/physicians): Physicians, residents, nurse practitioners and physician assistants in EDFlow: Assign me, Seen and Seen again, why the seen time matters to the patient's screen, NACRS PIA, and a quick-reference card.
    - [Results and reassessment](/fr/staff/physicians/results-and-reassessment): How result status reaches patients in EDFlow: the site's results display delay, holding and releasing results, all results back, serial tests, reassessment, and the results-back digest.
    - [Calling a code](/fr/staff/physicians/calling-a-code): How to call a code in EDFlow in two steps: pick the type and the patient it's for, review who will be excluded and notified, then confirm. Code categories, who is notified, and the patient delay notice.
    - [Going-home summary rules for physicians](/fr/staff/physicians/after-visit-summary): Content rules for the EDFlow going-home summary for physicians: no diagnosis text from the EHR, the prescriber-attested medicines section, follow-up and red flags from approved templates.
    - [My metrics for physicians](/fr/staff/physicians/my-metrics): Per-physician step metrics in EDFlow: definitions, the private self view against blinded peer ranges, case-mix context, and why there are never ranks.
    - [Your profile](/fr/staff/physicians/your-profile): Control how patients see you in EDFlow: the name display policy, the optional photo, being hidden from patients, linked EHR identities, and your notification settings.
  - Infirmières et infirmiers responsables
    - [Charge nurses](/fr/staff/charge): Running the emergency department with EDFlow as charge nurse: zones and shifts, codes, department volume, escalations, overrides, feed downtime, analytics and a quick-reference card.
    - [Zones and shifts](/fr/staff/charge/zones-and-shifts): Assign nurses to zones, the triage pool, the support pool, charge and the physician in charge in EDFlow, and how those assignments route patient requests and decide who is on shift.
    - [Department volume](/fr/staff/charge/department-volume): Set the department volume level in EDFlow (normal, busy, very busy, surge), how suggestions are computed, imaging service status, and what patients, family, the entry page and the waiting-room display show.
    - [Codes](/fr/staff/charge/codes): Charge nurses and codes in EDFlow: call, extend, clear and cancel codes, resolve paged codes, post the delay notice, merge and throttle rules, and which categories can notify patients.
    - [Escalations](/fr/staff/charge/escalations): Request service levels and escalation in EDFlow for charge nurses: urgent requests without a response, Going now timers, thinking of leaving, over-the-usual-wait alerts and reassessments overdue.
    - [Overrides and corrections](/fr/staff/charge/overrides-and-corrections): Override EHR data in EDFlow when the feed is wrong, undo a console action, correct a time (including the PIA), reopen a departed visit, cancel a duplicate and link a downtime registration.
    - [When the EHR feed is down](/fr/staff/charge/feed-down): What to do when the EDFlow EHR feed is delayed or down: what patients see, frozen estimates, the downtime procedure and kit, running the manual console, and handing back to the feed.
    - [Department analytics for the charge nurse](/fr/staff/charge/analytics): Department analytics a charge nurse can open in EDFlow: today's flow and bottlenecks, and Ask your data where the site has turned it on, with what it can and can't answer.
    - [Big board and handover](/fr/staff/charge/big-board-and-handover): Big-board mode for the staff station in EDFlow (initials only, auto-paging, no actions, big-board station credentials) and the per-nurse handover summary.
  - Personnel de l'inscription
    - [Registration clerks](/fr/staff/clerks): What registration clerks see and do in EDFlow: the limited board, visit cards and the print queue, manual registration, lost cards, sign-in help, and confidential and unknown patients.
    - [Visit cards](/fr/staff/clerks/visit-cards): The EDFlow visit card print queue: automatic printing after triage, the 15-minute reprint window, card layouts and recipients, the print station, and what's printed on the card.
    - [Register a patient](/fr/staff/clerks/register-a-patient): Register a patient by hand in EDFlow at manual-mode sites or during EHR downtime: the fields, the minimal data profile, the duplicate check, triage and the card recipient.
    - [Lost cards and access](/fr/staff/clerks/lost-cards-and-access): Replace a lost or wrongly given EDFlow visit card, sign out a patient's devices, handle This wasn't me alerts and possible wrong-patient sign-ins, and revoke access.
    - [Helping patients sign in](/fr/staff/clerks/helping-patients-sign-in): Help a patient sign in to EDFlow on their own phone: staff-assisted pairing and the five most common sign-in problems, without ever handling their card code.
    - [Confidential and unknown patients](/fr/staff/clerks/confidential-and-unknown-patients): Set or clear the confidential (no-information) flag in EDFlow, confirm a provisional identity for an unknown patient, and what each does to the board, cards and family sharing.
- Administrateurs
  - [Users and access](/fr/admin/users-and-access): Manage EDFlow staff accounts: invites, roles and the full permission matrix, approvals for privileged roles, deactivation, unlock and MFA reset, bulk import and SCIM, and the quarterly access review.
  - Paramètres
    - [Site settings](/fr/admin/settings): How EDFlow site settings work: allowed ranges, settings locked in production, privacy-reducing changes, approvals, history and revert, configuration transfer, and the full settings reference.
    - [Hospital information](/fr/admin/settings/hospital-information): Set the hospital information patients and family see in EDFlow: names, address and entrance, phones, Wi-Fi, parking, visitor policies, wayfinding points with maps, the patient portal and co-branding.
    - [Zones, beds and shifts](/fr/admin/settings/zones-beds-and-shifts): Define EDFlow zones with their streams, beds and EHR location codes, treatment-space capacity, shift times and the CTAS reassessment intervals for the waiting room.
    - [Request types](/fr/admin/settings/request-types): Edit the EDFlow request catalogue: enable, reorder and customise request types, routes and pools, FYI-only types, care-flag rules, service-level targets, and the locked I feel worse request.
    - [Code types](/fr/admin/settings/code-types): Configure the EDFlow code-type catalogue: Ontario colour-code defaults, categories and patient notification rules, notice stages and scope, durations, optional templates and paging location filters.
    - [Tests and benchmarks](/fr/admin/settings/tests-and-benchmarks): The EDFlow test catalogue: EHR code mappings, patient-visible names and steps, sensitive and hidden tests, result thresholds per imaging modality, service hours, default benchmarks, estimate settings and historical import.
    - [Patient content](/fr/admin/settings/patient-content): Govern patient-facing content in EDFlow: education sheets, going-home templates, task templates, FAQ and glossary; the draft, clinical review, approval and publish workflow; and AI drafting help.
    - [Languages](/fr/admin/settings/languages): Configure languages in EDFlow: English and French, the site default and active offer of French, up to five safety locales for the safety-critical messages, and translation completeness.
    - [Privacy and retention](/fr/admin/settings/privacy-and-retention): Configure EDFlow privacy and access settings: patient and family access windows, sharing limits, the data profile, youth-confidential ages, results display delay, retention periods and de-identification.
    - [Notifications](/fr/admin/settings/notifications): Configure EDFlow notification channels per site: push, patient and family text messages (Twilio), email (Resend), the generic lock-screen default, rate caps, sending a test, and clinical communication platforms.
    - [Waiting-room display](/fr/admin/settings/waiting-room-display): Set up the EDFlow waiting-room display: public or key access, the official typical wait, slides, language mode, orientation, embedding, and registering big-board and print stations.
  - [Announcements](/fr/admin/announcements): Post, schedule and expire EDFlow site announcements for the entry page, patients, family, the waiting-room display and staff, with approved templates, a 280-character limit and link rules.
  - Analyses
    - [Analytics](/fr/admin/analytics): EDFlow analytics conventions and every metric definition: time zones, T0, percentiles, small-cell suppression, Ontario LOS groups, filters, annotations and exports, generated from the same definitions the computations use.
    - [Flow and bottlenecks](/fr/admin/analytics/flow-and-bottlenecks): Find where ED time is lost with EDFlow: flow segments from arrival to departure, the per-visit bottleneck flag, the period bottleneck ranking by excess minutes, heatmaps, trends and capacity drivers.
    - [Test turnaround](/fr/admin/analytics/test-turnaround): Test turnaround analytics in EDFlow: order-to-result and collection-to-result times per test, hour-by-weekday heatmaps, bucket coverage, the estimate level patients get, and the benchmark job.
    - [Request analytics](/fr/admin/analytics/requests): Request analytics in EDFlow: volume by type, zone and hour, time to first response and to resolve, urgent in-person response, service-level compliance, escalations and alerts per nurse per hour.
    - [Clinician metrics](/fr/admin/analytics/clinician-metrics): Per-physician step metrics in EDFlow: attribution, the blinded and named views, case-mix context, the minimum sample size, governance, and why there are never ranks or league tables.
    - [Feedback](/fr/admin/analytics/feedback): Patient feedback analytics in EDFlow: the five-question post-visit survey, the in-visit pulse, response rates, top-box shares, comments hidden when they may contain personal information, and family feedback.
    - [Adoption and equity](/fr/admin/analytics/adoption-and-equity): Who uses EDFlow in your ED: the activation funnel from card to feedback, broken down by preferred language, age band, arrival mode and platform, and the equity panel that flags gaps over 10 points.
    - [Codes and delays](/fr/admin/analytics/codes-and-delays): Code and volume analytics in EDFlow: the code log, frequency by type and hour, patients notified, the descriptive code impact on waits, and time in each volume level.
    - [Estimate quality](/fr/admin/analytics/estimate-quality): Check that EDFlow wait estimates are honest: coverage of the 9-in-10 ceiling (target 88%), calibration, fallback levels, bucket coverage, the benchmark job and importing historical data.
    - [Ask your data](/fr/admin/analytics/ask-your-data): Ask plain-language questions about ED operations in EDFlow and get charts and reports built from de-identified analytics, with the query shown, plus anomaly alerts. What data it uses and how to review it.
  - [Reports and exports](/fr/admin/reports-and-exports): De-identified exports from EDFlow (visit facts, test turnaround, request facts, feedback, code log), how they are de-identified, the export log, single-use downloads and scheduled reports.
  - [AI](/fr/admin/ai): Turn EDFlow AI features on per site: the six layers that must all allow a feature, the governance gates G-AI-1 to G-AI-6, budgets, conversation retention, the kill switch, and where flagged conversations go.
  - [Pilot playbook](/fr/admin/pilot-playbook): Run a EDFlow pilot in your emergency department: baseline measurement, staff briefing and training mode, posters and QR signage, the first week, the weekly review and the success metrics.
  - [EDFlow Mail](/fr/admin/mail): EDFlow Mail for the company team: shared mailboxes, AI triage of every inbound email, rules, hybrid search, support tickets with auto-acknowledgement, and the rule that mail never carries patient health information.
  - Protection de la vie privée
    - [Privacy officers](/fr/admin/privacy): EDFlow for privacy officers: the audit log and what is logged, per-patient access reports, monitoring alerts A-1 to A-28, exports with second-person approval, incidents, emergency revoke and safety concerns.
    - [Access requests and retention](/fr/admin/privacy/access-requests-and-retention): Answer PHIPA access requests with a EDFlow visit-record export, place and lift legal holds, and understand the retention schedule, care records and de-identification after the operational window.
    - [Message outbox](/fr/admin/privacy/message-outbox): The EDFlow message outbox: every text, email and push attempt with masked recipients and masked links, delivery status, resend, and why invite and reset links are never kept.
    - [Vendor support access](/fr/admin/privacy/vendor-support-access): How time-boxed vendor support access to your EDFlow site works: no standing access, a ticket and reason, read-only or admin scope, at most 4 hours, notifications to managers and a full audit trail.
    - [AI review](/fr/admin/privacy/ai-review): Review flagged EDFlow AI conversations as part of the safety review group: what gets flagged, reason codes, conflict rules, what you see, and resolving safety events.
  - Analystes en intégration
    - [Integration analysts](/fr/admin/integration): EDFlow for integration analysts: feed health states and what each audience sees, per-source status, heartbeats, event counts, rejections by error code, roster discrepancies and feed alerts.
    - [Sources and keys](/fr/admin/integration/sources-and-keys): Register an EHR source in EDFlow, edit its versioned mapping profile, reveal a signing key once, rotate with two active key versions, and disable a source in an emergency.
    - [Event log](/fr/admin/integration/event-log): Read the EDFlow EHR event ledger: accepted, duplicate, buffered, ignored and rejected events, error codes, the allow-listed payload view, and validating a payload as a dry run.
    - [Unmapped codes](/fr/admin/integration/unmapped-codes): Map unmapped test and location codes from the EHR feed in EDFlow: map to a catalogue test, create an entry or ignore, the zero-unmapped go-live gate, and AI mapping suggestions.
    - [Dead letters](/fr/admin/integration/dead-letters): Handle EDFlow dead letters: buffered events that expired and processing errors, viewing and revealing payloads (audited), replaying after a fix, discarding, and bulk replay.
    - [Data issues](/fr/admin/integration/data-issues): Work the EDFlow Report a data problem queue: what staff report, resolving or closing reports, and how data issues feed the 98% milestone agreement go-live gate.
    - [Simulator](/fr/admin/integration/simulator): The EDFlow EHR simulator for the sandbox and showcase: fire the next event for a visit, run scripted scenarios, autopilot a synthetic department, choose the transport (direct, signed webhook, HL7 v2, FHIR) and control the feed.
- Développeurs
  - [Quickstart](/fr/developers/quickstart): Create a sandbox app, get an OAuth token, check health, send a heartbeat, an arrival and a triage event, watch the patient appear on the sandbox board, and receive your first webhook, in about 15 minutes.
  - [Concepts](/fr/developers/concepts): How the EDFlow integration model works: sites, sources, encounters and events, facts and derived stages, projections and minimum necessary data, idempotency, ordering and precedence, and the early-arrival buffer.
  - [Authentication](/fr/developers/authentication): Authenticate to the EDFlow Integration API: OAuth 2.0 client credentials with private_key_jwt, client secret or mTLS, short-lived JWT access tokens, scopes, network binding, HMAC source keys for the signed ingest profile, clock skew, lockouts and signing at send time.
  - [Credentials](/fr/developers/credentials): Manage EDFlow API credentials: self-serve in the developer portal or issued by the hospital or the vendor, shown once, rotation with overlap, expiry reminders, revocation, and what to do if a key leaks.
  - API reference
    - [API reference](/fr/developers/api): The EDFlow Integration API reference: base URLs per environment, the pinned API version, conventions for ids, lists and incremental sync, errors, rate limits, the sandbox playground, and the OpenAPI and Postman downloads.
    - Codes
      - [List code alerts](/fr/developers/api/codes/listCodeAlerts): Department code alerts (default: active). `area` is omitted when the site turns `integration.api.includeCodeArea` off.
    - Documents
      - [Get a visit document](/fr/developers/api/documents/getDocument): Fetch a visit document by id (Phase 3). Requires `documents:read` and a token obtained with `private_key_jwt` or mTLS; documents are available for 72 hours.
    - Encounters
      - [Get an encounter's care team](/fr/developers/api/encounters/getCareTeam): The current care team. Zone-derived nurses are computed at read time (`id: null`, `source: zone`). Staff hidden from patients are listed with `hiddenFromPatients: true`.
      - [Get an encounter](/fr/developers/api/encounters/getEncounter): One encounter. `404` for unknown ids, other sites and archived encounters.
      - [List encounters](/fr/developers/api/encounters/listEncounters): Encounters ordered by `(updatedAt, id)`. `updatedSince` gives incremental sync; items updated in the last 10 seconds are held back (settle window).
      - [Look up an encounter by visit number](/fr/developers/api/encounters/lookupEncounter): Resolves an EHR visit number to an encounter without EDFlow storing the number. A miss is `200` with `found: false`. Rate-limited (`lookup`) and audited without the identifier.
    - Fhir
      - [FHIR CapabilityStatement](/fr/developers/api/fhir/getFhirCapabilityStatement): FHIR R4 CapabilityStatement (`kind: instance`). Declares only `batch`, `$process-message` and `$ingest`; there is no FHIR read API.
      - [$ingest OperationDefinition](/fr/developers/api/fhir/getFhirIngestOperationDefinition): The OperationDefinition of `$ingest` (canonical `https://edflow.space/fhir/OperationDefinition/ingest`).
      - [SMART configuration](/fr/developers/api/fhir/getSmartConfiguration): SMART Backend Services configuration: asymmetric client authentication (`private_key_jwt`) for token requests to the push endpoints only.
      - [Ingest a FHIR batch Bundle](/fr/developers/api/fhir/ingestFhirBundle): A FHIR R4 `batch` Bundle only (each entry processed independently). A `transaction` Bundle is refused with `422 transaction_not_supported`; other Bundle types go to `$ingest`. `Accept: application/fhir+json` answers a `batch-response` Bundle.
      - [Ingest another Bundle type ($ingest)](/fr/developers/api/fhir/ingestFhirCustom): `$ingest`: Bundle types FHIR does not allow at the base (`collection`, `searchset`, `history`), including Subscriptions Backport notifications. Handshakes and heartbeats produce no events.
      - [Process a FHIR message](/fr/developers/api/fhir/processFhirMessage): `$process-message`: a `message` Bundle whose first entry is a `MessageHeader`. Synchronous; duplicates (`Bundle.id` + `MessageHeader.id`, 30 days) replay the stored response. Data rejections answer 200 with `fatal-error`; transient failures answer 503 with `Retry-After`.
    - Hl7 v2
      - [Ingest HL7 v2](/fr/developers/api/hl7-v2/ingestHl7v2): Raw mode (`application/hl7-v2`, `x-application/hl7-v2+er7` or `text/plain`, optional `charset` that must agree with MSH-18): one ER7 message, answered with an ACK per the ACK table. JSON mode (`application/json`): `{ messages }` (≤ 50). Transient failures are `503`/`429` with `Retry-After` and no ACK. Site: `?site=`, else resolved from MSH-4 through the mapping profile. Engines must never hold their queue on a EDFlow ACK.
    - Ingest
      - [Get an ingest event](/fr/developers/api/ingest/getIngestEvent): One ledger row of the app's source by the source event id (URL-encoded). Metadata only.
      - [Ingest one event](/fr/developers/api/ingest/ingestEvent): One normalized event (≤ 32 KiB). `accepted`, `duplicate`, `ignored` and `superseded` answer 200; `buffered` and `quarantined` answer 202; a data rejection is `422 event_rejected`; a reused id with another payload is `409 idempotency_conflict`; a processing error is `503` (retry the same event).
      - [Ingest a batch of events](/fr/developers/api/ingest/ingestEventBatch): 1 to 100 normalized events, applied in array order, each atomically and independently. The 200 body is byte-compatible with `/ehr/v1/events`, so an engine can switch transports without changing response handling. A per-event `processing_error` is `retryable`: resend that event (same id).
      - [List ingest events](/fr/developers/api/ingest/listIngestEvents): The ingest ledger of the app's source (30 days), ordered by `(updatedAt, id)`. Metadata only, never payloads.
      - [Dry-run any input](/fr/developers/api/ingest/validateInput): Dry run for any input: nothing is persisted, notified or ledgered. The input kind comes from `Content-Type` (`application/json` events, `application/fhir+json`, `application/hl7-v2`, or JSON `{ messages }` with `?input=hl7v2`). The environment checks (processing id, sandbox tripwire) apply.
    - Metadata
      - [Health](/fr/developers/api/metadata/getHealth): Public liveness. Compare `time` with your own clock. `down` answers HTTP 503.
      - [Identity and configuration](/fr/developers/api/metadata/getMeta): Who the caller is and how the platform is configured for it: app, organization, sites, scopes, pinned version, credential, limits and webhook egress addresses.
      - [OpenAPI document](/fr/developers/api/metadata/getOpenApi): The OpenAPI 3.1 document of this deployment, generated from the operation registry. Identical to the published document except `servers`.
    - Oauth
      - [Get an access token](/fr/developers/api/oauth/createAccessToken): Issues a short-lived (≤ 300 s) ES256 access token (RFC 9068). Cache it and refresh 30 s before `expires_in`. Errors use RFC 6749 bodies; failed client authentication is rate-limited per (client id, source address).
      - [OAuth authorization server metadata](/fr/developers/api/oauth/getAuthorizationServerMetadata): RFC 8414 authorization server metadata. Lists every client authentication method this deployment supports.
      - [Token signing keys](/fr/developers/api/oauth/getTokenSigningKeys): Public keys of the access-token signing keys (ES256). Two keys are published during a rotation.
      - [Revoke an access token](/fr/developers/api/oauth/revokeAccessToken): RFC 7009. Always answers 200, even for unknown tokens. The next request with a revoked token gets `401 token_revoked`.
    - Requests
      - [Acknowledge a request from the EMR](/fr/developers/api/requests/acknowledgeRequest): Marks an open request as seen when a clinician handles it in the EMR. The patient sees the same result as a console acknowledgement: "Seen by {name}" for a linked practitioner, otherwise the generic care-team copy. Already acknowledged answers 200 with the current state; resolved or cancelled answers `409 conflict`. Requires the site's request write-back switch.
      - [Get a request](/fr/developers/api/requests/getRequest): One request.
      - [List requests](/fr/developers/api/requests/listRequests): The requests feed, ordered by `(updatedAt, id)`, with the 10-second settle window. Only requests past the patient's undo window appear.
      - [Resolve a request from the EMR](/fr/developers/api/requests/resolveRequest): Resolves a request from the EMR (acknowledging it first when open). Already resolved answers 200 with the current state; cancelled answers `409 conflict`.
    - Sandbox
      - [Create a patient request](/fr/developers/api/sandbox/sandboxCreateRequest): Creates a patient request on a synthetic encounter as if the patient tapped it (skipping the undo window), to test `request.created` webhooks and write-back.
      - [Get a conformance run](/fr/developers/api/sandbox/sandboxGetConformance): A conformance run and its checks with evidence.
      - [Get fault settings](/fr/developers/api/sandbox/sandboxGetFaults): The app's active fault settings.
      - [Reset the sandbox](/fr/developers/api/sandbox/sandboxReset): Resets the org's sandbox sites: deletes the app's ledger rows and webhook history for those sites.
      - [Run a simulator scenario](/fr/developers/api/sandbox/sandboxRunScenario): Runs a simulator scenario (for example `chest_pain_admit`, `lwbs`) through the chosen transport.
      - [Set fault injection](/fr/developers/api/sandbox/sandboxSetFaults): Makes this app's own requests fail or slow down (`503` with `Retry-After`, `429`, latency, token endpoint down) for ≤ 24 h. Other apps are unaffected. At most 5 faults.
      - [Start a conformance run](/fr/developers/api/sandbox/sandboxStartConformance): Starts a go-live conformance run: `ingest`, `webhooks`, `writeback`, `outage_recovery` (turns on a 30-minute `unavailable` fault), `clock_skew` (±90 s), `backfill_10k`.
    - Signed ingest
      - [Signed ingest: events](/fr/developers/api/signed-ingest/signedIngestEvents): Normalized events signed with the source key (`EDFlow-Source`, `EDFlow-Timestamp`, `EDFlow-Delivery-Id`, `EDFlow-Signature`). An exact replay of a processed delivery returns the stored 200 result.
      - [Signed ingest: FHIR](/fr/developers/api/signed-ingest/signedIngestFhir): A FHIR R4 Bundle signed with the source key; `EDFlow-Site-Code` names the site.
      - [Signed ingest: health](/fr/developers/api/signed-ingest/signedIngestHealth): Unauthenticated health of the signed ingest: `status`, `time` and `specVersions`.
      - [Signed ingest: HL7 v2](/fr/developers/api/signed-ingest/signedIngestHl7v2): JSON-wrapped HL7 v2 messages (≤ 50) signed with the source key; ACKs follow the ACK table.
      - [Signed ingest: validate](/fr/developers/api/signed-ingest/signedIngestValidate): Dry run of any of the three inputs (`EDFlow-Input`); persists nothing.
    - Sites
      - [List sites](/fr/developers/api/sites/listSites): The sites bound to the app, with feed state, volume and the site's capability switches.
    - Tasks
      - [List tasks](/fr/developers/api/tasks/listTasks): Patient tasks ordered by `(updatedAt, id)`, with the 10-second settle window.
    - Webhooks
      - [Create a webhook endpoint](/fr/developers/api/webhooks/createWebhookEndpoint): Creates an endpoint. The URL must pass the destination policy (HTTPS, public host, no private ranges). The `whsec_` signing secret is returned **once**.
      - [Delete a webhook endpoint](/fr/developers/api/webhooks/deleteWebhookEndpoint): Deletes an endpoint and cancels its pending deliveries.
      - [Get a delivery](/fr/developers/api/webhooks/getWebhookDelivery): One delivery with its thin payload and ≤ 10 attempts.
      - [Get a webhook endpoint](/fr/developers/api/webhooks/getWebhookEndpoint): One endpoint. Secrets and header values are never returned.
      - [List deliveries](/fr/developers/api/webhooks/listWebhookDeliveries): Deliveries of an endpoint, newest first (without payloads).
      - [List webhook endpoints](/fr/developers/api/webhooks/listWebhookEndpoints): The app's endpoints (≤ 20).
      - [List webhook event types](/fr/developers/api/webhooks/listWebhookEventTypes): The event catalogue with each type's data schema, sensitivity, expiry and `liveFrom`.
      - [Recover failed deliveries](/fr/developers/api/webhooks/recoverWebhookDeliveries): Redelivers every failed delivery since a time (≤ 14 days). Expired events are skipped unless `includeExpired`.
      - [Redeliver a message](/fr/developers/api/webhooks/redeliverWebhook): A new delivery of the same message (same `webhook-id`). An expired sensitive event needs `allowExpired`.
      - [Rotate the signing secret](/fr/developers/api/webhooks/rotateWebhookSecret): Adds a new secret version; both sign during the overlap (1–168 h, default 24 h). The new secret is shown once.
      - [Send a test message](/fr/developers/api/webhooks/sendWebhookTest): Posts a `webhook.test` message synchronously and returns the attempt.
      - [Update a webhook endpoint](/fr/developers/api/webhooks/updateWebhookEndpoint): Updates an endpoint. Re-enabling an auto-disabled endpoint is `status: enabled`; then `recover`.
      - [A code was called](/fr/developers/api/webhooks/webhook-code.called): A department code is active (after the two-step confirmation). No patient data.
      - [A code ended](/fr/developers/api/webhooks/webhook-code.cleared): A code was cleared, cancelled or expired.
      - [A code changed](/fr/developers/api/webhooks/webhook-code.updated): A code was extended or its patient notice changed.
      - [A patient opened the visit](/fr/developers/api/webhooks/webhook-encounter.access_activated): The first patient session on the visit.
      - [The visit stage changed](/fr/developers/api/webhooks/webhook-encounter.stage_changed): The derived stage changed. Expires after 6 hours or when a newer stage change exists.
      - [Feed state changed](/fr/developers/api/webhooks/webhook-feed.state_changed): A site's feed moved between healthy, delayed and down.
      - [An event was dead-lettered](/fr/developers/api/webhooks/webhook-ingest.dead_lettered): A buffered event expired or a data rejection was dead-lettered; fix the mapping and replay it.
      - [A roster was quarantined](/fr/developers/api/webhooks/webhook-ingest.roster_quarantined): The roster circuit breaker held a department roster for a person to confirm or discard.
      - [A credential is expiring](/fr/developers/api/webhooks/webhook-integration.credential_expiring): Sent 30, 7 and 1 days before a credential expires.
      - [A request was acknowledged](/fr/developers/api/webhooks/webhook-request.acknowledged): From the staff console, the companion app or the API.
      - [A request was cancelled](/fr/developers/api/webhooks/webhook-request.cancelled): The patient cancelled the request.
      - [A patient sent a request](/fr/developers/api/webhooks/webhook-request.created): The request passed the patient's 5-second undo window. Expires after 2 hours, or at once when it is no longer open.
      - [A request was escalated](/fr/developers/api/webhooks/webhook-request.escalated): A step of the escalation ladder. Expires after 1 hour, or when it is no longer open.
      - [A request was resolved](/fr/developers/api/webhooks/webhook-request.resolved): Resolved by staff, by the API, or closed at departure.
      - [A patient completed a task](/fr/developers/api/webhooks/webhook-task.completed): The patient marked a task done.
      - [Staff confirmed a task](/fr/developers/api/webhooks/webhook-task.confirmed): Staff confirmed a patient-completed task.
      - [A communication log is ready](/fr/developers/api/webhooks/webhook-visit.communication_log_ready): At departure when document write-back (Phase 3) is on. Fetch it with `GET /v1/documents/{documentId}` within 72 hours.
      - [Test message](/fr/developers/api/webhooks/webhook-webhook.test): Sent by the portal's Send test button or `POST /v1/webhook-endpoints/{id}/test`.
  - [Webhooks](/fr/developers/webhooks): Receive signed EDFlow webhooks (Standard Webhooks): subscribe, verify signatures, deduplicate on webhook-id, order by version, expiry, retries and auto-disable, authenticating to your gateway, event types, and redelivery.
  - Event reference
    - [Event reference](/fr/developers/events): The EDFlow normalized event contract: the envelope, prohibited fields (the PHI tripwire), identifiers never allowed in ids, shared types, and every inbound event type with JSON Schemas to download.
    - [admission.status_changed](/fr/developers/events/admission-status-changed): Bed flow for an admitted patient waiting in the ED.
    - [careteam.member_assigned](/fr/developers/events/careteam-member-assigned): One care-team member was assigned.
    - [careteam.member_released](/fr/developers/events/careteam-member-released): One care-team member was released.
    - [careteam.snapshot](/fr/developers/events/careteam-snapshot): The authoritative team asserted by this source, limited to rolesCovered.
    - [consult.status_changed](/fr/developers/events/consult-status-changed): A consult was requested, started, completed or cancelled.
    - [department.census_reported](/fr/developers/events/department-census-reported): Aggregate department status with no identifiers.
    - [department.code_called](/fr/developers/events/department-code-called): An emergency code was called.
    - [department.code_cleared](/fr/developers/events/department-code-cleared): A code was cleared.
    - [department.roster_reported](/fr/developers/events/department-roster-reported): The complete list of encounters active in the ED, for reconciliation.
    - [encounter.arrived](/fr/developers/events/encounter-arrived): Registration or arrival at the ED.
    - [encounter.assessed](/fr/developers/events/encounter-assessed): The physician initial assessment or a reassessment.
    - [encounter.cancelled](/fr/developers/events/encounter-cancelled): The registration was voided.
    - [encounter.departed](/fr/developers/events/encounter-departed): The patient physically left the ED.
    - [encounter.departure_cancelled](/fr/developers/events/encounter-departure-cancelled): The discharge was reversed.
    - [encounter.disposition_decided](/fr/developers/events/encounter-disposition-decided): A decision to discharge, admit, observe or transfer.
    - [encounter.location_changed](/fr/developers/events/encounter-location-changed): A bed or area move, leave of absence or return.
    - [encounter.triaged](/fr/developers/events/encounter-triaged): Triage completed, or a re-triage.
    - [order.placed](/fr/developers/events/order-placed): A test or diagnostic order (the full order asserted each time).
    - [order.results_reviewed](/fr/developers/events/order-results-reviewed): A clinician acknowledged the results.
    - [order.status_changed](/fr/developers/events/order-status-changed): The current status of an order, with every timestamp known so far.
    - [patient.merged](/fr/developers/events/patient-merged): Two MRNs were merged.
    - [patient.updated](/fr/developers/events/patient-updated): A demographic or privacy correction.
    - [system.heartbeat](/fr/developers/events/system-heartbeat): Feed liveness.
  - [FHIR R4](/fr/developers/fhir): Send FHIR R4 to EDFlow: batch Bundles, the $ingest operation for collection, searchset and Subscriptions Backport notifications, $process-message, how each resource maps to events, Epic and Oracle Health notes, and a worked example.
  - [HL7 v2](/fr/developers/hl7v2): Send HL7 v2 to EDFlow over HTTPS: supported versions and vendors (Epic Bridges, Oracle Health Millennium, MEDITECH), triggers and the events they produce, result and order status maps, the field map, character sets and escapes, the ACK table, and a worked example stream.
  - [Mapping profiles](/fr/developers/mapping-profiles): The versioned EDFlow site mapping profile: encounter filters and identifiers, locations and beds, CTAS codes, roles and practitioner ids, dispositions, order and consult codes, NPO diet codes, result thresholds, privacy options, and unmapped-code governance.
  - [Sandbox](/fr/developers/sandbox): Create a sandbox app and develop against the EDFlow sandbox: synthetic-only enforcement, fictional hospitals, simulator scenarios, dry-run validation, fault injection, conformance profiles including outage_recovery, and resetting, plus how customer test differs.
  - [SDKs and snippets](/fr/developers/sdks-and-snippets): Code snippets in cURL, TypeScript and Python for every EDFlow API operation, signing helpers for the signed ingest profile with the conformance test vector, the OpenAPI document, Postman collection and typed clients.
  - [AI mapping assistant](/fr/developers/ai-mapping-assistant): Use the EDFlow mapping assistant to draft a site mapping profile from sample HL7 v2, FHIR or CSV: synthetic samples only in the sandbox, allow-list scrubbing, a proposed profile validated against the event schema, and nothing applied without review.
  - [Errors](/fr/developers/errors): Every EDFlow error code: request-level HTTP status on the signed ingest profile, per-event result codes, and REST API problem details (RFC 9457) with retryable flags and the retry action to take first.
  - [Rate limits and retries](/fr/developers/rate-limits-and-retries): EDFlow rate limits per bucket, the RateLimit headers, which errors to retry and how, exponential backoff with jitter, idempotency keys, and batching and size limits.
  - [Versioning and deprecation](/fr/developers/versioning-and-deprecation): How the EDFlow API and event contract are versioned: the URL major version, dated Api-Version pins, specVersion, notice periods for new enum values and event types (60 days) and breaking changes (12 months), Deprecation and Sunset headers, and host migration.
  - [Go live](/fr/developers/go-live): Take a EDFlow integration live: sandbox conformance, the customer-test shadow run and the 98% milestone agreement gate, promotion with four-eyes approval and the PIA attestation, cut-over, and monitoring after go-live.
  - API changelog
    - [API changelog](/fr/developers/changelog): Changes to the EDFlow Integration API and event contract: dated API versions, additive releases, announced enum values and event types, deprecations and sunsets.
  - [Build with AI](/fr/developers/build-with-ai): Point Claude Code, Cursor or another coding assistant at the EDFlow docs: llms.txt, llms-full.txt, a Markdown version of every page, the docs MCP server, and the rules to give your agent.
  - [SMART on FHIR](/fr/developers/smart-on-fhir): The optional SMART on FHIR launch that opens a patient's EDFlow card inside Epic or Oracle Health FirstNet without a second login: the flow, prerequisites per vendor, and why staff access stays invite-only.
  - [EHR write-back](/fr/developers/ehr-write-back): Options for sending EDFlow activity back to the EHR: request write-back through the API, an optional end-of-visit communication log document, and why the pilot stays read-only.
  - [Engine configuration](/fr/developers/engine-configuration): Configure your integration engine for EDFlow: store and forward, a queued destination that never holds the queue on AE or AR, signing and token refresh at send time, surviving a 30-minute outage, heartbeats and rosters, dead letters, and Mirth Connect / OIE templates with Rhapsody and Cloverleaf notes.
  - [FHIR implementation guide](/fr/developers/fhir-implementation-guide): The EDFlow ED Visit Workflow FHIR implementation guide: base profiles on CA Baseline, must-support and prohibited elements, terminology and canonical URLs, the $ingest operation, examples, and validating with the HL7 FHIR validator.
- TI et sécurité
  - [Architecture](/fr/security/architecture): EDFlow system context and runtime containers for hospital reviewers: the web tier, the Convex backend, the mobile apps, the integration engine link, optional providers, environments and what runs where.
  - [Data flow](/fr/security/data-flow): How data moves from the EHR to the patient's screen in EDFlow, what crosses each boundary and what never does, and the data inventory by privacy class with retention.
  - [PHIPA roles and privacy](/fr/security/phipa): EDFlow under Ontario's PHIPA: the hospital as custodian, the vendor as agent and electronic service provider, voluntary HINP duties, minimum necessary, consent for family sharing, patient access, breach notification, and PIA and TRA support.
  - [Controls](/fr/security/controls): The EDFlow controls matrix: authentication and MFA, server-side authorization and projections, token hashing, encryption, rate limits, audit, log redaction, security headers and CSP, supply chain, vulnerability management and penetration testing.
  - [Threat model](/fr/security/threat-model): A summary of the EDFlow threat and risk assessment: attacker models, STRIDE threats per component, the top risks and their mitigations, and residual risks.
  - [Data residency](/fr/security/data-residency): Where EDFlow stores hospital data: AWS ca-central-1 with disaster recovery in ca-west-1, backups in Canada, RPO and RTO, the web tier in Montréal, and which environments hold synthetic data only.
  - [Subprocessors](/fr/security/subprocessors): Every EDFlow sub-processor with its purpose, whether health information can reach it, the data categories, its location and when it applies, from the single list shared with the privacy page and the security review pack.
  - [Accessibility](/fr/security/accessibility): EDFlow accessibility conformance for hospital reviewers: WCAG 2.2 AA on every surface, how it is tested (axe in CI, keyboard, screen readers, Dynamic Type and font scale), the conformance report, and known issues.
  - [Identity and SSO](/fr/security/identity-and-sso): Staff identity in EDFlow: Microsoft Entra ID setup, MFA policy per role, the session policy table, SCIM provisioning and deprovisioning, and how patient and family access differs.
  - [Network requirements](/fr/security/network-requirements): Hosts and ports to allow for EDFlow: web, the realtime WebSocket, push notifications, integration-engine egress to the API, the waiting-room display kiosk, and guest Wi-Fi guidance for patients.
  - [Devices and device management](/fr/security/devices): Devices for EDFlow: staff phones under MDM and the managed-device requirement, shared workstations, print and big-board stations, the waiting-room kiosk, and patients' own phones.
  - [Availability and incidents](/fr/security/availability-and-incidents): EDFlow service levels: the support severity matrix with 24/7 P1 response within 30 minutes, the 24-hour breach notice, maintenance windows and notice, SLOs and the HA topology they depend on, RPO and RTO, DR drills and the status page.
  - [Audit logging](/fr/security/audit-logging): What EDFlow records in its audit log, the record format, append-only storage with a daily hash chain, proactive monitoring rules, per-patient access reports and SIEM export.
  - [AI governance](/fr/security/ai): How EDFlow governs AI: models and providers, zero data retention and no training, data classes C0 to C3, what leaves the tenant, human approval, the medical-device boundary, enablement gates G-AI-1 to G-AI-6, the kill switch and opting a visit out.
  - [Vulnerability disclosure](/fr/security/vulnerability-disclosure): How to report a security vulnerability in EDFlow: scope, safe-harbour rules, what to include, what never to do with patient data, response times, and security.txt.
  - [Compliance documents](/fr/security/compliance-documents): What EDFlow publishes, what is shared under NDA (the security review pack, PIA and TRA inputs, penetration test summary, questionnaire answers), the SOC 2 position stated accurately, and how to request documents.
  - [Privileged access](/fr/security/privileged-access): How EDFlow vendor staff can and cannot reach production: no standing access, audited time-boxed support access, break-glass with approval and session recording, two-person deployments, personnel security, and data return and destruction.
- Marque
  - [Hospital communications](/fr/brand/hospital-communications): Posters, QR signage, visit cards, the waiting-room display and co-branding rules for hospitals running EDFlow, with the safety messages every piece must carry.
  - [Writing patient content](/fr/brand/writing-patient-content): Voice, tone and word choices for hospital authors writing EDFlow patient content (education sheets, going-home templates, FAQ, announcements), with French typography rules and the words never to use.
  - [Press kit](/fr/brand/press-kit): EDFlow logos, a curated screenshot pack captured from fictional sample data, and boilerplate text for articles, hospital newsletters and announcements.
- Notes de version
  - [Release 1.2](/fr/releases/1-2-0): EDFlow 1.2: the Integration API and developer portal, signed webhooks, the documentation site with automated screenshots, brand configuration and co-branding, email and SMS delivery, and AI features that stay off until a site approves them.