open-index/open-npm huggingface dataset:
npm package: @nhealth/admin
Description: FHIR admin layer for nHealth
Latest version: 0.0.43

# FHIR for Nuxt
Build FHIR applications rapidly with Nuxt

## ✅ Status

Currently under development (WIP).

## FHIR Server

nhealth is designed to work with various FHIR servers. Currently, it supports Hapi and Medplum.

## Overview

This repository provides a framework for building FHIR applications using Nuxt. It includes several packages and modules to facilitate the development of FHIR-compliant applications. The key components are:

- **packages/auth**: Manages authentication and session handling.
- **packages/profiling**: Offers tools for profiling and managing FHIR resources.
- **packages/app**: The main application layer that integrates the other packages.
- **playground/profiling**: A sample project demonstrating profiling capabilities.
- **packages/questionaire**: Questionaire builder and viewer for FHIR applications. [WIP]
- **playground/demo**: A demo project showcasing the framework's usage.

Each package and project is designed to work together, providing a comprehensive solution for building FHIR applications with Nuxt.

## TODO
- Test with Open Servers: https://confluence.hl7.org/spaces/FHIR/pages/35718859/Public+Test+Servers
- Checkout Synthea: https://synthetichealth.github.io/synthea/

## FHIR Server Test
- https://atollee.com/de
- https://www.health-samurai.io/
npm package: @nhealth/app
Description: FHIR application layer for Nuxt based on Medplum Fhir server
Latest version: 0.0.43

# FHIR for Nuxt
Build FHIR applications rapidly with Nuxt

## ✅ Status

Currently under development (WIP).

## FHIR Server

nhealth is designed to work with various FHIR servers. Currently, it supports Hapi and Medplum.

## Overview

This repository provides a framework for building FHIR applications using Nuxt. It includes several packages and modules to facilitate the development of FHIR-compliant applications. The key components are:

- **packages/auth**: Manages authentication and session handling.
- **packages/profiling**: Offers tools for profiling and managing FHIR resources.
- **packages/app**: The main application layer that integrates the other packages.
- **playground/profiling**: A sample project demonstrating profiling capabilities.
- **packages/questionaire**: Questionaire builder and viewer for FHIR applications. [WIP]
- **playground/demo**: A demo project showcasing the framework's usage.

Each package and project is designed to work together, providing a comprehensive solution for building FHIR applications with Nuxt.

## TODO
- Test with Open Servers: https://confluence.hl7.org/spaces/FHIR/pages/35718859/Public+Test+Servers
- Checkout Synthea: https://synthetichealth.github.io/synthea/

## FHIR Server Test
- https://atollee.com/de
- https://www.health-samurai.io/
npm package: @nhealth/auth
Description: Authentication and Authorization module for Nuxt based Fhir applications
Latest version: 0.0.43

# FHIR for Nuxt
Build FHIR applications rapidly with Nuxt

## ✅ Status

Currently under development (WIP).

## FHIR Server

nhealth is designed to work with various FHIR servers. Currently, it supports Hapi and Medplum.

## Overview

This repository provides a framework for building FHIR applications using Nuxt. It includes several packages and modules to facilitate the development of FHIR-compliant applications. The key components are:

- **packages/auth**: Manages authentication and session handling.
- **packages/profiling**: Offers tools for profiling and managing FHIR resources.
- **packages/app**: The main application layer that integrates the other packages.
- **playground/profiling**: A sample project demonstrating profiling capabilities.
- **packages/questionaire**: Questionaire builder and viewer for FHIR applications. [WIP]
- **playground/demo**: A demo project showcasing the framework's usage.

Each package and project is designed to work together, providing a comprehensive solution for building FHIR applications with Nuxt.

## TODO
- Test with Open Servers: https://confluence.hl7.org/spaces/FHIR/pages/35718859/Public+Test+Servers
- Checkout Synthea: https://synthetichealth.github.io/synthea/

## FHIR Server Test
- https://atollee.com/de
- https://www.health-samurai.io/
npm package: @nhealth/fhir
Description: Create FHIR applications with Nuxt based on Medplum Fhir server
Latest version: 0.0.43

