J P Systems, Inc

Transcription

1 J P Systems, Inc info@jpsys.com

2 Requirements Analysis IT Architecture Data Architecture Business Architecture Clinical Terminologies Standards Development Healthcare IT Strategy Interoperability Planning

3 Founded in 1983, J P Systems provides Healthcare IT consulting services including enterprise architecture. We specialize in data standards, medical terminologies and interoperability planning. Additional resources and Subject Matter Experts are added to your team based on your needs. Our personnel are active with standards development organizations such as HL7, OMG, LOINC, X12 and IHTSDO. We are the lead modelers for the Federal Health Information Model effort led by HHS ONC. We are experienced in VA and DoD VLER interoperability consulting. We perform: o o o o o o o o Requirements Analysis for Healthcare Data Exchange Interoperability Studies & Analysis Data and Process Modeling in UML Data Standards Development (HL7) Medical Terminology Mapping and Standardization Medical Informatics Shareholder and Community Engagement Software Tools for Healthcare IT Architectural Support

4 Requirements Analysis Enterprise Architecture 1. Define SOA Common Services (e.g. Verify Patient Identification) 2. Data Exchange Planning (E2E and G2E) Business Architecture 1. Business and Process Analysis 2. Define Business Logic 3. Stakeholder Engagement 4. Functional Gap Analysis Information Architecture 1. Data and Process Models 2. Healthcare IT Domains: see 3. Bind models to common terminologies: LOINC, SNOMED for interoperability Healthcare Data Standards Development for Interoperability 1. Standards Development 2. Standards Alignment and Gap Analysis 3. HIT Tooling for standards development 4. Implementation Guide Development

5 We help to get you and your trading partners on the same page - each with their own flavor of data. Each partner needs a data model Then using XML tools, model to model transformations are performed by MDHT The result is data flow between two organizations.

6 Model Driven Architecture and the tool MDHT Allows data to be exchanged between enterprises via standardized XML schemas from canonical information models. We can export NIEM artifacts from models.

7 o o Information Architecture is the analysis and design of the data used in information systems. o Modeling semantics and reference knowledge common to a wide range of artifacts o Leveraging the semantics to ensure consistency across models/artifacts o Using the same semantics as a basis for logical and physical database model generation, software component and service generation, rule development (e.g., in production rule-based systems), etc. o Logical consistency, validation, and reuse The proper set of architectural tools enables information flow and planning for interoperability within an enterprise and with its trading partners.

8 Information Architecture is the art and science of understanding the objectives of information in the context of the intended audience. It's the high level description of business information and communication and enables the translation of business perspectives to/from IT. Information Architecture relates the Business Architecture to Information Technology. Business Strategy and Information Architecture are closely related. Information Architecture enables the existing Business Strategy and Information Architecture fosters new Business Strategies

9 Ms. Mulrooney is the President and founder of J P Systems, Inc. She has 35 years of business and technical consulting experience. She is highly experienced in data architecture, software development, business process analysis, business logic and the design of Enterprise IT systems. Skills include all phases of project development from feasibility studies to requirements analysis, and system design. She excels in difficult multi-stakeholder enterprise environments while maintaining excellent client relations. She is the author of ww.healthcareitinteroperability.com. She has been an IT and business consultant to over a 100 companies for J P Systems since 1983 including the following industries and agencies: Healthcare, Defense, TV and Broadcasting, Transportation, Financial, Dod Secretary of Defense, Navy, Air Force, and Army. She oversees all the company departments including contracts, finance, sales, marketing and performs other CEO functions for J P Systems. Ms. Mulrooney founded J P Systems in She designs and develops websites, graphics and manages the J P Systems social media streams. She develops the companies' business strategies, oversees technical progress of all contracts and actively monitors the finances. She sits on the board of Open Health Tools and has provided financial and technical guidance along with process improvements and revenue stream improvements.

10 Mr. Mulrooney, Vice President, has over 26 years of software design and development experience, of which the past 15 years have concentrated on Health IT and 9 years on Enterprise Architecture. Mr. Mulrooney currently serves as a Standards Architect for the U.S. Veterans Health Administration under the auspices of the Chief Health Informatics Officer. In this capacity, he is the Lead Modeler for the Federal Health Information Model (FHIMS.org), which is a logical information model which, under the auspices of the Federal Health Architecture, is intended to guide the information exchange requirements and Information Architectures of the partner federal agencies. Mr. Mulrooney is experienced in Enterprise Architecture, RM/ODP, Zachman Framework, the Federal Enterprise Architecture (FEA) and Service Oriented Architecture for healthcare. Within VHA, he has served as an advisor to multiple reengineering projects to provide guidance regarding the enterprise s architectural initiatives and interoperability standards. He is also experienced in the full system development life cycle, USDP, RUP, OOA, OOD, UML and ER modeling, EDI, database management systems, and business process reengineering. He has been a consultant on two VA T4 efforts: VLER Interoperability and VistA Evolution.

