labkey / wnprc-modules

Custom LabKey modules developed by WNPRC

WNPRC Modules (for LabKey)

This repository includes all the custom LabKey modules developed by the WNPRC for use in the EHR system. Each subfolder contains a separate module.

Building the WNPRC Modules

To build the WNPRC EHR modules for development:

1. Follow the instructions to set up a LabKey development machine.
2. From the LabKey root directory:
   1. Clone this repo into the external modules directory:

      git clone https://github.com/WNPRC-EHR-Services/wnprc-modules.git externalModules/wnprc-modules

   2. Add the following to ~/.gradle/gradle.properties:

      moduleSet=../../externalModules/wnprc-modules/gradle/settings/wnprc

   3. Build LabKey, which includes all of our modules, too:

      ./gradlew deployApp

From there, all standard Gradle rules apply; you can build individual modules or even individual steps. For example:

# deploy our modules only
./gradlew :externalModules:wnprc-modules:deployModules

# build just the WNPRC_EHR module
./gradlew :ext:wnp:WNPRC_EHR:build

# re-run webpack for the breeding module
./gradlew :ext:wnp:bre:webpack

wnprc-modules's Issues

Ticket 49802: Problem with purchasing module display

Ticket 49802: Problem with purchasing module display

• Issue 49739: Remove use of org.apache.commons.net.ntp.TimeStamp or migrate to Date or a java.sql.Timestamp
• Investigate issue
• Fix issue
• TC verify & open PR
• Code review @labkey-adam @cnathe
• Code review changes
• TC verify and merge

Secure Issue 49291: Expanding the wnprc billing module

Issue 49291
Spec
Implementation on a 23.11 release

Tasks

• Investigate and scope out the details
• Investigate backwards compatibility
• Q&As with client
• Create a query for procedure charge id associations
• Spec & Implementation plan
• Implementation review @labkey-jeckels @ankurjuneja @labkey-martyp
• Schema updates - 1 hr
• Calculate costs - 2 hrs
• Refactor existing procedure query - 2 hrs
• Process queries - 5 hrs
• Test regression fixes - 3 hrs
• Test updates - 3 hrs
• Validation - 2 hrs
• Refactor email notification - 2 hrs
• Code Review - 1 hr @ankurjuneja @labkey-jeckels
• Code Review changes
• TC Verify and merge 📌