A metric dictionary records what each measure counts, its source, time basis, exclusions, and responsible owner. It helps a practice identify when two reports use the same name for different populations. Define the measure before comparing performance or asking a vendor to explain a difference.
Give each measure a complete definition
Record the name, business question, numerator and denominator when relevant, source system, and reporting period. State whether the date refers to inquiry creation, appointment scheduling, attendance, or another event.
For example, “evaluations booked” could mean bookings created during a month or patients from a particular inquiry group who eventually booked. Both can be useful, but they should not share an unexplained label.
Document exclusions and changes
Explain how unknown sources, cancelled appointments, repeated submissions, and corrected records are treated. Identify who can confirm the definition and how changes will be communicated.
When a definition changes, preserve enough context to interpret older reports. A movement in a chart may reflect a rule change rather than a change in patient behavior. Do not rewrite the historical meaning silently.
Bring definitions into the product conversation
Ovrflo’s separate acquisition and patient workflow views provide a demo context for discussing source and milestone definitions. Use representative records to test whether the words on a report match the journey being described.
The public demo contains fictional figures, not a validated practice dataset or a configurable metric-dictionary module. Use this guide as a working approach for documenting requirements alongside your reporting evaluation.
Your working checklist
- State what each measure counts and why.
- Record its source, date basis, and exclusions.
- Assign an owner for definition questions.
- Explain changes before comparing reporting periods.
See the workflow in Ovrflo.
Explore the related workspace with fictional data, then discuss what your team would need in practice.