Click here to Skip to main content
15,889,096 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more: , +
I work on developing EMR software and we are working towards meeting Meaningful Use Stage 2. Part of the requirements entail adding functionality to send messages and documents that adhere to the Direct Standard specifications (which is a fancy way of saying 'e-mail' but with specific rules about how to secure and send it).

I found an API developed by those at DirectProject.org (http://wiki.directproject.org/[^]) but I am having little success when it comes to actually implementing it. I have no experience with Certificates, Anchors, SMTP, S/MIME, etc. I have spent the last five or so days sifting through the API and Googling differing things and I understand a bit more but not enough to implement it.

Here is the Documentation for the API: http://api.nhindirect.org/Help/Index.html[^]

If someone has the time or is interested in helping, here are the steps that I need to be able to do with this API:

To Send:
1. Locate destination address and certificate
2. S/MIME sign w/ private key
3. S/MIME encrypt w/ destination certificate
4. Send

To Receive:
1. Receive
2. S/MIME decrypt w/ private key
3. S/MIME verify w/ source certificate

Section D in this link (http://wiki.directproject.org/Deployment+Models[^]) shows a diagram of these steps.

Any and all help is much appreciated!

Thanks!
Posted
Comments
Richard MacCutchan 8-Aug-13 13:07pm    
The sensible option would be to either read the documentation or ask the people at Direct Project.
Bernhard Hiller 9-Aug-13 2:58am    
Can you send and receive email in plain text? That's the point to start from. Encryption/decryption comes later on.
KarstenK 15-Aug-13 4:46am    
it looks like you need some professional help for your "work". :-O

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900