synthea VS fhir

As someone working in this arena, I offer an alternative perspective for your consideration: healthcare was an early adopter of information technology and as a result many of its most core technologies come from a nearly unrecognizable time in computing. These systems are “outdated” as a result of success.

The current prevalence of these venerable technologies may be in part due to regulation, but more often has to do with their success.

HL7v2 is just token delimited ascii. Not unlike the similarly primitive but ubiquitous csv. The fields within it are defined by standards documents and once you use it a little, you can read enough to get the gist of most messages. As you might guess, modules in your language of choice are used to parse and compose HL7v2 so its detail isn’t that important.

Something I’d like to point out about Google Hospital is that under the hood it uses MITRE’s Synthea to generate synthetic patient data.

https://www.healthcareittoday.com/2017/09/13/open-source-too...

https://synthetichealth.github.io/synthea/

Have you tried Synthea? https://github.com/synthetichealth/synthea

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.

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.

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).

The docs are very helpful: https://hl7.org/fhir/

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", "")}"); };

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).

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.

Here is the implementation if you want to give it a go: https://github.com/HL7/fhir