HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
breck7
pau
JavaScript2019–2024
breck7 / pau

pau

Medical records you can copy and paste

Explore on GitHubRead Hacker News discussions
2Distinct people
6Mentions
1Explicit recommenders
12GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Medical records you can copy and paste

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

Hi! We are interested in similar problems. I worked on a new idea for EMR at UH Cancer Center called Pau (https://github.com/breck7/pau). It's now encompassed as a tiny part of…

breck used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2019-09-25 16:24:38 UTC to 2024-07-23 01:12:07 UTC.

012342019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC413
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

6 sources
breck·Jul 23, 2024Recommendation phrase
Hi! We are interested in similar problems. I worked on a new idea for EMR at UH Cancer Center called Pau (https://github.com/breck7/pau). It's now encompassed as a tiny part of a larger effort called Scroll (https://scroll.pub/). You might be interested in learning about ScrollSets (https://breckyunits.com/scrollsets.html) Happy to chat if you want some feedback (email is breck7@gmail.com) P.S. I love your focus on the concept of "instruments". Great word choice. Bullseye concept--well done!
In Show HN: OpenDataCapture an electronic data capture platform for data collection
breck·Nov 11, 2019
Awesome! We are on the same page on a lot of things. > It is your data and shouldn't belong to the provider. Agreed! What do you think of the concept of the "Copy/Paste Test"? The idea is a good EHR should allow you to copy/paste your entire medical history into an email in a non-fragile way. If it can't do that, it's not a good EHR. We think this one dimension encompasses a lot of sub dimensions of what goes into a well designed EHR system. > It would require an institutional body/government to standardize the EMR and centralize it We're thinking the opposite: decentralized, git backed, concatenative grammars. You eventually probably would indeed have one grammar rise to the top, but the idea is to allow anyone to view, suggest edits, and fork the collection of grammars. Here is the current collection of Pau Grammar files: https://githu
Read the rest
b.com/treenotation/pau/tree/master/grams. Note: this isn't even v1 yet, but the core ideas are there.
In Google's ‘Project Nightingale’ Gathers Personal Health Data on Millions
breck·Oct 30, 2019
If anyone is interested in a revolutionary new type of medical records system where you can copy/paste your entire medical records in a safe way, we are working on a system here called Pau (https://github.com/treenotation/pau). Imagine if you could just copy/paste your medical records in an email to change doctors. Or participate in a new medical study via a simple copy/paste. Or if you were in an acute care setting and your healthcare providers could instantly call up all your relevant medical history. We are going to enable those sort of things.
In Biology Is Eating the World
breck·Sep 25, 2019
This is a great perspective, thanks. > what sea change are you expecting that will bring in a large number of beginners? I think a number of kill apps will arise that exploit Tree Notation. Let me mention 2 teams I spend a lot of time with. One is working on a paper for a new system for EMR where healthcare providers/clinicians/researchers use the same syntax for the whole life cycle of medical data. So nurses in Bolivia might write intake notes on pen and paper in an EMR Tree Language; doctors in India may dictate notes into an EMR Tree Language; patients may copy/paste their entire medical records from one provider to the next during an acute care visit; and researchers at the end of the pipeline might get their data in a clean strongly typed Tree Language before loading into a deep learning training model. https://github.com/treenotati
Read the rest
on/pau The second is a new language for data science that will make inroads amongst the Python/R data science crowd as well as pull Excel users over. It's a language and runtime that runs in your browser on your computer or your smart phone, and does everything locally. Nothing to install, no funny syntax to learn, the world's clean data will be at your fingertips, easy to share EDA results. https://github.com/treenotation/ohayo The WHO estimates there are about 40M professionals in the healthcare industry. I've seen estimates that there are 750M Excel users. None of the TIOBE languages exceeds 20M. So I think either of those 2 alone could be bigger in 2027 in terms of user base than any language on the TIOBE top 10. But I expect dozens of giant killer apps that will be built by startups/teams that I have no involvement with. People are exploring it in the legal space, crypto space, web form space, educational programming space, gaming space, and on and on. The ideas are there for the taking. It's going to be like the 1990's web boom all over again. > And why will they learn (or be taught) a tree language? Simplicity is timeless. Binary Notation is the dominant notation of our day. It's 330 years old. All of the TIOBE top 10 are under 50 years old. Binary Notation can't get simpler without sacrificing a lot of functionality. Likewise, AFAIK Tree Notation can't get simpler without sacrificing a lot of functionality. It's more akin to some universal pattern in nature than it is to a man made invention. Now, I'm not saying it's perfect and odds are high that I have screwed something up royally (you can see the earlier versions starting around 2011 called Noted and then Space to see previous critical flaws I had), and that's what I'm hoping to be the outcome of this Long Bet: someone will point out some critical flaw that I haven't seen, or some people will try, fail, and then see the potential and jump on board the train.
In In 2027, at least 7 out of the top Tiobe languages will be Tree Languages

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.