Morbidity Register Summary
Deduplicate a morbidity register and tally unique patients by reported condition code.
Description
A morbidity register may contain repeated patient-condition entries.
A morbidity register may contain repeated patient-condition entries. Deduplicating within each condition yields unique patient counts without treating repeated entries as new people.
The tool returns uniquePatients (unique patients); conditionLabels (condition labels); patientCounts (patient counts). Input measurements and model parameters are supplied by the caller; the tool computes the stated summary rather than acquiring those measurements.
When to use Morbidity Register Summary
Use Morbidity Register Summary when you already have caseIds, conditionCodes and want uniquePatients, conditionLabels, patientCounts. This is useful for checking a supplied calculation, documenting a measurement convention, or comparing observations prepared on the same basis.
How to use Morbidity Register Summary and understand its results
- Enter caseIds, conditionCodes using the field table below. Match the units, ordering and data boundaries described in the calculation.
- Run the tool after checking the stated bounds and matching paired observations or categories. A malformed request gives a tool error rather than a usable measurement.
- Read uniquePatients, conditionLabels, patientCounts. Use the calculation and interpretation below to distinguish amounts, ratios, signs and decision flags where applicable.
- Review the supplied parameters and assumptions before using the result in a report or comparing it with another observation.
| Input field | Meaning | Value type and bounds | Requirement |
|---|---|---|---|
| caseIds | Case ids | list of string | Required |
| conditionCodes | Condition codes | list of string | Required |
Group aligned nonempty patient IDs and condition codes into sets, sort the condition labels, and count unique patients globally and within each group.
count[condition] = number of distinct patient IDs recorded for that condition The symbols refer to the supplied quantities or generated values described above; unit conversions and comparison boundaries follow the stated implementation.
{
"input": {
"caseIds": [
"A",
"A",
"B"
],
"conditionCodes": [
"hydrocele",
"lymphedema",
"hydrocele"
]
},
"output": {
"uniquePatients": 2,
"conditionLabels": [
"hydrocele",
"lymphedema"
],
"patientCounts": [
2,
1
]
}
}Limitations and assumptions
Exact identifiers determine deduplication. One patient can occur in multiple conditions, so condition counts need not sum to the global total.
Numerical inputs must be finite. The tool checks its declared input shape and calculation constraints; those checks do not verify the quality, calibration or representativeness of the supplied observations.
Alternative or Complementary methods
Coinfection Species Count: Deduplicate reported parasite species and flag multiple-species detections. Control Component Compliance: Audit reported completion of caller-defined integrated parasite-control components.
Methodological background: Monitoring drug coverage for preventive chemotherapy.1
References
-
Monitoring drug coverage for preventive chemotherapy — World Health Organization
Similar or alternative tools
- Coinfection Species Count
Deduplicate reported parasite species and flag multiple-species detections.
- Control Component Compliance
Audit reported completion of caller-defined integrated parasite-control components.