WF-21 — CE/CME Programme Lifecycle and Certificate Issuance

This is the clearest example in the pilot of real, substantial activity that scores nothing unless it is deliberately routed. IoL's CE/CME portfolio may be its largest single body of teaching by participant numbers. It has no Program Code, so it cannot appear as a programme row, and no OBEF KPI takes CPD delivery as an input in its own right. Four routes exist by which it can reach the framework anyway, all of them at institution level, and all four depend on attributes stamped on the activity at capture: whether it qualifies as an approved short qualification, whether it was delivered for an industry client, whether it was registered as an event, and whether the event was open to students or aimed at the community. Get those attributes right at design time and a large body of work becomes visible. Get them wrong or leave them blank and the same work is invisible, permanently, because none of them can be added afterwards to an activity that has already run.

1. Purpose

To ensure that every continuing education and continuing medical education activity IoL delivers meets a demonstrated professional need, is developed and delivered free of undeclared commercial influence, is attended by people whose attendance is verified, produces a certificate the participant can rely on with their regulator and employer, and is recorded in a form that allows the institution to claim it under the institution-level indicators it genuinely qualifies for.

2. Scope

Scope statement. This process manages non-credit continuing education and continuing medical education from the identification of a professional practice gap, through channel routing, accreditation or credit approval, faculty and content development, conflict-of-interest management, delivery, attendance verification, participant evaluation and certificate issuance, to the recording of the activity against the institution-level indicators it qualifies for.

Applies to. All non-credit CPD, CE and CME activity delivered by IoL: courses, workshops, symposia, short programmes and online modules, whether open-enrolment, delivered for a Dubai Health entity, delivered for an external industry client, or offered free to the public. Both fee-bearing and free activity. Participants who are practising health professionals, and public participants where the activity is community-facing.

Does not apply to. Credit-bearing teaching within PGDipHPE and MScHPE, which is Channel C1 and covered by WF-03, WF-09 and WF-10. The design and Ministry approval of a micro-credential, which is WF-22; this workflow hands over to it and does not duplicate it. Academic and community events that are not CE/CME activity, which are WF-23; where a CE/CME activity is also registered as an event, WF-23 owns the event record and this workflow supplies its attributes. Partnership agreements and their contribution valuation, which are WF-24.

Applicable requirements. OBEF guide v11.5 KPI 2.5, KPI 3.4, KPI 6.1 and KPI 6.2; CHEDS Institute - Events.xlsx, Institute - Financials.xlsx, Institute Partnerships.xlsx; HEDB MicroStudents and Micro-Graduates datasets and the MICROCREDENTIALS lookup; the accreditation requirements of whichever body IoL accredits or seeks accreditation through [IoL to confirm; the departmental notes refer to ACCME-oriented and IACET-oriented practice, and the two impose different requirements]; Dubai Health Authority CME/CPD requirements applicable to the professions being served [IoL to confirm]; MBRU financial and contracting policy.

The channel constraint, stated once and relied on throughout. Non-credit CPD/CME is not a CAA-accredited programme. It has no Program Code. It therefore cannot be scored at programme level at all, and it does not appear in any of the 22 programme-level KPIs for PGDipHPE or MScHPE. Everything below is about institution-level indicators. Any expectation that a strong CPD portfolio will lift a programme score is mistaken and should be corrected wherever it appears.

3. Trigger, boundary and endpoint

4. SIPOC

5. Accountability

Process owner. IoL CE/CME Lead, or the role able to commit faculty, approve content, sign off accreditation submissions and decide whether an activity is designed as a short qualification.

Escalation.

6. Process steps

1. Assess the practice gap and define the need. Identify the professional practice gap, the target profession and level, the learning outcomes, and the evidence that the gap exists (audit data, regulator requirement, employer request, participant demand, published guidance). This is accreditation requirement and good practice before it is anything to do with OBEF. [CAPTURE] needs evidence, target audience, learning outcomes. Serves the accreditation file and the KPI 6.1 and 6.2 audience classification.

2. Take the channel routing decision, at design time, and record it. Before anything is built, decide and record which of the four routes this activity is intended to reach, if any. [CAPTURE] the routing decision, its date and its rationale. Serves 2.5, 3.4, 6.1 and 6.2.

   Route	Reaches	The attribute that must be true, and be true by design
   A. Short qualification	KPI 2.5 (5.0%)	The activity meets the definition of an approved short qualification or professional certificate: on the pre-approved MoHESR list and meeting its criteria, or a micro-credential approved by the Ministry after development by a MoHESR-licensed HEI. Handed to WF-22
   B. Industry client delivery	KPI 3.4 (3.0%)	The course or training programme was developed and delivered for an industry client, and the revenue is recorded as direct revenue from clients or as an other-industry contribution covering CPD programmes
   C. Academic event	KPI 6.1 (3.0%)	The activity is organised, co-hosted or hosted by MBRU, is open to student attendance, is on an academic topic, and meets the attendance and duration minimum for its type
   D. Community event	KPI 6.2 (2.0%)	The activity targets the local or wider community and delivers social benefit. A free course needs only five participants and one hour

   This is the single most consequential step in the workflow. Every one of the four attributes is decided by how the activity is designed, marketed and registered, and every one of them is impossible to establish retrospectively. An activity closed to students cannot be made open to them after it has run. A fee-bearing course cannot be made free. A certificate that is not an approved short qualification does not become one because it was useful. Decision point. Routes C and D are mutually exclusive for any one activity: an event is counted under either KPI 6.1 or KPI 6.2, never both. Decide which at this step, not at extract.

