Encounter Attributes

[ssmusoke (Stephen Senkomago Musoke)]

@mksd

@tendomart could you describe what the business needs are for program attributes on a couple of examples?

In UgandaEMR are using program attributes to manage the identification information for enrollment into a specific program. Since a patient can be enrolled multiple times into the same program say TB treatment, its possible to store the facility and district TB numbers as attributes for that program instance

[mksd (Dimitri R)]

Out of curiosity, will you display those attributes through the UX, or they are just being kept track for other reasons.

Anyway @tendomart, yes, Program could be made attributable, as of Core 2.4.x.

[ssmusoke (Stephen Senkomago Musoke)]

@mksd

Out of curiosity, will you display those attributes through the UX, or they are just being kept track for other reasons.

Yes we intend to show them on the UI and in reports plus exchange them with a central server for aggregation across facilities

[tendomart (tendo kiiza Martyn)]

@burke

Theoretically, since Program defines the program and PatientProgram defines a patient’s enrollment into that program…

• Program Attributes would be used to add implementation-specific metadata about a program
• Program Tags would be used to categorize/label programs
• PatientProgram Attributes would be used to add implementation-specific metadata about a patient’s enrollment into a program
• PatientProgram Tags would be used to categorize/label enrollments

Thanks @burke for making it this plain.

@mksd

Out of curiosity, will you display those attributes through the UX, or they are just being kept track for other reasons.

@mksd

@tendomart could you describe what the business needs are for program attributes on a couple of examples?

@mksd

@ssmusoke has laid it bare as it should be.