51–60 of 103 posts
I’m a huge fan of Metriport, Dima, and the whole team! I’m constantly impressed by the strides you are making in addressing this significant problem. I often brainstorm company ideas just to have the opportunity to use Metriport.
- Amit
Earlier quoted context omitted.
Is this intended for use by providers or consumers/patients? Authorized providers can use TEFCA through a QHIN to query for treatment purpose of use, which is supported by all participants. How does your service differ in practice from existing networks of networks like Health Gorilla and Particle Health?
> Is this intended for use by providers or consumers/patients? This currently can only be used by providers, or healthcare IT vendors working with providers. Referring to the post: "using Metriport for patient data exchange today requires a Treatment purpose of use under HIPAA - which means that only Covered Entities, or Business Associates who work with Covered Entities, can use Metriport." > Authorized providers ca…
Earlier quoted context omitted.
Is this intended for use by providers or consumers/patients? Authorized providers can use TEFCA through a QHIN to query for treatment purpose of use, which is supported by all participants. How does your service differ in practice from existing networks of networks like Health Gorilla and Particle Health?
> Is this intended for use by providers or consumers/patients? This currently can only be used by providers, or healthcare IT vendors working with providers. Referring to the post: "using Metriport for patient data exchange today requires a Treatment purpose of use under HIPAA - which means that only Covered Entities, or Business Associates who work with Covered Entities, can use Metriport." > Authorized providers ca…
Congrats on the launch, the site it's quite nice and informative... "Access comprehensive EHR data for your patients in seconds, with FHIR R4...", I got Vietnam flashbacks from building an app to interface with the NHS Covid Vax certificate, that was my first encounter with FHIR... And honestly, all I wanted by the end of the day was to set myself on FHIR! Such a complex abstraction. Anyway, Godspeed!
Hahaha definitely feel you there - also see you're a seasoned healthcare vet with the FHIR puns! Integrating with vaccine registries is another unique beast, and we haven't had the pleasure of doing that yet. Each state has actually has its own registry, they don't even use FHIR, and instead use an even older standard than C-CDAs - CAIR2 HL7v2: https://www.cdph.ca.gov/Programs/CID/DCDC/CAIR/CDPH%20Docume... We don't…
https://repository.immregistries.org/resource/hl7-version-2-...
The CDC IZ Gateway can make it somewhat easier to work with multiple state registries.
https://www.cdc.gov/vaccines/programs/iis/iz-gateway/overvie...
In practice the C-CDAs obtained from providers sometimes include immunization section entries so you can pick up some records that way as well
There actually is a standard for converting C-CDA records to FHIR. It isn't 100% complete but serves as a useful starting point. If you find problems with it you can feed those back into the standards process.
Microsoft has an open source library which works pretty well and I think implements at least part of that standard, although I haven't used it lately.
https://github.com/microsoft/FHIR-Converter
FHIR also includes unstructured narrative text so it isn't necessarily better than C-CDA in that regard. You'll find that data quality problems come down more to provider systems configuration and charting policies rather than data formats.
I know this wouldn't fly in the US, but it is a very convenient system for people.
Where I live we have a centralized system run by government that all healthcare providers are required to integrate with. You can access & manage all your data & healthcare history from a single location, for free. I know this wouldn't fly in the US, but it is a very convenient system for people.
Earlier quoted context omitted.
Yes it was - it was internal to our company, but the apps got sold off when the business downsized. The engineering team lobbied to have the main backend open sourced, partly because it made the divestment of the apps built on it easier. The architecture was that that was a backend for apps, and the individual apps would host a stateless BFF service to translate the backend into what they needed, and then the web/mob…
Was there anything else at Sensyne that could have been open-sourced and/or of value to the community? I may be in a position to open some of that up before it's lost.
I think the only other useful thing that wasn't added to the Foundation was some HL7 integration code that would sit in a customer environment and forward on requests to that backend securely. I believe that moved on with the software that it was primarily developed for, though, which is an in-hospital tablet based system for recording patient observations.
Is there/do you plan on creating in foreseeable future post mortem of the tracking app beyond the note on your reddit?