# FHIR for Nuxt
Build FHIR applications rapidly with Nuxt

## ✅ Status

Currently under development (WIP).

## FHIR Server

nhealth is designed to work with various FHIR servers. Currently, it supports Hapi and Medplum.

## Overview

This repository provides a framework for building FHIR applications using Nuxt. It includes several packages and modules to facilitate the development of FHIR-compliant applications. The key components are:

- **packages/auth**: Manages authentication and session handling.
- **packages/profiling**: Offers tools for profiling and managing FHIR resources.
- **packages/app**: The main application layer that integrates the other packages.
- **playground/profiling**: A sample project demonstrating profiling capabilities.
- **packages/questionaire**: Questionaire builder and viewer for FHIR applications. [WIP]
- **playground/demo**: A demo project showcasing the framework's usage.

Each package and project is designed to work together, providing a comprehensive solution for building FHIR applications with Nuxt.

## TODO
- Test with Open Servers: https://confluence.hl7.org/spaces/FHIR/pages/35718859/Public+Test+Servers
- Checkout Synthea: https://synthetichealth.github.io/synthea/

## FHIR Server Test
- https://atollee.com/de
- https://www.health-samurai.io/
npm package: @nhealth/fhir-profiling
Description: FHIR profiling module for Nuxt based on sushi and fsh
Latest version: 0.0.43

# FHIR for Nuxt
Build FHIR applications rapidly with Nuxt

## ✅ Status

Currently under development (WIP).

## FHIR Server

nhealth is designed to work with various FHIR servers. Currently, it supports Hapi and Medplum.

## Overview

This repository provides a framework for building FHIR applications using Nuxt. It includes several packages and modules to facilitate the development of FHIR-compliant applications. The key components are:

- **packages/auth**: Manages authentication and session handling.
- **packages/profiling**: Offers tools for profiling and managing FHIR resources.
- **packages/app**: The main application layer that integrates the other packages.
- **playground/profiling**: A sample project demonstrating profiling capabilities.
- **packages/questionaire**: Questionaire builder and viewer for FHIR applications. [WIP]
- **playground/demo**: A demo project showcasing the framework's usage.

Each package and project is designed to work together, providing a comprehensive solution for building FHIR applications with Nuxt.

## TODO
- Test with Open Servers: https://confluence.hl7.org/spaces/FHIR/pages/35718859/Public+Test+Servers
- Checkout Synthea: https://synthetichealth.github.io/synthea/

## FHIR Server Test
- https://atollee.com/de
- https://www.health-samurai.io/
npm package: @nhealth/questionnaire
Description: Easyily add FHIR Questionnaires to nhealth applications
Latest version: 0.0.43

# FHIR for Nuxt
Build FHIR applications rapidly with Nuxt

## ✅ Status

Currently under development (WIP).

## FHIR Server

nhealth is designed to work with various FHIR servers. Currently, it supports Hapi and Medplum.

## Overview

This repository provides a framework for building FHIR applications using Nuxt. It includes several packages and modules to facilitate the development of FHIR-compliant applications. The key components are:

- **packages/auth**: Manages authentication and session handling.
- **packages/profiling**: Offers tools for profiling and managing FHIR resources.
- **packages/app**: The main application layer that integrates the other packages.
- **playground/profiling**: A sample project demonstrating profiling capabilities.
- **packages/questionaire**: Questionaire builder and viewer for FHIR applications. [WIP]
- **playground/demo**: A demo project showcasing the framework's usage.

Each package and project is designed to work together, providing a comprehensive solution for building FHIR applications with Nuxt.

## TODO
- Test with Open Servers: https://confluence.hl7.org/spaces/FHIR/pages/35718859/Public+Test+Servers
- Checkout Synthea: https://synthetichealth.github.io/synthea/

## FHIR Server Test
- https://atollee.com/de
- https://www.health-samurai.io/
npm package: @nhevia/simple-docs
Description: "Simple documentation tool"
Author: Nicolas Hevia
Latest version: 0.6.5