11 Dr. Tim Cromwell has over 30 years of Healthcare IT experience in the VHA. He is a Registered Nurse with an earned doctorate in Nursing. He is an experienced Project and Program Manager and a subject matter expert in the VHA VLER and VistA systems, Clinical Informatics, Health Information Technology, Population Health and Healthcare Transformation. Dr. Cromwell led the Line of Business for Health of the Virtual Lifetime Electronic Record project (VLER), one of the Secretary s Transformational Initiatives. Dr. Cromwell s VLER Health team delivered 11 pilot locations where VA, DoD and private sector partners exchange health information via the Nationwide Health Information Network (NwHIN). Responsibilities included managing a team of terminologists, vocabulary engineers and data architects to develop and sustain standards within VA EHR systems, and to move those systems to interoperability with the private sector. Dr. Cromwell was the VA s main POC for the VA s efforts to join the Nationwide Health Information Network (NwHIN). For the DoD / VA Interagency Program Office responsibilities included IT and Business Development, and national deployment activities for standards based health information exchange within Department of Defense and the Department of Veterans Affairs. Areas of influence included: standards development and deployment, standards based health information exchange development and deployment, health IT architecture, and analytics related to returns on investment of health IT investments. Within these two positions, Dr. Cromwell controlled lifecycle investments in excess of $100M, and directed staff whose skill sets included health informatics, medical and nursing terminologies, health IT architecture, analytics and research methodology, business analytics, as well as program management.

12 Ioana Singureanu is a CDA and healthcare standards expert, enterprise IT architect and consultant. She has seven years experience with requirements analysis with Healthcare standards development for the Veterans Healthcare Administration (VHA). She also develops data models of healthcare domains as a data architect for the Federal Health Information Model (FHIMS.org) a program for the ONC. She is a key player for the UML modeling of the Privacy and Security healthcare domain for the FHIM. o Project lead for the Health Level Seven, HL7, Development Framework (HDF), lead modeler for the HL7 Project Initiation/Approval process o HL7 co-chair positions held: Modeling and Methodology, Conformance & Guidance for Implementation/Testing (CGIT), Technical Steering Committee (TSC) member, Conformance Special Interest Group. o Developed implementation guides using the fast-track process developed by VHA: IHE Patient Care Device Technical Framework - Pulse Oximetry Integration Supplement Detailed Clinical Models for Medical Devices Domain Analysis Model V3DAM_DCM4MEDDEV_R1_I2_2014SEP Privacy Consent Directive, DSTU and Normative CDAR2_IG_CONSENTDIR_R1_N2_2014SEP, Data Segmentation for Privacy Implementation Guides (CDA, NwHIN Direct, NwHIN Exchange) HL7_IG_DS4P_R1_CH1_CONTENT_N1_2013SEP, HL7_IG_DS4P_R1_CH2_DIRECT_N1_2013SEP, HL7_IG_DS4P_R1_CH3_EXCHANGE_N1_2013SEP As a member of the Standards and Community Architecture team and as an active HL7 member (Technical Steering Committee member, co-chair of Modeling and Methodology), developed a healthcare methodology and tooling approach based on standard Object Management Groups Unified Modeling Language (UML) 2.1 and other standardbased tools. Lead the effort to specify and issue a draft methodology specification: Healthcare Development Framework (HDF) for use across healthcare standard development organizations. M.S. Computer Science (Major in Database Management Systems, Minor in Internet and Web Systems) June University of Massachusetts, Lowell B.S. Electrical Engineering with Minor in Computers-Mathematics. December University of Massachusetts, Lowell, Summa Cum Laude (College of Engineering valedictorian).

13 Jay Lyle is a Interoperability consultant, Business Architect, Healthcare IT Medical Terminologist and Project Manager. He is currently a consultant on the VHA VLER Interoperability T4 project. In support of the Federal Health Architecture, Mr. Lyle supports the development of the Federal Health Terminology Model. This includes overseeing the creation of value sets in CDC s PHIN VADs, and the linkage of those value sets to the Federal Health Information Model in support of HHS ONC. This effort involves coordination of terminology experts from multiple partner agencies. In support of Veterans Health Administration s Standards and Interoperability program, Mr. Lyle provides project management, business analysis, data modeling, healthcare terminology and informatics expertise to Health Terminology Standards related projects. He supports VA Terminology goals at Standards Development Organizations such as HL7 and inter-agency initiatives such as the VA-DOD integrated Electronic Health Record (iehr) and Federal Health Architecture. His program management advice, planning ability, communication skills and clear thinking is highly valued by our clients.

14 Standards and Terminology Development J P Systems is active in the development of international Healthcare IT standards for: Data standards development Health Level 7: ver. 2, 3, CDA and FHIR Terminology standards MED-RT, SNOMED-CT Clinical Standards LOINC Prescription Processing Standards - NCPDP ICD-10 is both a terminology and a standard HL7 CDA is file oriented, data persists unlike a message HL7 FHIR is resource oriented, has transport and data structures Clinical Terminology Modeling

