<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>floatrock</author><text>ah HL7.&lt;p&gt;&amp;gt; I hope you like XML documents, flat files, pipes and hats, SOAP, and even CORBA.&lt;p&gt;Completely true.  But that&amp;#x27;s not really the problem.  You can download an HL7 or XML-parsing library and the dirtiness of the representation is converted to JSON or whatever works for you.&lt;p&gt;The problem is API loopholes.&lt;p&gt;HL7 does a pretty fair job defining what concepts get put into which fields.  However, many implementations ignore the computer-readable fields and literally dump everything as 80-character human-readable console outputs in the &amp;quot;custom text&amp;quot; fields.  Want any structured data?  You&amp;#x27;re gonna have to write a text parser specific to the hospital&amp;#x27;s legacy console systems.&lt;p&gt;There&amp;#x27;s also a good deal of standardization over how things SHOULD be presented (ICD-9 etc), but those are ignored.  Often times physicians or pharmacists just type the drug into a free-text box.  5 different spellings of Ampicillin are the least of your worries -- it gets bad when the dosage is mixed in with the name, and it gets worse once you get into compounds or mixes.  The standard isn&amp;#x27;t the problem, its the data mapping problem for all the human-inputs.&lt;p&gt;And then you get into fun stuff where billing people use different codes than everyone else for the same drugs, procedures, admissions, etc (there&amp;#x27;s a reason billing admins are so highly paid... it&amp;#x27;s a black art where you get creative how you describe things to the insurance companies).&lt;p&gt;All of this is to say that I would love to see a RESTful, well-modelled API over HL7 messages, but the problems go far deeper than the protocol spec (and that&amp;#x27;s just for technical side of things... the politics and business threats of open APIs that the article talks about are completely true as well).  It&amp;#x27;s been a couple of years since I&amp;#x27;ve been in the space and not at all familiar with these new FHIR specs, but I wish that process all the best.  If you&amp;#x27;re looking for a real challenge, it&amp;#x27;s not picking up Clojure or whatever is the language du jour... a true challenge is doing anything in healthcare.</text><parent_chain></parent_chain></comment><story><title>The most important API you’ve never heard of</title><url>http://rockhealth.com/2015/03/important-api-youve-never-heard/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jbob2000</author><text>The one big problem I see with healthcare information is red tape. Independent developers and small shops do not have the resources to deal with lots of red tape. We saw with the recent VAT changes in Europe that it&amp;#x27;s really hard for anyone who isn&amp;#x27;t an enterprise company to deal with lots of regulation.&lt;p&gt;Before we start talking APIs, I want to know the hoops I&amp;#x27;m going to have to jump through before I even git init.</text><parent_chain></parent_chain></comment><story><title>The most important API you’ve never heard of</title><url>http://rockhealth.com/2015/03/important-api-youve-never-heard/</url></story>