3. Obtain accreditation or credit approval. Submit the activity to the accrediting body on whose terms IoL operates, in the form and timescale that body requires, and record the credit or CE hours awarded, the accreditation reference and its validity period. [CAPTURE] accrediting body, activity reference, credit or CE hours, validity dates. Serves participant value and the evidence file; not itself an OBEF input. State the dependency honestly. IoL's CE/CME practice is described in the departmental notes as oriented to ACCME-style and IACET-style requirements. Which accreditation IoL actually holds, seeks or operates under is [IoL to confirm], and it matters here for two reasons: the two frameworks impose materially different requirements on needs assessment, conflict-of-interest management and outcome measurement, and neither is the same as the MoHESR approved-short-qualification test in route A. Accreditation by ACCME or IACET does not make an activity an approved short qualification for KPI 2.5. Route A depends on the MoHESR list or Ministry approval, and on nothing else.

4. Select faculty and develop content. Faculty selected on expertise and educational capability, content mapped to the stated learning outcomes, materials versioned, and the assessment or participation requirement defined. [CAPTURE] faculty identity and affiliation, content version, learning outcomes, the requirement a participant must meet to be certificated. Serves the evidence file and, where the faculty member is external, the KPI 3.3 and 3.4 partner records held by WF-03 and WF-24.

5. Collect and mitigate conflict-of-interest declarations, before content is finalised. Every person in a position to control content (faculty, planners, reviewers) declares relevant financial relationships. Declared conflicts are resolved before delivery by content review, peer review, removal of the conflicted material or replacement of the individual, and the mitigation is recorded. Disclosures are made to participants at the start of the activity. [CAPTURE] declaration per contributor, date, conflicts identified, mitigation applied, participant disclosure made. Serves the accreditation file. This step has no OBEF weight and belongs in the workflow anyway. It is the substance of what makes a CME certificate mean anything, and an activity that fails here fails regardless of what it scores.

6. Contract with the client, where the activity is delivered for one. Where a Dubai Health entity, an employer or an external organisation commissions the activity, the contract must name the client, its sector and type, the deliverable, and the financial terms, and it must be in place before delivery. [CAPTURE] client identity normalised to the controlled organisation list, partner type, contract value, dates. Serves 3.4, and feeds WF-24. Decision point. The client's type decides whether the revenue can be claimed under KPI 3.4 and under which of the eight accepted contribution types. Federal ministries and public bodies are classified as government agencies rather than non-profit organisations, which changes the treatment. Classify at contract, not at extract.

7. Deliver the activity. Record the actual delivery: dates, duration in hours, mode, venue, and the faculty who actually delivered as against those who were scheduled. [CAPTURE] delivery dates, actual duration, mode, delivering faculty. Serves 6.1 and 6.2 duration minima, which are one hour in every category.

8. Verify attendance by name. Attendance is captured at the time, per session, per participant, by a method that produces a name list rather than a headcount: registration scan, sign-in, platform log. Partial attendance is recorded as partial. [CAPTURE] participant names and identifiers, sessions attended, total attendance count. Serves 6.1 and 6.2 numerator eligibility and the certificate. "About sixty people" is not evidence. Appendix B permits the Ministry to demand attendee names for both event KPIs. An activity whose attendance is estimated cannot be counted and cannot be defended, and the estimate cannot be upgraded to a name list later. Decision point. Test the count against the minimum for the type at this step: conference 150, seminar 50, workshop 15, other academic 50 for KPI 6.1; educational programme 20, volunteering 5, free course 5, cultural 50, public lecture 50 for KPI 6.2. If the activity falls short, record it and do not count it. Rounding up is the failure that this decision point exists to prevent.

9. Collect participant evaluation. Issue the evaluation instrument at or immediately after delivery, retain the raw per-question responses with the issue and collection dates, and feed the results back into the next needs assessment. [CAPTURE] raw responses, issue and collection dates, respondent count. Serves the accreditation file and the Appendix B event-feedback evidence for 6.1 and 6.2.