15 Standard Reference Clinical Terminologies Clinical Terminology Modeling using Apelon s DTS and IHTSDO workbench Structures For Clinical Decision Support SNOMED CT updates for your organization Monitoring of SDOs Standards Development HL7 Ver. 2. Use Terminology for HL7 Ver 3. Standards Development and Use Terminology for HL7 FHIR Standards Development and Use HL7 CDA Standards Development and Use Development of Concepts and Terms

16 The Standards Development Cycle Standards Development Cycle within a Standards Development Organization (SDO) 1, New requirements proposed SDO Work Group 2. Standard modeled in UML by work group Developers write software to implement standard, new requirements arise Standards Ballot : SDO membership votes & comments 3. SDO members vote Various entities develop constraints / directions for the standard SDO Publishes standard 4. Standard approved

17 Standards Development You may benefit from creating a Implementation Guide for Clinical Document Architecture (CDA ver. 3). J P Systems develops Implementation Guides for CDAs. The HL7 Structured Documents Work Group defines the CDA characteristics and structure. The characteristics are: 1) Persistence, 2) Stewardship, 3) Potential for authentication, 4) Context, 5) Wholeness and 6) Human readability. 2) HL7 v. 3 messages are not persistent, CDA files are. A CDA file has a header, main body (text, XML or a pointer to a document). CDA tags are defined by the HL7 Reference Information Model (RIM) and use standard controlled vocabulary (e.g. LOINC). Common examples include: Discharge Summary, Imaging Report, Admission & Physical, Pathology or other Test Result Report The Continuity of Care document (CCD) specification is a constraint on the HL7 (CDA) standard, meaning it is a specific type of CDA for a specific purpose.

18 Open Source Tooling for Model Driven Architecture Model Driven Health Tools (MDHT) is Used for: Model Driven Code Generation - Use the generated API (for creating / updating documents) Conformance/Validation Tools -Validate existing xml documents Generate Documentation from models - Create Implementation/ User Guides in XHTML, PDF, Other formats Extend / Constrain the existing models - Create new models from existing base models like Create new models For project files and more see:

19 HCP: Dr. A s Office HCP: Hospital X HCP: Dr. B s Office submitcardvalidationrequest(" <PatientID= 5678/> <HICcompanyName= ABC Insurance/> <GroupID=100957/> ") Web Service Communication Layer Logging of Persistent Transactions Cloud HIC: Adjudication Service HIC: Insurance Eligibility Service HIC: Insurance Service Master Transaction database CDA= Clinical Document Architecture EHR= Electronic Health Record ESB= Enterprise Service Bus HL7= Health Level Seven NCPDP= Natl. Council of Prescription Drug Programs X12= Accredited Standards Committee X12 <statuscoverage>... <status=active/> <- Approved. <EligibilityObservation GroupID= enddate=09/2013 PatientID= 5678 coveragetype = medical deductible = = XXXXXX/>

20 HCP: Dr. A s Office HCP: Hospital X Client submitclaim(" <Patient ID=1234/> <Procedure=abc/> <Diagnosis=xyz/> ") ICD10-AM code HIC #1 Insurance Eligibility Service Web Service Communication Layer HIC #1 Insurance Adjudication Service Pharmacy A TPA # 1 Insurance Eligibility Service HL7 v3, NCPDP, X12, CDA, etc. Transaction database CDA=Clinical Document Architecture EHR=Electronic Health Record ESB=Enterprise Service Bus HL7=Health Level Seven NCPDP=Natl. Council of Prescription Drug Programs X12=Accredited Standards Committee X12 <statusclaim>... <status=approved/> <- Approved. <EligibilityObservation maxbenefitlimit= coveragetype = Dental deductions = 100 exclusions = XXXXXX/>

21 We have extensive experience with: Data Requirements Analysis and Information Modeling We developed 39 healthcare domain models in UML including Lab, Security and Privacy, Providers and Eligibility, see Business Logic Extensive experience with defining the needs of enterprise to enterprise (E2E) exchanges for the Veteran s Administration with 120 hospitals and 500 clinics plus private providers, DoD liaison and joint offices Business Owner & Stakeholder Engagement Experience with coordination of requirements between US Health Human Services, Office of the National Coordinator, major private providers, government agencies (e.g. Food and Drug Administration, CDC) for public health reporting.

22 Business Architecture Business Process Analysis Analyze Business Logic Develop Use Cases Information Modeling in UML

23 J P Systems Enterprise Support Planning for Stakeholder Engagement Communication Plans Facilitation of Stakeholder Meetings Governance Board Creation and Policy Definition Adoption Strategy gaining consensus and Buy In from business owners Healthcare Use Case Development, Review and Analysis Scope Limitation Consulting Planning and Architecture for Interoperability Business Logic Identify and Document Business logic