requirements for epidemic information management farrukh najmi xml standards architect sun...
TRANSCRIPT
![Page 1: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/1.jpg)
Requirements for Epidemic Information Management
Farrukh Najmi XML Standards Architect Sun Microsystems
![Page 2: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/2.jpg)
About the Speaker
● XML Standards Architect, Sun– Focused on content management
● Previously, architect of HP CareVue Clinical Information System
● Co-author and editor, ebXML Registry
● Co-founder, freebxml.org● Lead Architect, freebXML Registry
![Page 3: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/3.jpg)
Some Basic Assumptions
● Advancing information management capabilities is the key to advancing epidemic management
● Topics covered are applicable to many other scenarios beyond epidemic management– Applies to any emergency management
scenario
![Page 4: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/4.jpg)
Agenda
● Requirements for epidemic information management
● Relevant technologies and standards
● Gap analysis, conclusions
![Page 5: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/5.jpg)
Information is Diverse
● Published literature – pubmed.com– Bio-med info databases (human
genome)
● Morbidity reports● Patient records● Live stock records● Multiple languages
![Page 6: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/6.jpg)
Information is Distributed● Hospitals and Clinics● Port of entry● Customs● Local public health
departments● National: US CDC● Farms, agri-business
![Page 7: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/7.jpg)
Need Info Sharing Across Entities
Hospitals Center for
Disease Control
Clinics
State Public
Health Dept.
Airports
SeaportsCustoms Dept.
FBI
CIAHomeland Security
Agri-busin
essAgriculture
Dept.FarmsFEMA NRC
Internet
![Page 8: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/8.jpg)
Info Management is Collaborative
● Many information authors belonging to many different autonomous entities
● Many consumers of information● Need to support workflow● Workflow must be governed by
collaborative Business Processes
![Page 9: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/9.jpg)
Info Sharing Must Be Secure● Authenticity of source● Integrity● Confidentiality● Role Based Access Control
(RBAC)● Audit trail
![Page 10: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/10.jpg)
Info Sharing Must Be Reliable● Guaranteed delivery of
messages● Quality of service
– At most once delivery– Once and only once delivery
![Page 11: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/11.jpg)
Info Sharing Must Be Timely● Asynchronous event notification
(Alerting)● Subscriptions to relevant
information● Content based selection of what is
relevant (Filtering)● Delivery of notifications via multiple
channels: email, web service invocation
![Page 12: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/12.jpg)
Need for Standard Vocabularies
● Must requirement for info sharing● Not many exist today● Need to be globally standardized● Each facet of epidemic
information needs a separate standard vocabulary
● Desirable to have a common core vocabulary across all facets
![Page 13: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/13.jpg)
Need for Vocabulary Reconciliation
● Vocabulary divergence is inevitable– Standard vocabulary is only a
foundation– Regional customization and
specialization is necessary
● Need ability to declare that two vocabulary terms are semantically equivalent
![Page 14: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/14.jpg)
Info Must Be Self Describing● Need for standard metadata● Ability to name, describe and
uniquely identify information● Ability to classify information● Ability to define semantic
relationships between information● Ability to define semantic
metadata
![Page 15: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/15.jpg)
Info Must Be Discoverable● Metadata key to enable
discovery● Need standard discovery
service● Must support ad hoc queries● Must support parameterized
stored queries
![Page 16: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/16.jpg)
Technology Standards for Epidemic Information Management
Farrukh Najmi XML Standards Architect Sun Microsystems
![Page 17: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/17.jpg)
What is ebXML?
● A modular suite of technical specifications
● Developed by OASIS and UN/CEFACT
● Enables enterprises to communicate with each using open standards
![Page 18: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/18.jpg)
What is ebXML Registry?
● A standard for secure, reliable, distributed information management
![Page 19: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/19.jpg)
Information is Diverse
● ebXML Registry– Has both registry and repository– Repository holds any type of content– Registry holds standardized metadata – Metadata describes the content and
makes it discoverable
![Page 20: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/20.jpg)
Information is Distributed● ebXML Registry
– Has a loosely coupled federated architecture
– Information may be linked across enterprise boundaries
– Information may be replicated across enterprise boundaries (only when appropriate)
– Federated discovery across enterprises
![Page 21: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/21.jpg)
Info Management is Collaborative
● ebXML Registry– Supports web content management– Web based authoring of information
● ebXML Business Process– Enables collaborative, automated
business processes
![Page 22: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/22.jpg)
Info Sharing Must Be Secure● ebXML Registry
– Authenticity of source via Digital Signatures
– Integrity ensured via signature verification (required)
– Confidentiality ensured via XML Encryption (optional)
– Role Based Access Control enabled via policies based upon XACML 1.0 standard
– Provides complete audit trail of user actions
![Page 23: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/23.jpg)
Info Sharing Must Be Reliable● ebXML Messaging
– Provides authenticity, integrity and confidentiality of messages via digital signatures
– Guaranteed delivery of messages– Quality of service options
![Page 24: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/24.jpg)
Info Sharing Must Be Timely● ebXML Registry
– Asynchronous event notification (Alerting)
– Subscriptions to relevant information– Content based selection of what is
relevant (Filtering)– Delivery of notifications via multiple
channels: email, web service invocation
![Page 25: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/25.jpg)
Info Must Be Self Describing● ebXML Registry Information
Model– Defines standard metadata– Ability to name, describe and uniquely
identify information– Ability to classify information– Ability to define relationships between
information– Working to support semantic metadata
![Page 26: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/26.jpg)
Info Must Be Discoverable● ebXML Registry
– Supports standard metadata that supports extensibility
– Has a standard discovery service– Support ad hoc queries
![Page 27: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/27.jpg)
Need for Standard Vocabularies
● ebXML Core Component● OASIS CAM: Schema assembly● OASIS UBL● Web Ontology Language (OWL)● But who defines all the
standard vocabularies needed in Epidemic Management?
![Page 28: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/28.jpg)
So What is Missing?
● Need controlled vocabulary in many areas
● Need a coordinating body to establish standards, policies, procedures and best practices
● Global cooperation and coordination
![Page 29: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/29.jpg)
The Future is Now
● Movement from paper to web based electronic forms for data entry
● Forms driven by common controlled vocabularies
● Form metadata and data stored in distributed ebXML Registries
● Automated collaborative workflow
![Page 30: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/30.jpg)
Summary● Information management is key
to efficient epidemic management
● ebXML standards meets most requirements for epidemic information management
● There is a need for content standards in various aspects of Epidemic Management
![Page 31: Requirements for Epidemic Information Management Farrukh Najmi XML Standards Architect Sun Microsystems farrukh.najmi@sun.com](https://reader035.vdocuments.us/reader035/viewer/2022062323/56649e1a5503460f94b070ee/html5/thumbnails/31.jpg)
More Information
● ebxml.org– http://www.ebxml.org
● freebxml.org– http://www.freebxml.org
● Open Source freebxml Registry– http://ebxmlrr.sourceforge.net/
presentations/freebXMLRegistryBrochure.pdf