None that I know of. And I believe this is because.. I don't think the solution (implied by the question) is a good solution/proposal.
Not only because hashing function may have collisions (even if it has a very low probability, the impact would be major, so why should we add such a risk ?) but also because you have another problem prior to hashing: unless you solve something that has not yet been fully solved (i.e. semantic interoperability), in a med profile you can -for instance- find/formulate the very same medical concept in several different ways (i.e. different text sequences may mean the same thing/medical concept) so in those cases you would get different hashes referring to the same concept (!) . How would you manage that ? Will you be able to map all those different hashes to the same medical concept ? (type of allergy or whatever). How would you say that two hashes really mean two different things.. and which things should they be ?. I believe you won't be able to predict all the possible different ways in our language we could express the same concept and the resulting hashing values will be severely flowed in semantic terms.
Even if you choose to use the best terminologies and controlled vocabularies or coded information to be used in the med profile, they will still need continued maintenance and revision over time (because of versioning etc. e.g. aliases, new concept in, deprecated concepts out etc.) all things that will impact severly on the effectiveness and reliability of your "decision support system" based on concepts hided by hashes values. So I don't think it is a good idea to hide a medical concept behind hashes and taking decisions based only on the hashes values.
Besides, if I authorize my Doctor to access my medical record, I want him to see it very clearly what my allergy is in terms he can understand. Can you imagine your Doctor watching hashing values supposed to be mapped vs. some medical coded information having absolutely no way to really verify the real concept that may be behind ? Not a good idea. You want compression ? Use compression algorythms. You want security ? User encryption with two ways functions and authentication infrastructure etc. (keep in mind that hashing is a "one-way" function). Just keep using hashing for those things we use them today (to index, retrieve items more efficiently, for digital signatures etc.) NOT to hide/store medical concepts. I would not innovate this way. But may be I am wrong. Is there a better answer to this?