3 ms·
Maybe it can be solved by prepending "ID:" for exports, and removing it on import. It could be proposed as a convention for all HC software companies.
by TacoSteemers 6y ago
Maybe it can be solved by prepending "ID:" for exports, and removing it on import.
It could be proposed as a convention for all HC software companies.
- altacc 6y agoIntroducing standards across many companies is incredibly difficult but your main problem is that a lot of healthcare IT systems are very old and not actively maintained, they're essentially on life support. So changing the format of a file, or requiring new import cleaning, is going to break integrations and data sharing in many places. Basically it'd create far more problems than it's attempting to solve.
- TacoSteemers 6y agoThat is understandable. I guess it depends on which country and which specific part of healthcare you are active in. In the 'care' domain in the Netherlands I also see that some of our integrations are one-off, but the most important ones do have industry wide standardization that receives updates based on law.
- IanCal 6y agoAlthough make sure to not use that for the first column heading, an uppercase I will make excel think it's a SYLK file and then refuse to open it.
- TacoSteemers 6y agoGood catch! The Wikipedia page confirms it. Nothing in software development is as straightforward as we might hope. https://en.wikipedia.org/wiki/Symbolic_Link_(SYLK) https://en.wikipedia.org/wiki/Symbolic_Link_(SYLK)