FHIR BI
An advanced clinical BI that taps your HL7 messages — V2.x, V3, FHIR and DICOM — in real time. Beyond rejection analysis, FHIR BI lets clinicians model real data and produce reports on patients' health status.
Behind every chart, an HL7 message
No IT background needed. An HL7 message is simply the "slip" one system sends another at each event: an admission, a lab result, a prescription. Here is, in plain terms, what the few codes used in the reports below actually mean.
MSH|^~\&|LABO|CHUM|BI|CHUM|20240607083000||ORU^R01
Header — the CHUM lab sends a result on June 7 at 8:30 am.PID|1||1958031712^^^RAMQ||TREMBLAY^JEAN||19551103|M
Identity — TREMBLAY Jean, health-card number in the RAMQ registry, born Nov 3 1955.PV1|1|I|SI^12^01|||…
Location — the patient is admitted to the Intensive Care Unit (ICU).OBR|1||A1234567|CREAT^Renal panel
Exam — a renal panel was ordered (request number A1234567).OBX|1|NM|2160-0^Creatinine||298|umol/L|59-104|H
Result — Creatinine at 298 µmol/L, above normal (59–104), flagged "H" for "high".The vocabulary, at a glance
ADTPIDPV1-3OBR-4OBXDG1RXE · RXASPMA living clinical dashboard
Every HL7 message feeds the dashboard as it arrives. Clinical indicators update continuously — no extraction, no data warehouse.
Critical results (OBX) — last 7 days
OBX-8 flag = 'H' or 'HH'Admissions by unit (PV1-3)
TodayOBX-8 · Critical results — every lab result carries an abnormal flag (OBX-8: "H" = high, "L" = low, "HH/LL" = critical). Criticals received per day are counted.
ADT^A01 · PV1-3 · Admissions by unit — each admission message names the patient's receiving ward in field PV1-3.
ACK · Rejection rate — share of messages refused by the receiving system, flagged by a negative acknowledgement (ACK AR/AE).Cross one clinical variable against another, freely
Pick a measure and a dimension: FHIR BI does the rest. A clinician gets the answer in two clicks — without writing a single query.
Critical OBX results by care unit
Last 30 daysExam distribution (OBR-4)
- Biochimie 34%
- Hematology 27%
- Microbiologie 18%
- Imaging 14%
- Pathologie 7%
Critical results to follow
Live PID · PV1 · OBX correlation| Patient (PID-5) | Unit (PV1-3) | Test (OBX-3) | Value | Status |
|---|---|---|---|---|
| GAGNON, M. | ICU | Potassium | 6,4 mmol/L | Critical |
| TREMBLAY, J. | ER | Troponine | 0,92 µg/L | Critical |
| CÔTÉ, L. | Medicine | Hémoglobine | 71 g/L | Low |
| ROY, P. | ER | Glucose | 22,1 mmol/L | High |
| BÉLANGER, S. | Nephrology | Créatinine | 298 µmol/L | Critical |
OBX-5 · OBX-8 · PV1-3 — the bars count, per care unit (PV1-3), the results whose value (OBX-5) is flagged critical (OBX-8). The chart shows where critical values concentrate.
OBR-4 — the donut breaks activity down by requested exam type, read from the OBR-4 exam code.
PID-5 · OBX-3 · OBX-5 — the table joins, live, the patient name (PID-5), the performed test (OBX-3) and its measured value (OBX-5).Model the health status of a patient population
Tracking a diabetic patient cohort from lab results received over HL7. Every HbA1c and glucose value arrives in a result message (the OBX segment): FHIR BI automatically groups them by patient and computes the averages. The clinician builds the report just by picking variables — no technical skill required.
HbA1c distribution (%) — cohort
Patient count per bandCohort average glucose — 6 months (mmol/L)
Downward trendDG1 · The cohort — the selected patients are those whose diagnosis (DG1) is diabetes, coded E10–E11 in ICD-10.
OBX-3 · OBX-5 · HbA1c — the distribution reads the HbA1c value (OBX-5) of results identified by their test code (OBX-3), then splits them into control bands.
OBX-5 · Glucose — the curve plots the cohort's monthly average of measured glucose values (OBX-5).A heart-failure cohort rebuilt from HL7 messages. BNP is read from lab results (OBX) and LVEF from echocardiography reports. A readmission is flagged automatically when an already-discharged patient (discharge message, ADT A03) is re-admitted (admission message, ADT A01) within 30 days — all with no technical skill.
Distribution by LVEF
- Reduced (< 40%) 48%
- Mid-range (40–49%) 22%
- Preserved (≥ 50%) 30%
30-day readmission — 12 months (%)
Below the 20% targetOBR-4 · OBX-5 · FEVG — the ejection fraction is read (OBX-5) from echocardiography reports, identified by their exam code (OBR-4), then grouped into categories (preserved / mid-range / reduced).
OBX-5 · BNP — BNP (or NT-proBNP) comes straight from lab results (OBX-5).
ADT^A03 → A01 · 30-day readmission — FHIR BI pairs, for the same patient (PID), a discharge (ADT A03) followed by a new admission (ADT A01) occurring within 30 days.A chronic-kidney-disease cohort built from labs received over HL7. Creatinine and estimated GFR (eGFR) come from lab results (the renal-panel OBX), and the KDIGO stage — the severity of kidney impairment — is computed automatically from those values.
Distribution by KDIGO stage
Patient countCohort mean eGFR — 12 months (mL/min)
Slowed declineOBR-4 · OBX-5 · Creatinine & eGFR — creatinine and estimated GFR are read (OBX-5) from the renal panel (OBR-4).
KDIGO stage — FHIR BI automatically classifies each patient by eGFR: G1 (≥ 90) to G5 (< 15). No manual entry, no calculation by the clinician.
OBX-5 · Albuminuria — the urine albumin-to-creatinine ratio is also read from results (OBX-5) to flag un-screened patients.An oncology pathway reconstructed from the dates carried by HL7 messages. Each step is dated automatically: suspicion (exam-request date), diagnosis (pathology result), the multidisciplinary tumor board and treatment start. FHIR BI then computes the delay between each step.
Median delay per step vs target (d)
From referral to first treatmentMedian suspicion→treatment by site (d)
Last 30 daysOBR-7 · OBX-14 · Step dates — each step is dated by its HL7 message timestamp: the exam request (OBR-7), the pathology result (observation date OBX-14), the tumor board and treatment start.
Pathway delays — FHIR BI subtracts these dates to get each step's delay, and automatically compares it to the target (≤ 28 days).
DG1 · Tumor site — the breakdown by site comes from the coded diagnosis (DG1, ICD-O topography).Antimicrobial-resistance surveillance from antibiograms received over HL7. Identified organisms and their antibiotic susceptibility are read from microbiology results (OBX), and antibiotic consumption is derived from drugs prescribed then administered (RXE, RXA).
Resistance (%): organism × antibiotic
Antibiograms from the last 90 days| Amox | Cipro | Ceftri | Pip-Tazo | Mero | |
|---|---|---|---|---|---|
| E. coli | 58 | 24 | 12 | 6 | 1 |
| K. pneumoniae | 72 | 31 | 18 | 9 | 3 |
| P. aeruginosa | 100 | 22 | 35 | 14 | 8 |
| S. aureus | 84 | 18 | 12 | 10 | 2 |
| Enterococcus | 12 | 40 | 90 | 30 | 5 |
Antibiotic consumption — 12 months (DDD/1000 d)
Downward trendOBX-3 · OBX-5 · Antibiogram — for each organism, the tested antibiotic (OBX-3) and its result — Susceptible, Intermediate or Resistant (OBX-5) — feed the organism × antibiotic resistance map.
SPM-4 · Organism & specimen — the identified organism and specimen type (blood culture, urine…) come from the specimen segment (SPM).
RXA · Antibiotic consumption — the curve is computed from antibiotics actually administered (RXA), converted to defined daily doses (DDD).Clinical cohorts
Diabetes, renal failure, oncology… define a population by its diagnosis (DG1 segment) or by a lab result (OBX segment).
Health trends
Track indicator trends (HbA1c, glucose, blood pressure) over time.
Shareable reports
Export and share the report with the clinical team or management.
A true clinical HL7 BI, with no IT training
Free cross-analysis
Cross any clinical variable against another — e.g. critical results by the care unit where the patient is.
Meaningful comparisons
Compare, for instance, CLSC vs hospital admissions by diagnosis or exam.
Instant charts
Trends, distributions, comparisons: the chart is built live, with no wait.
Full autonomy
Explore clinical data directly at the source, with no detour through the IT team.
PACS analytics, organized by domain
Every C-STORE association feeds these dashboards, grouped by theme: volume, performance, rejects, conformance, dose, metadata and capacity.
Activity & volume
PACS load: day × hour
Studies received (C-STORE) — typical week| 00–04 | 04–08 | 08–12 | 12–16 | 16–20 | 20–24 | |
|---|---|---|---|---|---|---|
| Lun | 12 | 40 | 210 | 180 | 90 | 30 |
| Mar | 10 | 38 | 225 | 190 | 95 | 28 |
| Mer | 11 | 42 | 240 | 200 | 100 | 32 |
| Jeu | 9 | 39 | 230 | 195 | 92 | 30 |
| Ven | 13 | 45 | 250 | 205 | 110 | 35 |
| Sam | 8 | 20 | 95 | 80 | 40 | 18 |
| Dim | 7 | 16 | 70 | 60 | 30 | 14 |
Top exams
StudyDescription (0008,1030) — 30 daysDistribution by modality
- CT 31%
- CR/DX 28%
- US 16%
- MR 14%
- MG 6%
- NM/XA 5%
Study volume — 12 months (thousands)
Upward trendPerformance & image access time
SLA compliance
Report < 60 minRetrieval by storage tier
Median retrieval timeAccess time by percentile
Time to first image (TTFI)Modalities: volume × delay × size
One bubble per modalityCapacity & storage
Storage capacity
Primary PACS arrayCumulative storage — 12 months (TB)
Growth ~ 0.7 TB / monthExam rejects by reason
Rejects by modality
Last 30 daysReject reasons
- Motion / blur 34%
- Positioning 26%
- Artifact 17%
- Exposure 13%
- Wrong protocol 6%
- Other 4%
Reject rate — 12 months (%)
Continuous improvementProtocol conformance
Conformance by protocol (target 95%)
% of exams following the approved protocolOverall conformance
All protocolsCT dose tracking (CTDIvol / DLP)
Median DLP vs DRL, by protocol
Diagnostic reference level (DRL) shown as the tickMedian DLP — 12 months (mGy·cm)
Continuous protocol optimizationDICOM metadata quality
Metadata completeness by tag
% of studies with a valid value · 99% thresholdConformance score
Key-tag metadataCross V2.x, V3, FHIR and DICOM on a single key
FHIR BI unifies the standards. Define a "join key" — a patient identifier (NAM, NIM, IPM, etc.) — and the tool automatically reconciles V2.x, V3 messages, FHIR resources and DICOM studies for the same patient.
The join key in action
Each standard exposes the patient identifier in a different fieldUnified patient record
Volume by unit, by standard
Messages joined on the patient key — 24 h- HL7 V2
- HL7 V3
- FHIR
- DICOM
Activity by standard — 12 months
Reconciled monthly volume- HL7 V2
- HL7 V3
- FHIR
- DICOM
Critical results: unit × test type
OBX (V2/V3) crossed with PV1-3 — 30 days| K+ | Troponine | Glucose | Creat. | Hb | |
|---|---|---|---|---|---|
| ER | 6 | 14 | 9 | 3 | 5 |
| ICU | 11 | 7 | 4 | 9 | 6 |
| Medicine | 4 | 2 | 7 | 5 | 8 |
| Surgery | 2 | 1 | 3 | 2 | 4 |
| CLSC | 1 | 0 | 5 | 1 | 2 |
Clinical example — patient journey
TREMBLAY, Jean · NAM TRJE 8203 1517 · joined on the keyOne imaging request, from order to report
The accession number links the HL7 order, the DICOM images and the report — a single request record, across all standards.
Join key — Accession number
The carrier field in each standardRequest journey
Events joined on accession A1234567Specimen traceability, from collection to result
The container identifier links the order, transport, lab receipt and analysis — a full chain of custody.
Join key — Container identifier
The carrier field in each standardChain of custody
Events joined on container C-88231Inform clinicians within seconds
Connected to the HL7 stream, HL7AI detects the critical event as the message arrives and notifies the right clinician immediately — instead of waiting for them to open the chart. Every second saved counts.
Potassium 6.8 mmol/L
ORU^R01 · OBX-5 = 6,8 · OBX-8 = HHPositive blood culture — S. aureus
ORU^R01 · OBX positive cultureInteraction — Warfarin + NSAID
RDE^O11 · new orderAllergy — Penicillin
RDE^O11 · AmoxicillinPulmonary embolism — CT angio
ORU^R01 · report · critical-finding codeTroponin 0.92 µg/L
ORU^R01 · OBX-8 = HINR 8.2 — anticoagulant overdose
ORU^R01 · OBX-5 = 8,2Glucose 1.8 mmol/L
ORU^R01 · OBX-8 = LLCreatinine 320 µmol/L — AKI
ORU^R01 · rapid riseHemoglobin 62 g/L
ORU^R01 · OBX-8 = LLSodium 118 mmol/L
ORU^R01 · OBX-8 = LLLactate 5.2 mmol/L
ORU^R01 · hypoperfusionOverdose — dose > maximum
RDE^O11 · RXE-doseTherapeutic duplication
RDE^O11 · 2 active PPIsHigh-alert medication — Insulin
RDE^O11Tension pneumothorax
ORU^R01 · critical findingIntracranial hemorrhage
ORU^R01 · TDM brainIncidental finding to monitor
ORU^R01 · follow-up recommendationHigh fall risk
ADT^A01 · history + ageEarly-warning score NEWS2 ≥ 7
ORU^R01 · vitals (OBX)Median notification delay
Diagnose and resolve integration incidents faster
For integration teams: every rejected message is analyzed automatically — faulty segment, acknowledgement code (AR/AE), cause and suggested fix — instead of reading logs by hand.
Automatic diagnosis
Reject analysis on arrivalPID-3AR · MSA-3 = « Missing required field PID-3 »Common support cases
Symptom, detected cause, HL7 field and action| Symptom | Detected cause | Segment / field |
|---|---|---|
| NAK (AR) on admissions | Missing patient identifier | PID-3 |
| Duplicate messages | Identical control ID | MSH-10 |
| Sequence gap | Non-contiguous sequence number | MSH-13 |
| Corrupted accents | ISO vs UTF-8 encoding | MSH-18 |
| Unrouted result | Unmapped exam code | OBR-4 |
| Unrecognized unit | Non-standard unit | OBX-6 |
| Interface down | MLLP connection lost | — |
Trace every message, from source to application
The Sankey diagram reveals the real data journey: which source systems feed which standards, and which clinical applications they are finally routed to. Each flow's thickness is proportional to its volume.
Source systems → standards → clinical applications
Daily volume · thickness ∝ message countAn accelerator for analyzing rejections and errors
For teams handling HL7 rejections, errors and inconsistencies.
- Clear visualization of faulty or inconsistent variables
- Correlation across multiple HL7 fields (e.g. PV1-2 vs PV1-3, OBR-4 vs OBX-3)
- Statistical analysis of rejection causes by facility, source system or period
- Quickly understand the "why" of a rejection, beyond the raw technical error message
Rejection causes by type
Last 7 daysConnected live to the National or Organizational Integration Agent's HL7 flow
Connected in real time to the integration agent's HL7 flow, the tool enables:
Immediate detection
Analysis of incoming messages as they arrive.
Near real-time tracking
Continuous tracking of rejections and critical alerts.
Proactive intervention
Act on at-risk flows before incidents occur.
Real-time integration monitoring
Monitor interface health: volumes, acknowledgements (ACK/NAK) and per-flow latency.
ACK rate — 12 months (%)
Positive acknowledgementsMedian latency by interface
Receive → ACKIncidents & resolution time
Categorize interface incidents and track the mean time to resolution (MTTR).
Incidents by category (30 d)
Technical causesMean time to resolution (MTTR) — 12 months (h)
Continuous improvementFlows, transport, stock and traceability
Reconstructed from HL7 (ADT, ORM, SPM) and DICOM messages — patient transport, specimens, reagents, sterilization, queues.
Patient transports — 12 months
Portering (per day)Source HL7 — ADT^A02 (transferts) + messages de brancardage. Each patient transfer fires an A02; events are counted per day to measure portering load.
Avg transport delay by unit
Request → pickupSource HL7 — ORM^O01 (demande) → ADT (prise en charge). The delay is the gap between the transport-request timestamp and arrival in the destination unit.
Bed occupancy by unit (%)
Bed management (PV1-3)Source HL7 — PV1-3 (localisation), ADT^A01/A02/A03. Admissions/discharges/transfers keep bed occupancy per unit current: occupied ÷ available beds.
Collection → lab receipt (min)
By collection siteSource HL7 — SPM-17 (date/heure de prélèvement) → OBR-14 (réception). Collection → lab-receipt time, computed per requesting unit.
ADT flow — 12 months
Admissions / transfers / discharges- Admissions
- Transfers
- Discharges
Source HL7 — ADT^A01 (admission), A02 (transfert), A03 (sortie). The three plotted volumes come straight from the event type carried in MSH-9 / EVN-1.
Specimens in transit — status
- In transport 19%
- Received 38%
- In analysis 37%
- Late 6%
Source HL7 — SPM-11 (rôle) + SAC (statut contenant). Each specimen's status (collected, in transit, received, rejected) is broken down into proportions.
Reagent stock vs threshold (%)
% of reorder levelSource HL7 — OMS^O05 (réquisition de stock) + RXA (consommation). Remaining reagent stock compared to the reorder threshold to anticipate stock-outs.
Stock-outs by category (30 d)
Source HL7 — OMS^O05 (statut « en rupture »). Count of stock-outs detected per supply category over the period.
Sterilization cycles / day
Typical weekSource HL7 — ORM^O01 (ordres de retraitement d'instruments). Sterilization cycles launched per day, from the CSSD reprocessing orders.
ER wait: day × hour (min)
Median time| 00–04 | 04–08 | 08–12 | 12–16 | 16–20 | 20–24 | |
|---|---|---|---|---|---|---|
| Lun | 45 | 60 | 180 | 210 | 150 | 80 |
| Mar | 42 | 58 | 175 | 205 | 145 | 78 |
| Mer | 40 | 55 | 185 | 215 | 155 | 82 |
| Jeu | 44 | 62 | 178 | 208 | 148 | 80 |
| Ven | 48 | 65 | 195 | 225 | 165 | 90 |
| Sam | 30 | 40 | 120 | 140 | 95 | 55 |
| Dim | 28 | 36 | 100 | 120 | 80 | 48 |
Source HL7 — ADT^A04 (admission urgence) + horodatages PV1-44/PV1-45. Time from triage to care, crossed by weekday × time slot.
No-show rate — 12 months (%)
Missed appointmentsSource HL7 — SIU^S12 (rendez-vous) vs ADT^A04 (présence). Scheduled appointments with no matching admission = no-show rate.
Pneumatic transport — sends/day
By serviceSource HL7 — OML^O21 (échantillon lié à l'ordre). Pneumatic-tube send volumes, correlated to lab orders per service.
Equipment utilization (RTLS)
- In use 64%
- Available 22%
- Maintenance 9%
- Missing 5%
Source — RTLS feed (real-time location), outside HL7. Mobile-equipment utilization status: in use, available, in maintenance, missing.
Room turnover time (min)
Discharge → readySource HL7 — ADT^A03 (sortie) → ADT^A01 (admission suivante). Time from a patient's discharge to the room being ready again (cleaning included).
Logistics message throughput — 12 months (k/day)
Stable queueSource HL7 — MSH (tous messages logistiques). Integration-engine throughput: ADT/ORM/OML messages processed per day, a queue-load indicator.
Revenue, costs, billing and coding
Clinical activity (ADT, procedures, DG1, results) becomes financial indicators: revenue by service, cost per stay, billing rejections, coding completeness.
Revenue by service (k$)
Current monthSource HL7 — DFT^P03 (transaction financière), FT1-16 (service), PV1-10. Each billed procedure produces a DFT; amounts are aggregated by requesting service.
Monthly billing ($M) — 12 months
Billed proceduresSource HL7 — DFT^P03 / FT1-6 (montant). Monthly sum of FT1 amounts across all financial transactions.
Avg cost per stay (DRG) — $
Top 5 DRGsSource HL7 — DRG (groupe diagnostic), DG1, PV1 (durée). Average cost per stay grouped by APR-DRG, from diagnosis and length of stay.
Billing rejection rate — 12 months (%)
Continuous improvementSource HL7 — ACK/MSA-1 (AR/AE) sur les DFT. Share of financial transactions rejected by the payer, per month.
Budget vs actual by line (k$)
Current quarter- Actual
- Budget left
Source HL7 — DFT^P03 (réel) vs budget planifié (ERP). Actuals come from FT1 transactions; stacked against budget per expense category.
Payer mix
- RAMQ 68%
- Private / insurer 18%
- Other province 8%
- Self-pay 6%
Source HL7 — IN1-4 (nom du payeur), IN1-2 (régime). Claim distribution by payer: RAMQ, private, CNESST, SAAQ, out-of-province.
Imaging cost by modality ($/study)
Source — HL7 DFT + DICOM Modality (0008,0060). Average cost per study by modality (CT, MRI, XR, US), joining billing with the DICOM header.
Drug cost by class (k$)
Current monthSource HL7 — RXA (administration), RXE-2 (code produit). Cost of administered drugs grouped by therapeutic class.
Margin by service (%)
Source HL7 — DFT (revenus) − coûts affectés. Margin per service = billed revenue minus allocated direct costs, as a percentage.
Revenue leakage (unbilled, k$)
By service — 30 dSource HL7 — ORU^R01/OBR (acte réalisé) sans DFT associé. Revenue leakage: procedures documented by a result but with no matching billing transaction.
Coding completeness (%) vs target
DG1 / proceduresSource HL7 — DG1 (diagnostics), PR1 (actes). Coding completeness: DG1/PR1 fields present vs expected per stay, against target.
Days sales outstanding — 12 months (d)
Downward trendSource HL7 — dates DFT (émission) → paiement. Average days-sales-outstanding: days between billing and payment.
Cost per bed-day — 12 months ($)
Source HL7 — PV1-44/45 (durée de séjour) + coûts. Total cost divided by occupied bed-days, derived from admission/discharge dates.
Lab spend by test family (k$)
Source HL7 — OBR-4 (test demandé), OBX. Lab spend grouped by test family (chemistry, hematology, microbiology, etc.).
Revenue by facility (k$)
Source HL7 — MSH-4 (établissement émetteur) + DFT. Revenue aggregated by source facility, identified by the sending field in the header.
Administrative & operational steering
Management indicators are computed directly from HL7 admit/transfer/discharge (ADT) flows, FHIR resources and DICOM volumes — with no manual entry.
Indicator scorecard
Value, target, trend and HL7/FHIR/DICOM source per indicator| Indicator | Value | Target | Trend |
|---|---|---|---|
| Admissions / day | 142 | — | ▲ 3 % |
| Average length of stay | 5,8 d | ≤ 6 d | ▼ 0,3 |
| Bed occupancy rate | 87 % | 85 % | ▲ 2 % |
| 30-day readmissions | 11,4 % | ≤ 12 % | ▼ 0,6 % |
| Median ER wait | 3 h 12 | ≤ 4 h | ▼ 14 min |
| ALC / alt-level patients | 38 | — | ▲ 4 |
| Cancelled surgeries | 4,1 % | ≤ 5 % | ▼ 0,3 % |
| Discharges before noon | 32 % | ≥ 35 % | ▲ 3 % |
| In-hospital mortality | 1,8 % | — | ▼ 0,1 % |
| Imaging exams / day | 1 284 | — | ▲ 4,1 % |
Patient activity & flow
Admissions vs discharges — 12 months
ADT^A01 / ADT^A03 events- Admissions
- Discharges
Average length of stay by service (d)
Computed from PV1 / Encounter.periodOccupancy & capacity
Occupancy rate by unit (%)
PV1-3 (location) · 85% targetOverall occupancy
All bedsQuality & performance
Key indicators vs target (lower is better)
Readmission %, ER wait h, cancellations %, ALOS dMedian ER wait — 12 months (h)
Triage → providerFrom opaque technical flow to clinical knowledge
FHIR BI turns HL7 into a source of clinical and operational knowledge.
Faster incident resolution
Reduces incident resolution times.
Better data quality
Improves the quality of exchanged data.
Support for clinical teams
Supports clinicians in modeling and analysis.
Real-time analysis
Real-time analysis when connected to the National/Organizational Integration Agent.
Health-status reports
Models patients' health status from HL7 data.
Stronger HL7 maturity
Strengthens the organization's HL7 autonomy and maturity.
See your HL7 messages differently
Create a free account and explore FHIR BI today.