npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@jahmezz/patient-ranker

v0.1.3

Published

Entry for Luma Health full-stack interview.

Readme

Patient Ranker

Healthcare facilities spend a large amount of time attempting to get a hold of patients. Patients are liable to cancel appointments, fail to respond in a timely fashion, and take other actions that can generally lower a facility's efficiency in filling schedules.

Patient Ranker is a customizable library that provides a framework for ranking the patients' likelihood of accepting appointments based on historical data.

It accepts patient historical data and outputs a ranked list of the patients most likely to respond.

Prerequisites

This library was built on Node v8.6.0.

It is written in ES6, meaning you must run it with esm for it to run properly.

$ node -r esm {your project}

Getting Started

First, install the library.

$ npm install @jahmezz/patient-ranker

Import the RankGenerator module into your project. Then, Load your patient data as JSON.

import RankGenerator from '@jahmezz/patient-ranker/RankGenerator'
let patientRanker = new RankGenerator();
patientRanker.loadPatientData({your patient data});

Then, request a list of patients using patientRanker.fetchBestPatients(facilityLocation).

This function accepts an object containing latitude and longitude. The output is a sorted array of the patients most likely to accept an appointment offer.

Input

let facilityLocation = {
    "latitude": "68.8129",
    "longitude": "71.3018"
}
let bestPatients = patientRanker.fetchBestPatients(facilityLocation);
console.log("Score: " + bestPatients[0].score);
console.log("ID: " + bestPatients[0].entry.id);
console.log("Name: " + bestPatients[0].entry.name);

Output

Score: 9.26
ID: 9902ce99-e4aa-434b-a5b5-49f2ae156391
Name: Laurine Kshlerin

An index.js is included with the project that you can run and review as an interactive demo.

$ node -r esm index.js

Running the tests

Run the following command:

$ npm test

The test suite consists of unit tests ensuring the functions in this library work properly.

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

Authors

  • James Kahng - Initial work - jahmezz

License

This project is licensed under the MIT License - see the LICENSE.md file for details

Acknowledgments

  • Much inspiration drawn from Akash's solution to the interview question.