10. Issue certificates. A certificate is issued only where the participant met the stated requirement and the attendance record supports it. Each certificate carries a unique verifiable identifier, the activity title and reference, the credit or CE hours, the date and the issuing authority, and is recorded in a register that allows verification on request. [CAPTURE] certificate identifier, participant, activity, hours, issue date. Serves participant and employer needs; and, where route A applies, feeds the KPI 2.5 attainment evidence through WF-22. Exception route. A participant who attended but did not meet the requirement receives an attendance record, not an attainment certificate. The distinction matters directly at KPI 2.5, where an attempt does not count and only obtaining the certificate does.

11. Register the activity where it qualifies, in the correct place, once. Create the Institute - Events.xlsx row through WF-23 where route C or D applies, with Open_to_students, Number of Attendees, Event duration, Targeted Audience and Ticket Price populated from steps 7 and 8. Record the revenue against the correct Institute - Financials.xlsx line through WF-24 where route B applies. Hand the activity to WF-22 where route A applies. [CAPTURE] the register entries made, and the routes deliberately not taken. Serves 6.1, 6.2, 3.4 and 2.5.

12. Reconcile and release to WF-26. Confirm that every delivered activity has a routing decision, that every claimed event meets its minimum, that no activity is counted under both 6.1 and 6.2, that revenue appears once across Financials, Partnerships and Research Projects, and that the certificate register agrees with the attendance record. [CAPTURE] reconciliation date, exceptions, resolution. Serves 2.5, 3.4, 6.1, 6.2 and assertions C5 and C9.

7. OBEF data generated

Read this table with the channel constraint in front of you. Every row is institution level. There is no programme-level row and there will not be one, because the activity has no Program Code. CE/CME activity reaches OBEF only through institution-level KPIs, and only if it is stamped with the right attributes at capture. Nothing in this table can be produced from an activity that has already run without them.

Capture rule. Five things must be true or recorded at the time and can never be added afterwards. The routing decision, because it determines how the activity is designed and marketed. Whether the activity was open to students, which is a fact about the invitation, not about the record. The verified attendance name list, because a headcount cannot be turned into names. The ticket price, because a free course is free at the point of offer. Whether the certificate was awarded on attainment or on attendance, because KPI 2.5 counts only attainment.

Reproducibility test. A second analyst can reproduce the KPI 6.1 and 6.2 contributions from Institute - Events.xlsx filtered on type, Open_to_students, duration and the attendance minima, and the KPI 3.4 contribution from Institute - Financials.xlsx reconciled to Institute Partnerships.xlsx. The KPI 2.5 contribution is not reproducible from this workflow at all, and correctly so: it is reproduced in WF-22 from the HEDB micro-credential datasets, and this workflow's only job is to make the handover and record it. The test fails today at the attendance name list and at the routing decision, on the assumption that neither is currently held for CE/CME activity [IoL to confirm].

8. Max-score design

How to read the yield line in the header. WF-21 is listed against 10.0% at institution level, and the four KPIs it contributes to carry 13.0% between them. The difference is deliberate: CE/CME is one contributor among several to each of those four KPIs, and this workflow should never be presented as owning them. WF-22 owns 2.5, WF-24 owns 3.4, WF-23 owns 6.1 and 6.2. What WF-21 owns is the supply of qualifying activity and the attributes that make it claimable.

What this workflow must do to reach the target.

1. Take a routing decision on every activity at design time, and record it, including the decision that an activity reaches no route at all. A recorded "no route" is a useful fact. An absent decision is a silent loss.
2. Design activities to be open to students wherever the topic allows. A CE/CME session on an academic topic that admits PGDipHPE and MScHPE learners alongside practising professionals is a KPI 6.1 event. The same session closed to learners is not. The cost of the difference is usually a line in the invitation.
3. Verify attendance by name at every activity, without exception, because it is the precondition for both event KPIs and the only evidence Appendix B will accept.
4. Record the client type at contract for every commissioned activity, so the revenue can be classified correctly under KPI 3.4 without a reconstruction exercise at year end.
5. Offer at least some free, public-facing activity, because the KPI 6.2 free-course bar is five participants and one hour, and IoL plausibly delivers activity of this kind already without registering it.
6. Assess every CPD course against the WF-22 short-qualification criteria and record the answer, so that the ones capable of qualifying are identified while they can still be designed for it.
7. Never count an activity under both 6.1 and 6.2, and settle the classification at step 2.

[REDESIGN] actions.

Sequencing note. R1 and R3 come first and are close to free: a form field and a registration setting. R2 is the one with the largest arithmetic behind it, because KPI 6.1's institutional anchor of 25 events is reachable for MBRU largely on the back of activity that already happens. R6 is the one that leads to the biggest single KPI, and it is also the one most likely to return the answer that most of the catalogue does not qualify, which section 9 addresses directly.

9. Indirect strategy where data cannot be collected

