The conference app for healthcare organisations
Two answers decide whether a healthcare organisation should read further. event67 does not track continuing medical education credits, and it must never carry patient data. Both are absolute.
A planning figure for a specialty society meeting or a large hospital system's education day.
The meetings a health organisation runs
A healthcare event app carries the meetings a hospital system, medical society or health service runs: clinical conferences, grand rounds, staff town halls, training days and society annual meetings. event67 provides the programme, moderated Q&A, capacity-controlled workshops, feedback and analytics under the organisation's own brand. It does not track CME, CE or CPD credits, does not manage abstracts or ePosters, and is not built to hold protected health information.
The clinical conference or society meeting
Several parallel tracks, a plenary, a workshop programme and a delegate body that will not queue at a microphone. Sessions filter by track with speakers, bios and rooms. Upvoted Q&A gets the question asked without a clinician having to be the person who asked it, and a track chair moderates from the console rather than from the stage. Skills sessions carry hard capacity, enforced on the server with automatic waitlist promotion.
Grand rounds and departmental education
A recurring weekly or monthly session behaves differently from an annual meeting. Each is its own event with its own free fifty activated attendees, so most departmental education costs nothing. Q&A opened in advance gives the presenter the questions before they stand up, which improves the session more than any other single change.
Staff town halls across a hospital system
A health system's internal communications problem is a shift-work problem: the people you most need to reach are not at a desk. Push announcements deep-link to the post, questions collected in advance are ranked by upvote, and each town hall is a separate event so quarter-on-quarter participation is comparable.
Training days and mandatory education
Sessions with true room capacity, waitlists that promote automatically, and per-session feedback collected while the session is still in the room. The boundary is firm: attendance in event67 is an operational record, not a compliance record, and it does not issue certificates or track credits.
Industry partners at a society meeting
Sponsors appear as tier-ordered pages with logos, descriptions and websites, and can be attached to sessions where your compliance rules permit it. There is no lead retrieval and no badge scanning, so an industry partner expecting a scanner needs one from another vendor. For meetings with strict industry-separation rules, the absence of scanning is occasionally an advantage.
What changes for a scientific committee
The society or system owns the app
Published to the App Store and Google Play under the organisation's own name, with its identity across every screen. For a medical society whose members are its brand, that matters.
Questions arrive ranked, not shouted
Upvoting changes who asks in a senior clinical room. Chairs get a list ordered by what the room wants answered, though moderation decisions are not logged.
Feedback per session, not one exit survey
Ratings and written suggestions collected inside each session give a scientific committee specific, actionable material rather than an aggregate satisfaction score.
A ceiling on the cost of a large meeting
The per-event price stops rising at a thousand activated delegates, so a meeting that exceeds its projection does not exceed this budget line.
Departmental education stops being invisible
Grand rounds and departmental teaching are usually the least measured education a health organisation runs, because nobody has a record of who attended or what they thought. Running each session as its own event, most of them inside the free tier, produces attendance and per-session ratings as a by-product. That is not a credit record and must not be presented as one, but it is the first evidence many education leads have had.
The healthcare-specific gaps, and one hard boundary
Read all of these. The last one is not a feature gap, it is a rule about how the product may be used.
- No CME, CE or CPD credit tracking. No attendance-duration verification, no credit rules and no certificate generation. For an accredited meeting this is usually decisive.
- No abstract submission, peer review, scoring or ePosters. No call for papers and no speaker portal.
- No offline operation. The app needs a network, and hospital basements and conference-centre breakout floors are famously bad for it. Test the venue.
- No exhibitor lead retrieval, badge scanning or badge printing for industry partners.
- No integration with clinical, HR or credentialing systems. The attendee list is a CSV import.
- No electronic health record integration of any kind.
- event67 must never be used to carry protected health information. It holds attendee profiles, session content, questions and photographs for an event. It is a conference app, not a clinical system, and no part of this product is designed, described or offered for patient data.
What a 700-clinician meeting costs
Seven hundred delegates activate. Fifty are free and the rest are billable once for the whole meeting, however many days and parallel sessions it runs.
- activated attendees
- 700activated attendees
- billable, after the first 50 are free
- 650billable, after the first 50 are free
- for the whole event, at $5.00 each
- $3,250for the whole event, at $5.00 each
Recurring departmental education runs as separate events, each with its own free fifty, so most grand rounds cost nothing.
What we will and will not claim
Healthcare procurement is used to vendors overstating this section. Here is the plain version.
| Control | What exists |
|---|---|
| Patient data | Not supported and not permitted. No PHI, in any field, at any time. |
| Certifications | We do not assert compliance certifications on this page. Ask us directly and we will describe exactly what exists. |
| Roles | Four levels: super admin, organization admin, moderator and attendee. A track chair can be scoped to one event. |
| Audit | Team chat and billing carry audit trails. Moderation actions are not logged. |
| Credits | Not tracked, not verified, not certified. There is no partial version of this feature. |
| Accessibility | WCAG AA contrast checking in the theme editor that warns and confirms before a save. No VPAT. |
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Does event67 track CME credits?
No. There is no credit tracking, no attendance-duration verification and no certificate issuing. If your meeting is accredited, credits must be recorded in a separate system. This is the most common reason a medical society does not choose event67, and it is not something we are working towards.
Is event67 suitable for patient data?
No, and this is a rule rather than a limitation to work around. event67 holds attendee profiles, session content, questions and photographs for an event. Protected health information must never be entered into it. Treat it as a conference app in the same category as a printed programme, not as a clinical system.
Can we run abstracts and posters?
No. There is no submission, peer review, scoring or ePoster capability. Sessions can reference posters as content, but the whole submission and review workflow happens in another platform.
Does it work without a network connection?
No. The app fetches the schedule, questions and announcements over the network. Venues with poor coverage in breakout areas are a real problem for this product, and offline-first competitors exist. Test the venue before committing to it.
How do industry partners appear?
As tier-ordered sponsor pages with logos, descriptions and websites, and attached to sessions where your rules allow it. There is no badge scanning and no lead retrieval, which for meetings with strict industry-separation rules is sometimes exactly what you want.
Can we use it for internal staff communications?
For town halls and education days, yes, as separate events with their own agendas, Q&A and announcements. It is not an internal communications platform and does not replace one; it covers the gatherings rather than the everyday channel.
Can we run it across several hospitals in one system?
Yes. The console is multi-tenant with organization admins and per-event moderators, so each site runs its own education calendar under one organisation. Team chat and billing carry audit trails, and each site's events carry their own free fifty activated attendees, which for departmental teaching usually means no cost at all.
Do you sign a business associate agreement?
That is a question to ask us directly rather than one to answer on a marketing page. What we will say plainly here is that event67 is not designed to hold protected health information and must not be used for it, so if your use case would require a BAA because PHI would be involved, the honest answer is that this is the wrong product for that use.
Keep reading
The events you run
The features that carry them
Adjacent industries
Talk to us about your clinical meeting
The credit answer is no. If your meeting can live with that, everything else in the programme is straightforward.