The app for a clinical or medical conference
The first question a medical conference organiser asks a vendor is about credits, so the answer goes here rather than in a footnote. event67 does not track CME, CE or CPD credits and does not issue certificates.
A planning figure for a specialty society meeting: several parallel tracks, a plenary and a workshop programme.
What a clinical audience needs from a programme
A medical conference app carries the multi-track scientific and clinical programme, opens moderated Q&A in sessions, connects delegates, and collects per-session feedback. event67 does that under the organiser's own brand. It does not do continuing medical education credit tracking, certificate issuing, abstract submission, peer review or ePosters, and for many accredited meetings that combination is disqualifying. Read the gap section before going further.
A parallel programme clinicians can navigate in a break
Six tracks, ninety sessions, and a delegate with eleven minutes between commitments. Filterable by track with starred sessions pinned to the top of a personal agenda. Each session carries its speakers, their bios, the room and a view count that tells the organiser which rooms will be tight.
Questions in a room that will not queue at a microphone
Clinical audiences are senior and self-conscious about asking in front of peers. Upvoted Q&A with moderation gets the question asked and gives the chair a ranked list. The moderation queue lets a chair hold a question they want to answer properly rather than kill it.
Workshops and skills sessions with hard capacity
A simulation session takes twelve. RSVPs are enforced on the server with automatic waitlist promotion, so a hands-on session neither oversells nor runs half empty because the drop-outs were never replaced.
Feedback that arrives per session
Accredited or not, a scientific committee needs to know which sessions worked. Ratings and written suggestions collected inside each session are more useful than one exit survey, and they arrive while the meeting is still running.
A meeting, session by session
Programme finalised
Load tracks, sessions and faculty
Tracks first, then sessions with speakers, rooms and sponsors. Speaker bios appear in the app; the invitation, disclosure and slide-collection workflow happens elsewhere, because there is no speaker portal.
Uses the programme.
Registration closes
Import delegates
Registration and fees run in your registration platform. Export the delegate list, import as CSV, send branded invites and reconcile the bounces before the meeting.
Uses the branded app.
Day one
Badge on a phone
QR check-in with a live arrivals count, and a Wallet pass so a delegate does not hunt for an email. A repeat scan returns already checked in, which matters over a three-day meeting.
Uses check-in and Wallet passes.
In session
Moderated Q&A and audience polling
Questions upvoted by the room, sequenced by a moderator working from the console. Polls give a reading of clinical practice in the room, which for a guidelines session is genuinely valuable content rather than decoration.
Uses Q&A and polls.
After
The scientific committee's evidence
Ratings per session, attendance by track, and the archive of every question asked. That is the material for next year's programme, and it is more specific than the usual recollection of which room felt full.
Uses session feedback and analytics.
Setting up a clinical meeting
Five steps, beginning with the accreditation question because it determines whether the rest is worth doing.
Settle the credit question first
If your meeting awards credits, decide which system is the record for them. event67 cannot be. Some organisers run credits on paper or in a separate platform and use event67 for everything else.
Create the event and brand it
The society's own identity across every screen, published under its name in both stores.
Build tracks, then sessions and faculty
Speakers appear with bios, rooms and their sessions. Collect the slides and disclosures elsewhere.
Set true capacities on skills sessions
Server-enforced RSVPs with automatic waitlist promotion, sized to the simulation room rather than to demand.
Brief a moderator per track
Per-event moderator roles, so a track chair moderates their own Q&A. Team chat and billing carry audit trails.
What a 640-delegate meeting costs
Six hundred and forty delegates activate. Fifty are free and the rest are billable once for the whole meeting, however many days and sessions it runs.
- activated attendees
- 640activated attendees
- billable, after the first 50 are free
- 590billable, after the first 50 are free
- for the whole event, at $5.00 each
- $2,950for the whole event, at $5.00 each
Delegates who register and never open the app are not billed. The meter counts activation, not registration.
The gaps that usually decide a medical meeting
These are not minor. For an accredited meeting they are frequently disqualifying, and it is better to find that out on this page.
- No CME, CE or CPD credit tracking. No attendance-duration verification, no credit rules and no certificate generation of any kind.
- No abstract submission, peer review or scoring. No call for papers.
- No ePosters, poster halls or digital poster viewing.
- No speaker portal, disclosure collection or presentation file management.
- No offline-first operation. The app needs a network, and conference-centre basements are famous for not having one.
- No exhibitor lead retrieval for industry partners, and no badge printing.
- No ticketing or registration payments.
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 of any kind: no attendance-duration verification, no credit rules and no certificates. If your meeting is accredited, you need a separate system of record for credits, and you should treat that as a fixed requirement rather than something we might add.
Can we manage abstracts and posters?
No. There is no abstract submission, no peer review, no scoring and no ePoster capability. Sessions can reference posters as content, but the submission and review workflow happens in another platform.
Does it work offline?
No. The app requires a network connection to load the schedule, questions and announcements. Conference centres with poor coverage in breakout areas are a known problem for this product, and offline-first competitors exist. Test the venue before committing.
How do industry partners appear?
As tier-ordered sponsor pages with logos, descriptions and websites, and attached to specific sessions where your compliance rules allow it. There is no lead retrieval and no badge scanning, so industry partners expecting a scanner will need one from elsewhere.
Is patient or clinical data ever involved?
It should not be. event67 holds attendee profile information, session content, questions and photographs for an event. It is not built for protected health information and must not be used to carry it. Treat it as a conference app, not a clinical system.
Keep reading
Other kinds of event
The features this leans on
The programme, the questions and the feedback
Everything a clinical meeting needs except credits, which we do not do and will not pretend to.