Category 4 predominates, overwhelmingly. Category 3 applies to one route and must be stated honestly rather than worked around.

Category 4, the activity exists but is invisible. This is the defining case of the whole pilot and CE/CME is its clearest instance. IoL delivers continuing education to practising health professionals. The teaching happens, the participants attend, the certificates are issued, and none of it reaches OBEF, because the framework has no CPD indicator and the four indicators it could reach all require an attribute that nobody has been asked to record. Nothing about the activity needs to change for three of the four routes. An academic CE session becomes a KPI 6.1 event by being open to students and having its attendance counted by name. A public health talk becomes a KPI 6.2 event by being registered with its audience and its zero ticket price. A commissioned course becomes a KPI 3.4 contribution by having its client type recorded on the contract. The response is capture and a design default, not a tactic, and it is R1, R2, R3 and R5.

Category 3, the activity genuinely does not exist, applies to route A, and this is where the honest answer has to be given. KPI 2.5's micro-credential component counts only short courses that are on a pre-approved MoHESR list and meet its criteria, or micro-credentials approved by the Ministry after being developed by a MoHESR-licensed HEI. Internally invented certificates do not count, however rigorous, however well accredited by ACCME or IACET, and however valuable to the participant.

So where a CPD course cannot be made to qualify as an approved short qualification, the honest answer is that it does not count, and the effort should go to the routes that do. That sentence is the operating instruction for this section. It has three practical consequences:

1. Do not submit internally issued CPD certificates as micro-credential attainments. They will not survive the HEDB MICROCREDENTIALS lookup, and attempting it damages the credibility of a submission whose whole value is that it can be trusted.
2. Do not redesign good CPD into a shape it does not fit merely to chase route A. If a two-hour update session for practising clinicians cannot be a short qualification, it should remain a two-hour update session, and it should be routed to C or D instead, where it counts for something and costs nothing.
3. Where redesign is genuinely feasible, take it to WF-22 as a design decision, with the Ministry approval route understood and its lead time accepted. That is legitimate and is exactly what the charter means by designing activity so that it qualifies.

There is no weight redistribution available anywhere in this workflow. Redistribution exists in four programme-level cases only, and CE/CME has no programme level. An activity that reaches no route simply contributes nothing. That is worth stating plainly because it removes any incentive to misclassify: there is no mechanism by which classifying an activity as absent produces a benefit.

Category 1 and Category 2 do not apply. All four target KPIs are Track A and MBRU submits them itself. None of them is a survey, so there is no small-population problem and no Appendix C question.

Category 5, performance genuinely low, is not the situation here and should not be reported as though it were. If IoL's CE/CME contribution to the framework is currently zero, the cause is that nobody was asked to record four attributes, not that the activity is weak. Diagnosing a capture problem as a performance problem produces a corrective action plan aimed at the wrong thing, and this workflow's first year of data should be read with that in mind.

Boundary check. This workflow must never:

• record a CE/CME activity as a programme-level KPI contribution, since it has no Program Code and no programme row;
• count an internally issued CPD certificate as a micro-credential or short qualification for KPI 2.5, where it is neither on the MoHESR pre-approved list nor Ministry-approved;
• treat ACCME or IACET accreditation as satisfying the MoHESR short-qualification test, since they are unrelated instruments;
• issue an attainment certificate to a participant who attended but did not meet the stated requirement, or count such a certificate as an attainment;
• estimate, round up or reconstruct an attendance figure, or count an event whose attendance falls below the type minimum;
• count an event under both KPI 6.1 and KPI 6.2;
• mark an activity Open_to_students where students were not in fact invited or admitted;
• record a faculty-only activity as a KPI 6.1 event, which the guide excludes explicitly;
• record a fee-bearing course as a free course, or set Ticket Price to zero where a fee was charged;
• claim CPD revenue under KPI 3.4 where the client is not an industry or economic-sector client of an accepted type, or claim the same revenue in Financials, Partnerships and Research Projects;
• add a routing attribute to an activity after it has been delivered.

10. Service standards

11. Records and evidence

Appendix B readiness. For the event routes, the Ministry can demand media material, attendance proof including names, venue or licensing approvals and feedback documentation, without notice. Today, IoL could most likely produce promotional material and certificate records within 15 working days. It could not produce attendance name lists or raw evaluation data with dates for most historical activity [IoL to confirm], which means historical CE/CME activity is largely unclaimable even where it qualified on every other test. That is an argument for starting now rather than for reconstructing backwards, and it should be said in those terms rather than treated as a data-cleaning project.

12. Risks and controls

13. Performance measures

The first five measures are the whole workflow. IoL can deliver an outstanding CE/CME portfolio and contribute nothing to OBEF, and the difference is entirely in those five rows. None of them is about educational quality and none of them should be confused with it.

14. Change control