![GitHub package.json version](https://img.shields.io/github/package-json/v/nhevia/simple-docs?style=flat-square) ![CircleCI Build Status](https://circleci.com/gh/nhevia/simple-docs.svg?style=shield "CircleCI Build Status") [![Known Vulnerabilities](https://snyk.io/test/github/nhevia/simple-docs/badge.svg?targetFile=package.json)](https://snyk.io/test/github/nhevia/simple-docs?targetFile=package.json)
![PR](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square) ![GitHub](https://img.shields.io/github/license/nhevia/simple-docs?style=flat-square) ![Twitter Follow](https://img.shields.io/twitter/follow/n_hevia?style=social)

# simple-docs

> A simple documentation tool.


### Installation

`npm install --save-dev @nhevia/simple-docs`

### Usage

- Add **sdoc** as a package.json script:

```
"scripts": {
  "docs": "sdoc"
}
```

- Use a comment block at the start of any file with `sdoc` preffix:

```javascript
/*sdoc
This is the main component
*/

// your code
```

- Run `npm run docs`. It will indentify documentation blocks in your project and generates an output file (`sdoc.md` by default, on root folder):


Since the generated file is markdown, it is supported inside documentation blocks.

```javascript
/*sdoc
  This is the **main** component
*/
```

![image](https://user-images.githubusercontent.com/50466554/91442173-b727aa80-e871-11ea-9a97-b54b94d9d72a.png)

### Options

- `-f <filename>, --file <filename>`  
Set the output file name:
`sdoc -f docs-components` | `sdoc --file docs-components`
>
- `-ni, --no-index`  
Set the output file name.
`sdoc -ni` | `sdoc --no-index`


### Why?

Most major documentation libraries have tools that are beyond the current necessities for personal projects.

I needed a **really** simple tool to generate documentation for my scripts. Insert a comment block at the beggining of the file describing it and its usage and that's it.

Note that if you're working in a team with multiple people, there are better, more tested and reliable alternatives.

### Contributing

Pull requests are more than welcome. 


### License

Copyright © 2020 Nicolas Hevia
This project is [MIT](https://opensource.org/licenses/MIT) licensed
npm package: @nhi/auth0-spa-js
Description: Auth0 SDK for Single Page Applications using Authorization Code Grant Flow with PKCE
Author: NHI
Latest version: 1.16.1

# @nhi/auth0-spa-js

Auth0 SDK for Single Page Applications using [Authorization Code Grant Flow with PKCE](https://auth0.com/docs/api-auth/tutorials/authorization-code-grant-pkce).

This is a fork from auth0 that adds support for form-urlencoded and gettings the config from the .well-known/openid-configuration endpoint. For more information see the: [pull request 458 auth0-spa-js](https://github.com/auth0/auth0-spa-js/pull/458).

The fork is updated automatically against the master from auth0 and will only be updated as long the rebase goes fine automatically.

The fork add experimental features and support is not given.

## Table of Contents

- [Documentation](#documentation)
- [License](#license)

## Documentation

- [Documentation](https://auth0.com/docs/libraries/auth0-spa-js)
- [API reference](https://auth0.github.io/auth0-spa-js/)
- [Migrate from Auth0.js to the Auth0 Single Page App SDK](https://auth0.com/docs/libraries/auth0-spa-js/migrate-from-auth0js)

## License

This project is licensed under the MIT license. See the [LICENSE](https://github.com/nhi/auth0-spa-js/blob/master/LICENSE) file for more info.
npm package: @nhi/eslint-config
Description: Shareable ESLint config for React/Node/TypeScript projects by NHI
Author: Balazs Orban
Latest version: 0.0.12

# @nhi/eslint-config <img src="https://upload.wikimedia.org/wikipedia/en/thumb/e/e3/ESLint_logo.svg/128px-ESLint_logo.svg.png" width=32/>

Shareable ESLint config by [Norsk Helseinformatikk AS](https://nhi.no)

## Usage

Use it in the following type of projects:
- React
- Node.js
- TypeScript


## Installation
1. Open your terminal
2. `cd your-project`
3. Install ESLint and the config itself with yarn or npm
   - `yarn add -D eslint @nhi/eslint-config`
   - `npm i -D eslint @nhi/eslint-config`
4. Add the following to your `package.json`:
   ```json
   "eslintConfig": {
     "extends": "@nhi"
   }
   ```
5. Enjoy! 🎉
npm package: @nhi/todo-to-azure
Description: Parses code for TODO (and other) annotations, and creates tasks/backlog items on Azure DevOps Boards
Author: Balazs Orban
Latest version: 0.0.13

# @nhi/todo-to-azure

> THIS IS EXPERIMENTAL ⚠

Parses your code for TODO (and other) annotations, and creates tasks/backlog items on Azure DevOps Boards, under the Current Iteration.

It will write back a URL for the created item into the comment.

## Example:

Before:
```
/**
 * TODO:
 * This must be done!
 */ 
```

After:
```
/**
 * TODO: https://dev.azure.com/{organization}/{project}/_workitems/edit/{id}
 * This must be done!
 */ 
```
And this will be added as a Work Item to `organization` in `project`, with `id`. 


## Installation

```sh
yarn add -D @nhi/todo-to-azure
```
or
```sh
npm i -D @nhi/todo-to-azure
```

## Usage

```
Usage: todoo [options]

Options:
  -v, --verbose         Verbose logging (default: false)
  -d, --dry             Only show parsed Work Items (default: false)
  -P, --show-processed  Show a list of already processed Work Items (default: false)
  -c, --config          Specify location of config file (default: .todo-to-azure.js)
  -i  --include         Glob pattern for files to parse (default: src/**/*.js)
  -t, --token           Personal Access Token for Azure Devops
                        Required scopes:
                        • Project and Team - Read & Write
                        • Work Items - Read & Write
                        Can be also defined in the config file
  -V, --version         output the version number
  -h, --help            display help for command
```

> If you specify the Personal Access Token `token` in your config file, be sure the file is gitignored, if your repository is public!

## Configuration

You can either use the flags shown in [Usage](#usage), or use an external file. This is `.todo-to-azure.js` by default.

It looks like this:

```js
module.exports = {
  include: "path/to/src/**/*.js",
  organization: "ORG",
  teamContext: {
    team: "Team name",
    project: "Project name"
  },
  token: "PERSONAL_ACCESS_TOKEN",
  annotations: ["TODO", "HACK", "BUG", "FIX"]
}
```
---
Created by <a href="https://nhi.no"><img alt="NHI.no" src="https://avatars3.githubusercontent.com/u/57369452?s=200&v=4" width=24/></a>
npm package: @nhimm/node-red-contrib-data-forge
Description: Data Science nodes for Node-RED using Data-Forge. Includes custom debug node for displaying Data-Forge dataframes in table format.
Author: BenVeenema
Latest version: 0.0.1

# Node-RED Contrib Data-Forge

This Node-RED package, `@nhi/node-red-contrib-data-forge`, provides a collection of nodes designed to facilitate data science tasks within Node-RED using the Data-Forge library. It includes nodes for filtering, melting data, renaming series (columns), and a custom debug node for displaying Data-Forge dataframes in a table format.

## Features
More functions from Data-Forge will be added over time, as of release 0.0.1 the following nodes/functions are avilable:
- **Filter**: Allows filtering of data based on specified criteria.
- **Melt**: Transforms data from wide format to long format.
- **Rename Series**: Enables renaming of one or more series (columns) in a DataFrame.
- **DebugDF**: A custom debug node tailored for visualizing Data-Forge DataFrames in a user-friendly table format.

## Installation

To install this package, you can use Node-RED's Palette Manager or run the following command in your Node-RED user directory (typically `~/.node-red`):

```bash
npm install @nhi/node-red-contrib-data-forge
```

## Dependencies
This package relies on the following NPM packages:

- data-forge: A powerful data manipulation and analysis library for JavaScript.
After installation, the nodes will be available in the Node-RED editor under the dataForge category. Drag and drop the nodes into your flow and configure them according to your data processing needs.

## Contributing
Contributions to this package are welcome. Please ensure that your contributions adhere to the following guidelines:

- Follow existing coding styles and practices.
- Update the README.md with details of changes to the interface or significant functionality.

## License
This project is licensed under the MIT License - see the LICENSE file for details.

## Acknowledgments
Ashley Davis and the Data-Forge library, for providing the data manipulation capabilities.