fhir
Zato
fhir | Zato | |
---|---|---|
9 | 3 | |
525 | 1,082 | |
2.5% | - | |
9.7 | 9.9 | |
10 days ago | 20 days ago | |
HTML | Python | |
GNU General Public License v3.0 or later | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fhir
-
AWS Step Functions Callback Pattern
I skipped over the prepare change function that is at the beginning of the sub-map flow because it's outside of the scope of this article. But when you choose AWS HealthLake you are signing up for a FHIR compliant datastore. FHIR stands for Fast Healthcare Interoperable Resource and it's the go-to and preferred format for exchanging Patient and other Healthcare data between domain boundaries externally. The prepare function breaks the NDJSON up and makes little FHIR payloads to be sent downstream into the ecosystem.
-
Salary transparency thread
For someone breaking into the industry, I would recommend starting here: https://hl7.org/fhir/ This is the future of data interoperability in healthcare. And if you understand this and how it works and get certified in it, you should be able to write your own ticket. If you can combine that with API development chops, you are golden. One thing I'll note is that healthcare data is its own unique animal but the items you see on that page look very similar to how healthcare data is organized in major systems.
-
Issue with ordering JSON keys when marshalling an ordered map
In this case, it appears that the source data are FHIR resources where a resourceType field canonically comes first (though is not required by the spec to do so I believe).
- Helseplattformen har valgt et system som er utviklet for et annet helsevesen og som det er logiske problemer med å få til å fungere hos oss
-
Anyone else work with health databases or HL7v2 everyday, but still a bit bamboozled by the concept of FHIR?
The docs are very helpful: https://hl7.org/fhir/
-
XPathNodeIterator not Iterating/Having Trouble with Returning Attributes
XPathDocument docNav; XPathNavigator nav; XPathNodeIterator nodeIter; string strExpression1; docNav = new XPathDocument(@"..\..\..\patient-example.xml"); nav = docNav.CreateNavigator(); XmlNamespaceManager namespaceManager = new XmlNamespaceManager(nav.NameTable); namespaceManager.AddNamespace("fhir", "http://hl7.org/fhir"); strExpression1 = "/Patient/telecom"; nodeIter = nav.Select(strExpression1, namespaceManager)); Console.WriteLine($"The XPath {strExpression1} expression yields the following phone numbers: "); while (nodeIter.MoveNext()) { XPathNodeIterator childIter = nodeIter.Current.SelectChildren("value", ""); Console.WriteLine($"Attribute: {childIter.Current.GetAttribute("value", "")}"); };
-
Who owns the copyright to my medical images?
I want to point out that in the United States, patients have access to their health data via API using open standards that are free and accessible for developers.
This is now.
There is a huge lack of applications that make use of these APIs and the opportunities to improve patient's managing their own health are enormous.
You can start here:
http://hl7.org/fhir/
(and maybe click on Resources to get an idea of what this is all about).
-
Need Medical Knowledge Graph
Have you heard about FHIR? http://hl7.org/fhir/ It's expressed in Turtle (among other formats). Not specifically for mental disorder, but it might help.
-
Billing API for Medicaid and Tricare
Here is the implementation if you want to give it a go: https://github.com/HL7/fhir
Zato
-
We Should Have Markdown Rendered Websites
Yes, the article is correct, there is a market for Markdown sites and related products.
Our Zato website is in Markdown: https://zato.io
We have a purpose-built static site generator, which makes sense in our case because:
* The resulting site is very fast, seeing as there is no need for runtime generation of any assets / HTML / any kind of resources
* It is easier for developers to work on documentation because they already know Markdown
* It is easy to statically apply filters such as spell checkers for multiple languages during the build
* Various optimizations can be applied, e.g. incremental builds or on-demand builds
The drawbacks are:
* Non-technical translators may have a difficult time working with anything but either their own specialized tools or MS Word and they consider Markdown to be "advanced"
* Sometimes you work with writers who are not technical at all and who will not understand what a build system is even if they are open to the idea of learning Markdown itself
Thus, there is a market for a lightweight CMS that would enable non-technical people to author Markdown in their browsers, without a need for any command line usage.
- Open-Source ESB, API, AI and Cloud Integrations in Python
- Service-Oriented Architecture (SOA)
What are some alternatives?
synthea - Synthetic Patient Population Simulator
pycon
invesalius3 - 3D medical imaging reconstruction software
python-fints - Pure-python FinTS (formerly known as HBCI) implementation
healthlake-export-manager - Sample and working repos to demonstrate exporting data from AWS HealthLake to trigger downstream operations
okuna-api - 🤖 The Okuna Social Network API
umls2rdf - These python scripts connect to the Unified Medical Language System (UMLS) database and translate the ontologies into RDF/OWL files. This is part of the BioPortal project.
scroll - Scroll is a language for scientists of all ages. Scroll includes a command line app that builds static blogs, websites, CSVs, text files, and more.
cogat - Cognitive Atlas
python-n26 - 💵 Unofficial Python client for n26 (Number 26) - https://n26.com/
Alerta - Alerta monitoring system
abna - Python library to automatically retrieve mutations from ABN Amro