I am working on a search engine to search for Internet-based codes for my software launch, which will allow users to search for ICD-9 medical codes (and corresponding ICD-10, clinical codes) used in medical diagnoses and medical billing.
The problem with creating search data files is that the Disease Control Center only frees the file in RTF Rich Text Format files, which are suitable for printing and reading, but difficult to programmatically load into a database.
There are several existing ICD-9 search engines, and I know that dozens of other programming teams have solved this problem for every crappy practice management system on the market. But due to the nature of the field, things are very closed, and no one has published their data publicly or released code to analyze these .rtf files or the data repository. The reason is that each company sees X the number of hours that they put into parsing these files into database data, as a barrier to entry for competitors.
What other types of specific programming problems arise because programmers constantly continue to solve problems, and how do you break the vicious circle and are the first person to release data or a solution? Or is it worth it to break this cycle and free your decision and make it easier for competitors? How do you profit or profit from the release of a solution to such a problem?
Miken source
share