390 likes | 569 Views
Pennsylvania Department of Health Enterprise Services. PA Department of Health Enterprise Reporting Gateway Services and Enterprise Data Warehouse Initiative. PA-NEDSS/ELR History. PA-NEDSS live in 2003 PA-ELR Web Service designed as a tool for PA-NEDSS in 2005
E N D
Pennsylvania Department of Health Enterprise Services PA Department of Health Enterprise Reporting Gateway Services and Enterprise Data Warehouse Initiative
PA-NEDSS/ELR History • PA-NEDSS live in 2003 • PA-ELR Web Service designed as a tool for PA-NEDSS in 2005 • ELR was built tightly coupled to PA-NEDSS • Shared Database • ELR utilizes the PA-NEDSS Security Model • Shared Web and Application Servers • ELR functionalities Embedded in PA-NEDSS • Batch Status Page • Manual Upload Page
Emerging HIE in Pennsylvania • The emergence of HIE technology in Pennsylvania is a driving factor in the de-coupling of PA-ELR and PA-NEDSS • Pennsylvania has a network of networks HIE model • The P3N is a thin layer at the Commonwealth level that allows regional HIOs to connect to each other. • P3N also allows for providers and hospitals to report to the Commonwealth including meeting public health reporting requirements for Meaningful Use • ELR/NEDSS was identified as the pilot for reporting to the Commonwealth • Current NEDSS/ELR functionality would not support reporting through the HIE Network
PA-ELR to Enterprise Reporting Gateway Service (ERS) • “De-coupling” of PA-ELR and PA-NEDSS • Migrate all ELR related components to ERS specific servers. • Migrate all NEDSS related components to NEDSS Specific servers • Create a new SQL Server Database for the ERS • Creation of a new Enterprise Web Service • Creation of an Authentication Web Service • Modification of old ELR web service (now NEDSS web service) • Completion of PAWS 2.0 • Creation of Enterprise Reporting Service Portal
ERS Key Components • PAWS 2.0 • Enterprise Authentication Service • New Enterprise Reporting Web Service • Orion Health’s Rhapsody Integration Engine • New Web Portal • Message Testing and Validation Service
Rhapsody • Replaced existing directory communication points with web services • Generation and return of HL7 formatted acknowledgements • Provides routing services • Non NEDSS public health systems that integrate into ERS will determine what if any business logic is maintained in Rhapsody • Existing NEDSS Business Logic remains in Rhapsody
PAWS 2.0 and Enterprise Web Services • PA-ELR Automated Upload Windows Service (PAWS 2.0) • Improved GUI; menus and data fields • Client side application • Supports multiple environments • Supports transport to multiple destination applications • Enterprise Authentication Service • Authenticates user against destination systems AD. • Allows user to change password via PAWS • Enterprise Web Service • Built using Microsoft Windows Communication Foundation (WCF) • Separate Endpoints configured for each client system
Web Portal • Centralized location for Public Health Reporting information • Links to Implementation Guides • Links to external resources • Frequently Asked Questions • Provides manual file upload functionality • Replaces current PA-NEDSS functionality • Functionality can be extended to other client applications • Provides a self service test tool
Testing Tool • Currently only supports ELR • Can be extended to Other Public Health Programs. • Test tool is customized to meet your State’s exact implementation guide. • Utilizes the Rhapsody Integration Engine • Exposes Rhapsody as a web service • Utilizes customized message definition file • Create custom validation tables • Utilize advanced validations • Utilizes a mapper to customize the final message displayed • Provides custom error language utilizing look-up tables. • Allows you to only display the errors that you desire to display.
Next Steps • Develop a Security Token Service (STS) • Utilize Microsoft Windows Identity Foundation (WIF) • Claims Based security model • Replaces the current Enterprise Authentication Service • Allows for Single Sign On to DOH applications • Develop Dashboard Functionality on the ERS web portal
Contact Information Mark Dittman – PA-ELR Project Manager mdittman@pa.gov Bill Pugh – NEDSS Project Manager wpugh@pa.gov
“Architecture exists to serve people. …design is firmly rooted in the interpretation of basic human needs ...design solutions as an integrated expression of function, purpose and sensory experience conceived in a holistic fashion to make perfect sense. How can this design best serve the people who will use it? How will it improve their lives, enhance the lives of their neighbors, serve their community and generations to come? …the focus remains, always, on people.” John C. Portman Architectural Firm - Atlanta1
Informatics Architecture – Outside and Inside • What you build will be used in ways that you did not intend Hollerith Card3 Atlanta Marriot Marquis4 Atlanta Marriot Marquis2
Informatics Architecture – Making a Star5in the Test Kitchen6 • Template 1 - Know your Ingredients • Eliminate the ‘white powder’ confusion in the kitchen • Example of what we found with a ‘contact’ • Data is an asset – treat it as such Some day, on the corporate balance sheet, there will be an entry which reads, 'Information'; for in most cases, the information is more valuable than the hardware which processes it.~ Grace Hopper
Informatics Architecture – Making a Star5 in the Test Kitchen6 • Template 2 – Mise en place7 • Prepare all of your ingredients ahead of time • Data conformance • A place for everything and everything in its place
Informatics Architecture – Making a Star5 in the Test Kitchen6 • Template 3 – Plan the recipe • Apply the attributes and facts of your ingredients • Conceptual Data modeling
Informatics Architecture – Making a Star5 in the test Kitchen6 • Template 4 – Implement the recipe • Use the outputs of the first 3 templates to build the architecture • Ingredients – Data Identification and Definition • Preparation – Data Conformance • Recipe development – Data Modeling
Next Steps • Build menus around the recipes • Similar process, but working from the prepared information not raw data • Work with stakeholders for their expectations and requirements • Stage the menus • How should the information look and perform • Implement the menus • Develop, test and make the information available as required The future is already here — it's just not very evenly distributed. ~ William Gibson
But how can we make a meal when there are sharing issues in the village? • Ad hoc teams • Train both IT and Program Staff • Bring in targeted resources • To teach theory • To review infrastructure • To augment staff on known and owned tasks • Initiate with a ‘stone’ from a benefactor. Opportunities multiply as they are seized. ~ Sun Tzu Stone Soup by Marcia Brown8
Meta Architecture – Executive/Strategic Support • Culture Change to One Vision • Triad of Assets – Human, Data, Budget • Enterprise Governance of Assets The future is already here — it's just not very evenly distributed. ~ William Gibson
Thank you • Pennsylvania Department of Health Staff • Environmental Public HealthTracking Grant (CDC) • Epidemiological and LaboratoryCapacity Grant (CDC) • Public Health EmergencyPreparedness Grant (CDC) • National Program of Cancer Registries (CDC)
When you cut into the present the future leaks out. ~ William S. Burroughs
References • http://www.portmanusa.com/designphilosophy.php • http://en.wikipedia.org/wiki/File:Marriott-marquis-atlanta-2008.jpg • http://en.wikipedia.org/wiki/File:Punch-card-5081.jpg • http://www.portmanusa.com/project.php?name=Atlanta Marriott Marquis Hotel&projectid=5617&country=USA • http://www.kimballgroup.com/data-warehouse-business-intelligence-resources/kimball-techniques/dimensional-modeling-techniques/star-schema-olap-cube/ • http://www.kimballgroup.com/2004/01/01/data-warehouse-dining-experience/ • http://www.pbs.org/food/features/mis-en-place-the-start-to-an-easy-meal/ • ISBN 9780689878367 –Stone Soup by Marcia Brown- picture from http://www.amazon.com/Stone-Soup-Aladdin-Picture-Books/dp/0689711034