-
Notifications
You must be signed in to change notification settings - Fork 283
(feat) Add label printing app for handling printing concerns #2433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it may not make sense to merge this into the patient-banner-app, but to create a new app that can hold this (and depend on common reports) that exposes an extension that the patient-banner-app can use.
Thoughts?
if (!patient?.id) { | ||
throw new Error('Patient ID not found'); | ||
} | ||
return `${window.openmrsBase}/ws/module/commonreports/patientIdSticker?patientUuid=${patient.id}`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So common-reports would now need to be listed as a dependency in the routes.json if we merge this in.
I agree @ibacher - especially because I forsee implementations wanting to add a print action button elsewhere throughout the application (such as in patient-management apps like Queues and clerical views, for a fast-print button; or billing for receipts, etc) so couching this within the banner app feels a bit restrictive. Though I get the initial use case :) |
c4aadcc
to
7da2305
Compare
packages/esm-patient-label-printing-app/src/hooks/useSickerPdfPrinter.ts
Outdated
Show resolved
Hide resolved
packages/esm-patient-label-printing-app/src/hooks/useSickerPdfPrinter.tsx
Outdated
Show resolved
Hide resolved
Co-authored-by: Dennis Kigen <[email protected]>
Requirements
Summary
Previous versions of the Patient Identifier Sticker used react libraries to capture and print the sticker. Since this became slow on low processor powered devices, this approach focuses on getting the sticker from the backend using the Reporting tooling.
See backend work here
Screenshots
Screen.Recording.2025-05-08.at.15.17.34.mov
Arabic
Related Issue
Other