1. Implementing and Supporting the Oregon Public Health Information Network Messaging System (PHINMS) One developer’s perspective. John E. McAdams Development Team Lead State of Oregon Department of Human Services Public Health Division www.oregon.gov/DHS/ph

2. Please, everyone, raise your hands and keep them up if: You’re responsible for building or installing software at your organization. You generally get complete requirements prior to building or installing this software. Your projects are, by and large, fully funded. Your projects are usually on time and on budget. Your project’s requirements seldom change.

3. Photo courtesy of http://www.flickr.com/photos/cleverboy68/465591914/ VISION

4. Photo courtesy of http://www.flickr.com/photos/tmh9/1014165892/ BUDGET

5. Today’s Topics… What Oregon identified as PHINMS implementation issues. Flexibility in choosing your PHINMS implementation. How Oregon implemented PHINMS. Questions and answers.

6. So, how did Oregon Implement PHINMS & …insure we can serve all our partners? …guarantee we can scale when needed? …respect our partner’s budgets? …be responsive to change? …support other strategic PHIN initiatives?

7. Serving all of our partners: Some large, but many are small. Some with budget, but most have limited funds. Many without dedicated IT resources All work within the same network infrastructure.

8. Respecting budgets: Be creative. Seek out collaborative opportunities. Be flexible.

9. Being responsive to change: Process for adding a message stream. Process for changing a message stream. Process for problem resolution. Annual process for certificate renewal.

10. Support other PHIN initiatives: PHIN certification PHIN directory exchange Case notification (Lead, TB, Varicella, Hepatitis) Lab reporting

11. Scalability: N Tier implementation scales easily with additional hardware. Modify and test your changes prior to introducing them into production. Keep areas of responsibility clear and separate. Profile your system performance when you perceive a bottleneck.

12. Our Architecture: DHS Users Network (Novell eDirectory) DMZ Web / Proxy Server PHINMS Server DB Server Firewalls SDC Secure Network (MS Active Directory) Internet To/From CDC/External Partners

13. Option 1 DHS Users Network (Novell eDirectory) DMZ Web / Proxy Server DB Server Firewalls Internet Send and receive via the database SendingReceiving SQL InsertSQL Select PHINMS Server State Data Center (SDC) Secure Network (MS Active Directory)

14. DHS Users Network (Novell eDirectory) DMZ Web / Proxy Server DB Server Firewalls Internet Option 2 Send via SFTP, receive directly from database SendingReceiving SQL Select PHINMS Server SDC Secure Network (MS Active Directory) SFTP

15. DHS Users Network (Novell eDirectory) DMZ Web / Proxy Server DB Server Firewalls SDC Secure Network (MS Active Directory) Internet Option 3 Send and receive via private folders SendingReceiving PHINMS Server

16. DHS Users Network (Novell eDirectory) DMZ Web / Proxy Server DB Server Firewalls SDC Secure Network (MS Active Directory) Internet Option 4 Send and receiving using an Application Programming Interface. SendingReceiving Partner System API PHINMS Server

17. DHS Users Network (Novell eDirectory) DMZ Web / Proxy Server DB Server Firewalls SDC Secure Network (MS Active Directory) Internet Option 5 Send and receiving using a web service SendingReceiving Partner System Web Service PHINMS Server

18. DHS Users Network (Novell eDirectory) DMZ Web / Proxy Server DB Server Firewalls SDC Secure Network (MS Active Directory) Internet Option 6 Send and receive via SFTP SendingReceiving PHINMS Server Partner System SFTP

19. Summary: Communicate with your partners. Facilitate gathering consensus on choosing one of these options. Talk to your infrastructure folks. Formulate and evaluate the pros and cons of all of your options. Present those options to your partners.

20. Acknowledgements: AMS-PH Developers. Oregon OIS management. Oregon central PHINMS workgroup. CDC PHINMS teams. Acute and communicable disease partners. Immunization partners. Oregon EPHT partners. Oregon State Data Center.

21. Useful Resources: PHINMS Product Web Site http://www.cdc.gov/phin/phinms PHINMS User’s Group Meeting 4 th Thursday Monthly, 1-2pm ET PHINMS User’s Group Forum http://team.cdc.gov For access, email: tjones4@cdc.gov tjones4@cdc.gov

22. Questions? John E. McAdams john.mcadams@state.or.us