Create nbri_ehr module

[labkey-martyp]

Rationale

Seeds the new nbriEHRModules repository with a working EHR module so NBRI development can proceed from a functioning baseline.

Related Pull Requests

None.

Changes

• Added the initial nbri_ehr module tree (~1,060 files: Java, JS, SQL, XML, HTML, TSV, gradle/properties, sample data), including the org.labkey.nbri_ehr Java package, NBRI_EHR* classes, and the NBRI_EHR folder type.
• Updated the GitHub workflow files with permissions blocks required by the release automation.
• Updated .gitignore to exclude referenceStudy ETL logs.

[labkey-bpatel]

Overall looks like a good starting point.

I am sure we'll trim and iterate as development progresses, but a few things stood out on this initial pass:

1. Are we planning to ETL data into this module? If not, the ETL queries and definitions and go.
2. Area/Building-specific .qview.xml files - there are quite a few of these with hardcoded location names (e.g. activeBehaviorCases/Building 10.qview.xml). Since these are site-specific and easy to recreate from the UI, I think we can drop them.
3. Two nbri_ehr DB scripts - any reason not to combine these into a single script?
4. nbri_ehr/resources/web/nbri_ehr/images/ull-logo-main-subsite.png - should be removed.
5. Death/Necropsy workflow - the combined form is complex and quite center-specific. Would it be worth splitting into two separate forms (a simpler Death form and a separate Necropsy form) as a baseline?
6. Copyright headers - Since this is the initial commit, normalize 'Copyright (c) 2024-2026 LabKey Corporation' (and other date-range variants) to 'Copyright (c) 2026 LabKey Corporation' across the new files.

Revised comments from claude code review:

1. Remove the duplicate CagematesDemographicsProvider registration.
2. Escape HL7 delimiters in the Orchard file writer.
3. Null-check birth before formatting in the Orchard file writer.
4. Guard isProcedureOrderEntered against empty result and null qcstate.
5. Delete datasetBirth.tsv~.
6. Non-blocker: Three workflows (branch_release.yml, merge_release.yml, validate_pr.yml) each add a top-level permissions: block that matches what the reusable actions require. actions/checkout@v3 is used in two of them - GitHub has been recommending v4 for a while; not blocking, but consider bumping to keep parity with the newer LabKey repos.

[labkey-martyp]

Thanks for the thorough review — all of this is addressed in 3f602e0 except the Death/Necropsy split:

1. ETLs: No ETL planned for this module, so the ETL definitions, dbo source queries, the CasesTemp staging table, and the now-unreferenced NBRIUserCreateTransform are all removed. We also removed the Orchard/HL7 integration entirely (generator, queries, module property, trigger calls, test coverage), which moots the escaping/null-check items.
2. Location qviews: All 250 Building/Area .qview.xml files are dropped.
3. DB scripts: Combined into a single nbri_ehr-0.000-25.001.sql.
4. Logo: Removed, along with its page references and other leftover NIRC branding.
5. Death/Necropsy: Agreed the combined form is complex — splitting it into a simpler Death form and a separate Necropsy form is bigger than this seeding PR, so we'd like to defer it to a follow-up issue and keep this PR as the working baseline.
6. Copyright headers: Normalized to 2026 across the module.

The inline comments (get_instance() rename, unused category param, duplicate CagematesDemographicsProvider) and the remaining code-review items (isProcedureOrderEntered guard, datasetBirth.tsv~, checkout@v4) are also fixed.