-
Notifications
You must be signed in to change notification settings - Fork 0
Home
The UI mockups are currently being hosted in myBalsamiq. http://mercyproject.mybalsamiq.com/projects/mercy
The old whiteboard picture is here : http://i.imgur.com/w65Wcgi.jpg
The FDA maintains a very nice database of all drugs licensed in the United States. It is updated every monday, and they even document the file format. AWESOME.
http://www.fda.gov/Drugs/InformationOnDrugs/ucm142438.htm
DrugBank also has a very good database of drug information, complete with information on what each drug is used to treat. The FDA database is more official, but it lacks this contextual information. The DrugBank data is legit, even if the website does look janky.
http://www.drugbank.ca/downloads
Each state has its own pharmacy registration & verification system; I reached out to the NABP to see if there was any service that could simplify it to verify pharmacies for all 50 states:
###NABP Recommendations
I got a reply from NABP!
Good Afternoon Andrew,
Thank you for contacting the National Association of Boards of Pharmacy® (NABP®). NABP is the independent, international, and impartial association that assists its member boards and jurisdictions in developing, implementing, and enforcing uniform standards for the purpose of protecting the public health.
We can suggest several resources for verifying the licensure status of pharmacies and pharmacists. NABP’s Pharmacist and Pharmacy Achievement and Disciplinehttp://www.nabp.net/programs/member-services/ppad (PPAD) database provides online reports of information about pharmacists, interns, technicians, pharmacies, and other entities licensed by state boards of pharmacy, including disciplinary information on persons or entities. Information in the PPAD database is supplied by the state boards of pharmacy, and there may be variation in how frequently the boards update this information with NABP. For the most up-to-date information regarding licensure status and disciplinary actions against pharmacies and pharmacists, we recommend that you contact the state boards of pharmacyhttp://www.nabp.net/boards-of-pharmacy/ individually. Many states offer an online license look-up feature that allows the user to check the licensure status of a pharmacy or pharmacist.
In the case of Internet pharmacies, you may also wish to check to see if the entity has received Verified Internet Pharmacy Practice Sites (VIPPS)http://www.nabp.net/programs/accreditation/vipps or Veterinary-Verified Internet Pharmacy Practice Sites (Vet-VIPPS)http://www.nabp.net/programs/accreditation/vet-vipps accreditation from NABP. VIPPS or Vet-VIPPS accreditation is a strong indicator of an Internet pharmacy’s compliance with state and federal laws and regulations and NABP's criteria.
In regards to your second question below, states license both pharmacies and pharmacists. Along with verifying the licensure and disciplinary status of a particular pharmacy, you may wish to at least verify the licensure of the pharmacist-in-charge for a particular facility.
We hope that you find this information helpful.
Regards,
Professional Affairs Department
We will be using PostgreSQL for this project because all of our data will be very well formatted, and we can make SQL ridiculously fast with this kind of data. Also because postgres has fantastic support for high availability and replication, and since Amazon RDS supports PostgreSQL natively, that's one less bit of infrastructure for us to keep up in production.
The below bits are outdated and were added here before Amazon announced PostgreSQL RDS at re:Invent - please update this section?
http://www.postgresql.org/docs/9.1/static/high-availability.html
Regardless there are apparently some best practices for using Postgres in AWS, even without RDS, so we should consider that. This service, if successful, will grow to large boundaries so we should consider scaling it into a provider like AWS.
http://aws.typepad.com/aws/2013/07/running-postgresql-on-aws.html
Paypal: https://developer.paypal.com/
Amazon FPS : http://aws.amazon.com/fps/#highlights1
Google Wallet : https://developers.google.com/commerce/wallet/
From someone that knows what they're talking about: "in a nutshell, the best first steps are to get a solid waiver from participants, and make sure everything is encrypted during storage and transmission ... as long as there is no personally identifiable data, you should probably be fine. but i would probably still go ahead with the waiver and encryption. You will probably still fall under a "business associate" relationship; meaning you would be on the hook for full compliance".
http://www.hhs.gov/ocr/privacy/hipaa/understanding/coveredentities/businessassociates.html
"Also, you'll probably need to use FIPS 140-2 compliant encryption, which means AES and SHA-256 for hashing"
So, it looks like we'll need to make our instances compliant by making all of the traffic encrypted (I already plan to do this inside of an Amazon VPC and all traffic across SSL anyway), and encrypting the data at rest. Unfortunately the only Amazon RDS that supports TDE/At-Rest-Encryption is Sql Server currently, so we might have to roll our own PostgreSQL AMIs and not use RDS. Blargh.
Also, we might reach out to the folks at NewCropRx and DrFirst; apparently they provide the vast majority of the e-prescription services in the country, and may have some insight/advice for us. I have some names.