CME credits with their certificates, against the council number your hospital entered.
In plain words: Keep CME credits and certificates against your council’s own figure.
Business · No PHI · hospitalsA clinician’s registration is renewed on continuing-education credits, and the evidence for those credits is usually a folder of certificates somebody hunts for in the last month of a five-year cycle. This keeps the ledger: a cycle per clinician against the requirement, every credit with the certificate reference it rests on, what has been verified by somebody other than the person who claimed it, and how far short the total still is. THE ONE NUMBER THIS APP DOES NOT SUPPLY IS THE COUNCIL’S. How many credits a council asks for, and over how many years, differs by council and changes by notification — so the requirement table ships empty, the field naming where the figure came from is not optional, and a hospital that has entered nothing sees credits counted and nothing measured, which the screen says out loud rather than showing a green tick.
It ships with no credit requirement and no cycle length in it: those are regulatory figures, and a wrong one looks exactly like a right one on a screen. A requirement cannot be stored without naming the circular or notification it came from, and until one is stored nothing is measured. A cycle keeps the total it was opened on, so a council raising its figure does not fail somebody halfway through. A credit carries its evidence — the certificate reference, the certificate itself, or both — and one with neither is refused. The certificate is uploaded from the desk and opened again from the credit; a file that is not one of your own finished uploads is refused. A credit dated outside its cycle, or added to a cycle that is finished, is refused, and a cycle closed short has to say why. Nobody verifies a credit they recorded themselves, and a cycle cannot be marked met until the VERIFIED credits actually reach the total. It does not file the renewal with the council, and it does not decide what counts as a credit — that is the council’s rule and your officer’s judgement.
Every app page carries this section. A listing with only benefits is an advertisement.CMETracker reads staff records, the registrations you already hold and writes the council requirement you entered, cycles, credits and their certificates. Its data class is No PHI. Every app works on the same patient record — nothing is copied into a silo.
It ships with no credit requirement and no cycle length in it: those are regulatory figures, and a wrong one looks exactly like a right one on a screen. A requirement cannot be stored without naming the circular or notification it came from, and until one is stored nothing is measured. A cycle keeps the total it was opened on, so a council raising its figure does not fail somebody halfway through. A credit carries its evidence — the certificate reference, the certificate itself, or both — and one with neither is refused. The certificate is uploaded from the desk and opened again from the credit; a file that is not one of your own finished uploads is refused. A credit dated outside its cycle, or added to a cycle that is finished, is refused, and a cycle closed short has to say why. Nobody verifies a credit they recorded themselves, and a cycle cannot be marked met until the VERIFIED credits actually reach the total. It does not file the renewal with the council, and it does not decide what counts as a credit — that is the council’s rule and your officer’s judgement.
All clinical data stays in the record; operational history stays queryable.
Yes — CMETracker is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.