Appearance
Conferences & Certificate Programs
Two ACPE structures worth setting up deliberately: a conference where attendees pick their own sessions, and a certificate program that reports a CPN alongside its UAN credit.
Multi-session conferences need a UAN per session
ACPE awards each UAN as a whole, so a learner earns the full credit hours attached to a UAN. For a conference where attendees pick and choose sessions, that makes a separate UAN per session the setup you want — and typically one per audience as well, so pharmacists and technicians each get their own. Requesting UANs this way is standard ACPE practice for multi-session conferences, and accreditors are used to the ask if yours initially issues a single bundled number.
With individual UANs in hand, the build is straightforward: one course for the conference, with a credit per session, each carrying its own UAN, times, and target audience. Every learner claims exactly the sessions they attended, and reporting happens automatically per session.
Working with a single bundled UAN
Build the conference the same way — all sessions and credits in LecturePanda — and your attendance reports still show precisely who attended what. Use that report as the basis for your CPE Monitor upload, and you keep the per-session detail while your accreditor catches up.
Certificate (CPN) credit alongside UAN credit
ACPE certificate programs issue a CPN (Certificate Program Number) in addition to the regular UAN credit. Both can be submitted automatically when the learner claims their normal credit.
- Create a second credit for the certificate, the same way you'd create a UAN credit.
- Set its activity type to Certificate. The form then asks for the CPN — enter it there.
- Scroll to the bottom of that credit's configuration and set its dependency to Auto-Claim, then select the UAN credit that is its component part.
Now when a learner claims their normal credit, both line items are submitted together — no second action needed from them.