(feat) O3-5124: Add Patient Identifier Sticker configuration to Distro

[jnsereko]

Summary

This configuration defines the layout and content settings for patient identification stickers.

1. Sticker Fields to Display:

   • Name
   • Date of Birth (DOB)
   • Age
   • Gender
   • Full Address

2. Sticker Dimensions:

   • Width: 70mm (default)
   • Height: 50mm (default)

3. Visual Settings:

   • Barcode: Enabled - displays a barcode representation of the patient identifier
   • Header: Enabled - includes a header section with the OpenMRS logo
   • Label Font Size: 2
   • Value Font Size: 4
   • Label-Value Gap: 1mm spacing between labels and their corresponding values

4. Additional Configuration:

   • Stylesheet: Uses patientIdStickerFopStylesheet.xsl for formatting which shows each value below its corresponding Field on a new line.
   • Logo: Displays the OpenMRS logo from web/module/resources/OpenMRS_logo.png added with Fix logo and address not showing in Sticker openmrs-module-patientdocuments#3
   • Pages: Prints only a single page of the sticker

Related Issue

https://openmrs.atlassian.net/browse/O3-5124

[jnsereko]

cc @dkayiwa, @ibacher

[ibacher]

Can we move this to the "referenceapplication-demo" repo? The general dividing line is that this has the minimal metadata necessary to run O3 whereas the "-demo" has all the metadata that might need to be tweaked by an implementation.

[dkayiwa]

@ibacher so for someone to take advantage of this printing functionality, they need to include demo data?

[ibacher]

@dkayiwa If they want it out of the box, yes, but we ship that content package as part of the release. The idea of separating the two is to make it easier to override or customise the options.

[dkayiwa]

@ibacher so it is easier to override/customise from the demo content package than the core content package?

[ibacher]

Not at a technical level, but organisationally the goal is to make it clear the metadata that's easily tweakable (and so an example configuration) vs the metadata where the app won't run.

[dkayiwa]

By app won't run, do you mean errors on startup and hence you cannot even log in? Or do you simply mean some features not usable?

[ibacher]

@dkayiwa More on inability to login side of things than features being unusable. I.e., many features won't work out of the box without something like the configurations in the -demo package, but they don't need to be those. OTOH, the login screen needs the "Login Location" tag to be assigned to at least one location so the location tag is part of this.

[dkayiwa]

Oh i see! Now i get the point. Thanks for bearing with my infinite loop of questions about this. 😊

[ibacher]

No, this has pointed out to me that we haven't actually documented that, so it's rule that exists mostly in my head, which is not right!

[dkayiwa]

Looool 😃

[jnsereko]

Thank you @ibacher and @dkayiwa
I have created a PR in demo to follow this up and will close this.