@kenyaemr/esm-service-queues-app 7.0.2-pre.65

package/.turbo/turbo-build.log

@@ -0,0 +1,40 @@
+assets by path *.js 2.51 MiB
+  assets by chunk 1.27 MiB (id hint: vendors)
+    assets by status 1.13 MiB [big]
+      asset 130.js 643 KiB [emitted] [minimized] [big] (id hint: vendors) 2 related assets
+      asset 430.js 518 KiB [emitted] [minimized] [big] (id hint: vendors) 2 related assets
+    asset 940.js 76.3 KiB [emitted] [minimized] (id hint: vendors) 1 related asset
+    asset 591.js 50.8 KiB [emitted] [minimized] (id hint: vendors) 2 related assets
+    asset 729.js 6.06 KiB [emitted] [minimized] (id hint: vendors) 1 related asset
+    asset 255.js 5.57 KiB [emitted] [minimized] (id hint: vendors) 2 related assets
+  + 32 assets
+assets by path *.json 21.5 KiB
+  asset kenyaemr-esm-service-queues-app.js.buildmanifest.json 19 KiB [emitted]
+  asset routes.json 2.54 KiB [emitted] [from: src/routes.json] [copied]
+orphan modules 3.5 MiB [orphan] 767 modules
+runtime modules 39.5 KiB 28 modules
+built modules 5.81 MiB (javascript) 252 bytes (share-init) 252 bytes (consume-shared) [built]
+  javascript modules 5.72 MiB 181 modules
+  optional modules 95.1 KiB [optional]
+    ./translations/am.json 11.2 KiB [optional] [built] [code generated]
+    + 8 modules
+  provide-module modules 252 bytes
+    modules by path provide shared module (default) swr/ 84 bytes 2 modules
+    + 4 modules
+  consume-shared-module modules 252 bytes
+    modules by path consume shared module (default) swr/ 84 bytes 2 modules
+    + 4 modules
+
+WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
+This can impact web performance.
+Assets: 
+  main.js (764 KiB)
+  130.js (643 KiB)
+  430.js (518 KiB)
+
+WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
+Entrypoints:
+  main (764 KiB)
+      main.js
+
+webpack 5.88.0 compiled with 2 warnings in 58774 ms

package/README.md

@@ -0,0 +1,20 @@
+# Service Queues
+
+The `Service Queues` app is a frontend module that enables users to track a patient's progress as they move through a clinic. Users can see an overview of various clinic metrics such as:
+
+- The number of active visits.
+- The number of patients waiting for a particular service.
+- The average number of minutes spent by patients waiting for a service.
+
+The key component of the service queue app is the `Active Visits` table. It displays a tabular overview of the active visits ongoing in a facility and the wait time of patients. Users can add patients to the service queue by starting visits for them. They can also view information from the current active visits as well as the previous visit on each queue entry by clicking the table extension slot. Users can also change the priority and status of an entry in the queue from the UI, effectively moving a patient from one point in the queue to another. In order to indicate that a patient is currently attending service, click on the bell icon. In order to edit an entry, click the pencil icon. 
+
+Amend the following concepts in the configuration schema to get started using the module:
+- `defaultPriorityConceptUuid` - concept UUID for `not urgent`.
+- `defaultStatusConceptUuid` - concept UUID for `waiting`.
+- `emergencyPriorityConcept` - concept UUID for `emergency`.
+
+After configuring the concepts, add the services according to the facility setup by clicking the `Add new service` button.
+
+In order to configure rooms that provide different services, click the `Add new room` button. To view patients attending service in different rooms, click the `Queue screen` button.
+
+You should now be able to leverage the service queues module 🎉