Digital Prescription : Standard for Cloud Computing Platform

A Universal Digital Prescription Standard is a Real Need for Work on Cloud Computing Platforms as Chances of NSA Spyware Activities is More. Currently except 3D Medical Data, there is no consistent IEEE Standard. IEEE Standard has the advantage to using the Standard as if like we use Free Software, although there can limitations added by the Group or Individual can bear usage of Closed Source software. RFC has no issue, but limitation of RFC is usage with practically working Protocols. As with revelations by Edward Snowden has clearly shown the NSA Spyware Activities and Associated Possible Relationship With Security Vulnerabilities Like Heartbleed, Shellshocked Shellshock Bash Vulnerability and Father of Linus Torvalds practically agreed about the approach of Spyware team to add deliberate backdoor to SELinux, recalling Snowden’s statement :

I believe in the principle declared at Nuremberg in 1945: “Individuals have international duties which transcend the national obligations of obedience. Therefore individual citizens have the duty to violate domestic laws to prevent crimes against peace and humanity from occurring.”

In other words, except the Public Servants, none should use any Digital Prescription or Electronic Prescription provided by any Governmental System or non-Free Service Providers (non-Free means do not obey the ruleset by Free Software Foundation) to protect own and patients’ personal Data Theft. Cloud Computing Platform, here only represents a low cost or free alternative to co-location server. Cloud Computing Platform can mean any Cloud Computing Service Model, however, usage of Private Cloud can be thought for robust security.

Digital Prescription : Still No Standard for Cloud Computing Platform

As the Author and This Website are publishing the idea implementing an Open Standard Digital Prescription with GNU GPL 3.0 License, except without prior information to Dr. Richard M. Stallman as Third Party, none should add a Closed Source Software or Software with Dubious, Dual License. The Software representing the practical usage of the rulesets.

Digital Prescription : Draft for Standard and Software

For practical usage, compatibility with existing command line tools is more important than developing a GUI based program as a Prototype application maintaining the Standard. As US Government has practically failed to provide any true security (recalling Rofecoxib and Human Deaths), Free Software, Gratis or for Fee, should itself override any fair intention. There is, at least one, so called certified, cloud-based e-prescription platform available from Haymarket Media Group, a privately owned media company headquartered in London, United Kingdom. Our proposed solution has no relationship with the said model. Taking the conventional definition of prescription (â„ž), which describes a prescription to be a health-care program implemented by a physician or other qualified practitioner in the form of instructions that govern the plan of care for an individual patient. Here the word Program was used to mean “A set of structured activities” not a Software Program.
 

Re-inventing the wheel is unnecessary. The basic rules for the Standard should essentially follow the old, traditional prescription, which will also help the digital conversion of the old prescriptions to digital format with some compatibility. Practical guidelines should be :

1. Using a universally readable digital document on any GNU Linux Computer
2. Corresponding Software Should Have a Command Line Interface and Hitting W should reveal the GNU GPL 3.0 License. The key W is taken as an example on GNU GPL 3.0 License.
3. Ideally the document should bear no extension but readable with any Text Editor including GNU Nano, Vi from command line.
4. MySQL so far, is the most commonly used Database software to ordinary individual. It can be used for saving data. MongoDB is better alternative and has practically usable extensions extending the RESTful API.
5. “the document” on point 3 means Digital Prescription
6. The document should optionally use GNUPG to secure the data
7. Although usage of GNUPG to secure the data can make the document fully unreadable (locked in) in case of loss of Key, it is ideal to prevent data theft
8. The document should allow to use normal cURL, wget etc. basic tools.
9. Upon running the standard curl -I <location>command against the document, while publicly being accessible (publicly means within a network NOT over the Public INTERNET) should return proper headers.
10. The document and Software should be compatible to all the Free Softwares which use GNU GPL 3.0 License to embed any document which has an existing or future IEEE Standard – this is important for including the 3D medical files.
11. Ideally the document should block using any close source software
12. If revision or versioning is used, it should be usable with any currently used versioning software which use GNU GPL 3.0 License. Revisions must be available with time stamp.

Everyone has a terminal since the past 4 decades, so this Standard of Digital Prescription should not create any compatibility issue. The description actually defines a typical robust Text Editor where the output is universally readable, user can add own method of naming the files. Hard copy, ideally should print the text on any standard printer with own real life prescription – that is the Hard Copy. Printing, in essence, will not print the header and footer – which is included on own real life prescription with proper security to prevent forgery.