41–45 of 45 posts
Earlier quoted context omitted.
I hate HL7 with a passion. As for docs, the main problem is that they've spent the last century or two training snowflake workflows and vocabularies. :(
FHIR is a step in the right direction http://www.hl7.org/implement/standards/fhir/
This is a hard space to be in. I am glad ycombinator is funding startups like this. To survive in this space you need to be profitable early on and it looks like you guys are already focusing on that business wise. The challenge for your business is the various Emr/EHR systems that you have to pull data from. Some of these vendors might not be so friendly, has data lock in is a business strategy. Some systems might n…
I implemented the backend for a few early health exchanges (BHIX, NMHIC, NYCLIX, etc). Things change, my observations are a few years old, so YMMV. #1 - Players are loathe to share their data. Much integration is now occurring because of consolidation, vs interchange. #2 - Patient privacy can only be protected one of three ways. a) globally unique identifiers which are then used to hash / encryption the data (translu…
This is a hard space to be in. I am glad ycombinator is funding startups like this. To survive in this space you need to be profitable early on and it looks like you guys are already focusing on that business wise. The challenge for your business is the various Emr/EHR systems that you have to pull data from. Some of these vendors might not be so friendly, has data lock in is a business strategy. Some systems might n…
I implemented the backend for a few early health exchanges (BHIX, NMHIC, NYCLIX, etc). Things change, my observations are a few years old, so YMMV. #1 - Players are loathe to share their data. Much integration is now occurring because of consolidation, vs interchange. #2 - Patient privacy can only be protected one of three ways. a) globally unique identifiers which are then used to hash / encryption the data (translu…
Earlier quoted context omitted.
I implemented the backend for a few early health exchanges (BHIX, NMHIC, NYCLIX, etc). Things change, my observations are a few years old, so YMMV. #1 - Players are loathe to share their data. Much integration is now occurring because of consolidation, vs interchange. #2 - Patient privacy can only be protected one of three ways. a) globally unique identifiers which are then used to hash / encryption the data (translu…
Lucene works well enough for indexing textual reports (chart notes, discharge summaries, etc) but doesn't do too much for coded discrete lab results. I've found it works better to transform HL7 V2 messages into the XML encoding and then store the entire XML document into a relational database XML column. Then you can find what you need with XQuery.
Our physician facing portal didn't allow searching on lab results, e.g. show WBC below 4,000.
We'd just show graphs of a patient's lab history, with filters for types of labs, date ranges, etc.
Earlier quoted context omitted.
Eh, I'd expect somebody shilling for Epic or any of the other major vendors to sound the same way--which is exactly what I said, no more no less. I'm not going to apologize. The problem with bandying about "HIPPA [sic]" and random ISO security standards is that it only serves to dampen enthusiasm for fixing the staggeringly pervasive issues of mismanagement and technological obsolescence. Anybody can come up with a "…
You sound like a shill for startups.