Can i create a software which can store doctor prescription? I have developed a software which can store doctors prescription digitally. wondering if there would any legal complications on it. Any laws preventing that sort of software/practice in united states. the user basically would manually re-enter what is in prescription into this app.
Your basic regulatory umbrella for anything that stores, transmits or interacts with any private health information or health IT systems is Health Information Privacy | HHS.gov, as well as state authorities. There are severe penalties at the federal and state level for non-compliance and privacy breaches, and many other agencies - such as the DEA, state health departments, insurance companies - would have to be involved in testing and certification of such a App. You will simply not be able to distribute the App on Google or iTunes without their approval, and those distributors will not approve a App that has not been strictly vetted for privacy and HIPAA compliance. In order to distribute such as App - with a TOS that assures personal privacy and shields you from liability (if possible) - you will need to spend hundreds of thousands of dollars on legal representation for compliance. As an example, see ohwilleke's answer to What kind of lawyer should I seek to understand compliance requirements for processing credit cards?
The use of the icon must be specific to the function of the icon within the Microsoft software. ... is pretty specific. What you have described isn't so it is not permitted by the licence.
Can you locate your license (generally not a trivial task)? It may appear under Help-About and a click to view EULA. The EULA specifically addresses redistribution of parts of the software and number of installations you can make with a single license. They do not say what uses you make make of the software, except that &quot;You may not rent, lease, lend or provide commercial hosting services with the Software&quot;. There is no express prohibition against commercial or non-commercial political use of the product: anything not prohibited is allowed. The fact that they say nothing about the content that you create with Word means, they have declined to have a say in the matter. (I am not sure about the wording of the &quot;Educational&quot; versions of Office: those are somewhat negotiated between the institution and MS).
The words "proprietary format" are important. Are you sure the format is proprietary? If it is, then it's likely protected in which case they might have grounds to sue (but that does not mean they would definetly win). If the format is not proprietary, and so long as you don't share data which is proprietary then I believe you fine. I'm not a lawyer - but I cite GIF files as an example. They were still protected by the US and some other countries until at least the late 90s and there were various threats to open source linux companies who shared code that used the file format. I'm not aware of anything other than threats and never heard of any company being sued, let alone winning or losing. Another example that comes to mind is the RedHat ISO format. My understanding is RedHat could not stop anyone from sharing open source, but they could prevent folks from sharing the format they assembled and shared the open source. Again, I am not sure if it was ever tested in any court of law anywhere.
The idea for an app is not subject to copyright. Only the artifacts of the app itself (sourcecode, images, texts, sounds, etc.) can be. So if one only copies the idea and creates their own version of all the other assets, then they are not violating copyright. However, in some cases, ideas can be subject to patents. But patents on software are tricky. First of all, only new ideas can be patented. When a supposed new idea was already published before, then that's called &quot;prior art&quot; and you can not patent it. Then getting a patent means a lot of investment in money and time (which is very different from copyright which you get automatically the moment you make something copyright-worthy). So not everything that could theoretically be patented gets patented. And then, many jurisdictions do not recognize software patents at all, and those which do have different limits on what is and is not patentable when it comes to software. This means patents are rarely a concern when copying the app idea of someone else, but not never. And another possible concern is the third pillar of intellectual property: Trademarks. This protects the name of the app. Trademark law oversimplified forbids to create a competing product with a name which might confuse customers. So if you created StevesSuperCoolAppForCoolPeople and I create StevesSuperCoolAppForCoolPeople - Simplified Edition, then I would be violating your trademark, because my product name sounds as if it was your product, when it is in fact an unrelated product with a similar purpose.
You get a lab to test it You should clearly document the chain of custody (ideally with photos) from the unopened packaging to the lab. Any decent sized city will have several labs with the capability to tell you what’s in a pill and provide an expert report.
Depending on your jurisdiction, such lists may be protected, but not by copyright. For example, in Germany there was a court decision that scanning all the country’s phone books and selling them on CD constituted “unfair competition” and was illegal, while hiring 1000 typists who would manually type in all this information would not be. Databases are protected in many jurisdictions, and a list of the 1000 most commonly used English words could reasonably be called a database.
I cannot speak for civil law systems (Germany) but in Common Law (UK, USA) systems the law looks at substance rather than form. So: Am I allowed to undo the word-wrapping of all the texts and unindent them, as well as performing a new word-wrap on them? Yes Do I have to make sure that it is readable for everyone on every device, and do I have to make sure that accessibility interfaces are used (e.g. for blind persons, which aren't even the target group of my software)? If they are licences (rather than contracts) they must simply be available; this does not mean universally available. Do I have to make sure, that if my application wouldn't even start correctly on a device, that the user is able to start the application in an impossible, absurd, magic or religious way to ensure that he can read the legal texts or is it enough to state it on the website then? It depends if you want the licences to be enforceable by you on the users or if you are simply complying with your disclosure obligations. See What if the user disagreed with the Terms of Service, but still registered on a website?. Do I have to make sure that the rendering of the licenses/privacy policy/impressum is performant (e.g. text rendering and refresh after scrolling takes less than a second)? I already have to include two external libraries with my software to display the texts, otherwise it would not be possible to display texts at all. No - make them wait if you want.