open-index/open-npm huggingface dataset:
npm package: @pih/esm-refapp-navbar
Description: A RefApp-styled navbar compatible with the standard styleguide
Latest version: 1.0.1
Deprecated: Renamed to @pih/esm-refapp-navbar-app

# pih-esm-refapp-navbar

A RefApp-styled navbar compatible with the standard styleguide

[![Build Status](https://travis-ci.com/pih/pih-esm-refapp-navbar.svg?branch=master)](https://travis-ci.com/pih/pih-esm-refapp-navbar)
npm package: @pih/esm-referrals-queue
Description: A page for viewing the J9 Home Visits from CommCare
Latest version: 1.0.2
Deprecated: Renamed to @pih/esm-referrals-queue-app

# @pih/esm-referrals-queue

A page for viewing the J9 Home Visits from CommCare

[![Build Status](https://travis-ci.com/pih/pih-esm-referrals-queue.svg?branch=master)](https://travis-ci.com/pih/pih-esm-referrals-queue)

## Design Notes

*Copied from [PIH Confluence](https://pihemr.atlassian.net/wiki/spaces/DSS/pages/538116104/PIH+EMR+Referrals+Queue)*

![design](https://raw.githubusercontent.com/PIH/pih-esm-referrals-queue/master/design-mockup.png)

There should be one row per referral in this list (not one per encounter).  Some encounters may result in multiple referrals.  See the Referral Type logic below.

Note that the basic referrals workflow would be for J9 clinicians/managers to view the list of referrals here, then take action upon them one by one by clicking on the “pending” referrals.  This will bring them into editing the Home Visit form from which the referral came.  From there they specify any action taken on the referral and navigate back to this list. 
Check out the [design doc](https://pihemr.atlassian.net/wiki/spaces/DSS/pages/538116104/PIH+EMR+Referrals+Queue).


## Configuration
<!-- GENERATED BY OPENMRS CONFIG CLI -->
See the [openmrs-esm-module-config docs](https://wiki.openmrs.org/display/projects/openmrs-esm-module-config)
for information about how to provide configuration files.

- links
  - patientDash
    - **spa** *(default: false)*\
      *must be a boolean.*
    - **url** *(default: /coreapps/clinicianfacing/patient.page?patientId=${patientUuid}&app=pih.app.clinicianDashboard)*\
      *must be a string. url template may not include backticks.*
  - visitPage
    - **spa** *(default: false)*\
      *must be a boolean.*
    - **url** *(default: /pihcore/visit/visit.page?patient=${patientUuid}&visit=${visitUuid}&suppressActions=true#/overview)*\
      *must be a string. url template may not include backticks.*
  - homeVisitForm
    - **spa** *(default: false)*\
      *must be a boolean.*
    - **url** *(default: /htmlformentryui/htmlform/editHtmlFormWithStandardUi.page?patientId=${patientUuid}&visitId=${visitUuid}&encounterId=${encounterUuid}&definitionUiResource=file:configuration/pih/htmlforms/section-mch-referral.xml&returnUrl=/mirebalais/spa/referrals-queue)*\
      *must be a string. url template may not include backticks.*
- **pendingStatuses** *(default: Pending status,Referral unmet)*
  - arrayElements\
    *must be a string.*
<!-- END OF GENERATED -->
npm package: @pihub/components
Description: This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.1.0.
Latest version: 8.1.0

# Components

This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 19.1.0.

## Code scaffolding

Angular CLI includes powerful code scaffolding tools. To generate a new component, run:

```bash
ng generate component component-name
```

For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:

```bash
ng generate --help
```

## Building

To build the library, run:

```bash
ng build components
```

This command will compile your project, and the build artifacts will be placed in the `dist/` directory.

### Publishing the Library

Once the project is built, you can publish your library by following these steps:

1. Navigate to the `dist` directory:
   ```bash
   cd dist/components
   ```

2. Run the `npm publish` command to publish your library to the npm registry:
   ```bash
   npm publish
   ```

## Running unit tests

To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:

```bash
ng test
```

## Running end-to-end tests

For end-to-end (e2e) testing, run:

```bash
ng e2e
```

Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.

## Additional Resources

For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.