Congress Mission

Blueprint

Every tool in the lab is documented the same way, from the operational problem to the MLR questions a reviewer will ask.

1. 1

   Operational problem

   At a major congress a Medical Affairs team splits across dozens of parallel sessions, posters, symposia and the booth. Coverage is planned in a spreadsheet, insights travel through personal chat apps, competitor news reaches the team hours late, and the debrief is reconstructed at night from scattered notes.

   Company tools are often unavailable on the floor, and consumer chat apps mix business insights with personal accounts.

2. 2

   Hypothesis

   If the team shares one live plan, captures insights in a structured way tied to each session, and gets an alert the moment something important lands, nothing priority is missed and the debrief is ready at the end of the day instead of the end of the week.

   If it runs phone to phone with no server or accounts, it can be used on day one, without IT onboarding, and with nothing stored outside the team's devices.

3. 3

   Solution architecture

   • Store (store.js): records as fields with hybrid logical clocks; last-writer-wins merge per field, so copies converge in any order. Per-record digests for catch-up.
   • Mesh (mesh.js): WebRTC data channels. Pairing by QR code carrying a compact session description (about 200 characters). Further links form automatically with offers relayed through linked phones; changes are gossiped to everyone.
   • Interface: mission control with countdowns, coverage and a live link map; plan with clash and gap checks and .ics/CSV import; insight capture with Flash alerts; team chat and pings; daily debrief exported as text, Markdown, CSV or PDF.
   • Tests: convergence of four devices under random concurrent edits; pairing codes for Chrome, Firefox and Safari formats; three browsers pairing by camera end to end.
   • Installable PWA, fully offline; a fictional demo crew for trying it alone.
4. 4

   HCP and patient impact

   HCPs: better-prepared follow-up after the congress: questions raised at the booth reach Medical Information the same day, and field teams share one accurate picture of new data.

   Patients: indirect. Faster internal understanding of new evidence supports more accurate scientific exchange.

   No patient data belongs in the app, and the capture form says so.

5. 5

   Regulatory and MLR considerations

   • No server: mission data stays on the team's devices; nothing is processed by mafflab.xyz or any third party (unless the optional STUN setting is turned on, which shares IP addresses with that server).
   • Insights are field observations, not verified data, and the app is not a CRM: HCP interactions still go into the company's systems according to local SOPs.
   • The capture form reminds users not to enter patient data or names of HCPs unless they spoke publicly.
   • Companies should confirm that peer-to-peer apps on company phones comply with their IT and data protection policies before use.