Appendix B. Technical Approach and Feasibility
B1. Overview of System and Networking
From Kent:
iCHP is implemented using commercially available products.
iCHP is not a software development effort but it is an integration effort.
CPR is based on CORBA, see attached paper, if you'd like to steal something
See how I carried Health Agents as a stereotype in the use case..I think this is
pretty consistent w/ what you had in mind. TAKE A LOOK AT MY SECTION A.1
Session profiles are XML documents, constructed by making CORBA calls and
from other XML sources
Health Plans and workflows are described in XML.
Initiation of of workflow is w/ a CORBA workflow service
Content, is local XML documents, or using ICE for external content sources
CORBAmed stuff
PIDS
LQS
COAS
RAD (old HRAC)
Open, open -> standards.
If no CPR, use consumer interests only
If not consumer interests -> build one ;-)
XSL for presentation…no mystery…;-)
B2. System Architecture
iCHP System Architecture
Exisiting BHS
Information
Systems
BHS
Clinical
Systems
BHS CPR
Services
BHS Video
Content
BHS
Electronic
Content
Stored
XML DTD
XML
Document
Server
Video
Library
Streaming
Video
Server
iCHP services are
distributied over several
production systems
Java/CORBA
API
Java/
CORBA
API
Web
Application
Server
CGI API
Common
Gateway
Interface
Workflow
Engine
Java/
CORBA
API
C++ API
Web Server
with SSL
Extenstions
Client
System
Encrypted
SSL
Java Enabled
Web Browser
with SSL
Windows
based
Streaming
Video player
Production
Systems
Security issues
The proposed security architecture will provide safety and privacy of the
information collected, processed, stored and provided by the enterprise. The
architecture will be based on the advanced open technologies. It will utilize public
key infrastructure (PKI)[Ref], LDAP[Ref], OMG CORBA security service[Ref],
OMG Resource Access Decision[Ref], smart cards[Ref] in addition to advanced
firewall technologies such as virtual private networks (VPN)[Ref].
PKI will play the primary role in user and party authentication as well as in data
authenticity, non-repudiation, integrity and confidentiality protection. Certificate
life-cycle management will be centered around LDAP-compliant directory service.
PKI and LDAP will serve as a foundation for consumer and intranet user
authentication and authorization, VPN security management.
The VPN solution will be based on such an open protocol as IPsec[Ref].
Access control to services and data will utilize strong PKI-based authentication
with smart-card technology, CORBA security service, and Resource Access
Decision facility from the OMG.
B3. Network Architecture
iCHP Metropolitan Network Architecture
iCHP
BHS
VPN
Video
iCHP
FIU/CADSE
VPN
Integrations
Systems
Existing
ATM
Florida
International
University
fiu.edu
Baptist Health
Systems
bhssf.org
Existing
100 Mbps
Production
Systems Existing
10 Mbps
10 Mbps
DS1
Kendall Clinic
ASDL
Metropolitan
Internet Service
Provider
Exisiting
10 Mbps
ISDN
Homestead
Clinic
On-Demand
Service
ASDL
ASDL
South Miami
Congregation
FIU Clinic
FIU and BHS will coordinate a
metropolitan area network which
will interconnect four different
clinic access sites and multiple
internet connections
Internet
56K
Consumer
Home
33.6K
Other Internet
access site
Clinics are connected at
ASDL/ISDN speeds to
provide a adequate
network bandwidth for
realtime video service and
interactive conferencing.
Networking requirements
We believe that network connectivity speeds greater than today’s analog modem
service is needed to support clinic sites since there will be several systems
accessing the networking simultaneously. System responsiveness is an
important factor since most users will be computer novices and may become
impatient when, due to the shared architecture of Internet topology, are delayed
due to network congestion. Since the ICHP metropolitan network will be
interconnect via the same ISP we believe this will not be as prevalent a problem.
Networking Security
Since the confidentiality of the ICHP participants is imperative we envision a
secure Virtual Private Network (VPN) will be created between FIU and BHS to
allow for the migration of integrated components develop at FIU to the BHS
production servers. The VPN will encrypt data leaving the FIU development and
BHS production sites before the data is delivered to the ISP. At all ICHP sites
integrated firewall and network router products will be used to provide security
from unauthorized access to ICHP equipment. All data interactions with ICHP
service will occur via web browsers enabled Secure Sockets Layer (SSL)
communications.
B4. Applicants Qualifications
Expert in the field for evaluation...
Jai Navlakha received his Ph.D. in Computer Science from Case Western
Reserve University in December 1977. Since then, he has been associated with
the School of Computer Science (initially, part of the Department of Mathematical
Sciences) at Florida International University. He was promoted to the rank of Full
Professor in Fall 1987, and served as the Director of the School from 1988 to
1992. Since Fall 1996, he has been the Director of the Center for Computational
Research in the School. He has published widely in the areas of software
engineering, algorithm analysis, expert systems and neural network applications.
Kent......
As the Corporate Director of Object Technology, system architecture is Kent
Wreder’s main area of responsibility within the Information Technology
Department at Baptist Health Systems of South Florida (BHS). He leads this
effort that started at BHS about three years ago which essentially augmented the
system acquisition process with a mandatory focus on a service-based
healthcare enterprise system architecture. Kent is a leading member within the
healthcare domain task force within the Obejct Management Group
(CORBAmed) within which interoperability standards for distributed healthcare
computing are produced. Kent also participates in researching distributed object
computing issues related to healthcare at the Center for Advanced Distributed
Systems Engineering (CADSE), a research division within the School Computer
Science at Florida International University.
Prior to joining BHS in 1992, Kent held research positions within the College of
Engineering at Florida International University and with the Corporate Research
Department of Cordis Corporation. He holds patents and inventions disclosures
in laser angioplasty, intravascular ultrasound and balloon angioplasty.
Kent holds a Bachelors of Science in Mechanical Engineering as well as a
Master’s in Computer Engineering and is currently pursuing a Ph.D. in Computer
Science with a Software Engineering focus.
Publications and presentations - 1998
Publications:
"Architecting a computerized patient record with distributed objects", Health Information Management
System Society Conference Proceedings, pages 149-158, February 1998
"The OMG Healthcare Domain Task Force Roadmap", Object Management Group (Document Number
corbamed/98-01-06),
January 1998
"Response to CORBAmed Clinical Observation RFI", Object Management Group, January 1998.
"An OMA-based Computerized Patient Record", Distributed Computing Magazine, September 1998
"Objects in Healthcare : focus on standards", ACM Standards View, Summer ‘98
"Architecture-Centered Enterprise System Development and Integration Based on Distributed Object
Technology Standard". Submitted to The International Conference of Software Engineering ’99.
"OMG Workflow Management Facility Use for Healthcare Task Management" - Object Management
Group Meeting
"Introduction to Systems Architecture" - BHS/IT document
"Issues in the security architecture of the computerized patient record enterprise", In Proceedings of Second
Workshop on Distributed Object Computing Security, Baltimore, Maryland, USA, May 1998.
"Taxonomy of CPR enterprise security concerns at Baptist Health Systems of South Florida", December
1997.
"CORBAmed Security White Paper", Object Management Group, November 1997. OMG document
number: corbamed/97-11-03
"Official requirements and recommendations from various organizations on security for Baptist Health
Systems of South Florida", October 1997.
Presentations
"Is Healthcare ready for the Internet?" - HOST Fall meeting, November 13-14, 1997
"An Approach to Construct a Computerized Patient Record Based on the Object Management
Architecture" , Role of Distributed Objects in Healthcare, 29 & 30 October 1998
"Architecting a Computerized Patient Record with CORBA" - Object Management Group
"Issues in the security architecture of the computerized patient record enterprise"
Second Workshop on Distributed Object Computing Security, Baltimore, Maryland,
May 1998
"Role-based Access Control and CORBA security", CORBAmed SecSIG in December of 1997
"Healthcare Security Framework", CORBAmed SecSIG in December of 1997
"Healthcare Resource Access Control RFP", Object Management Group Meeting, 1998
"Healthcare Resource Access Control RFP Submision", Object Management Group Meeting, 1998
"Healthcare Administrative, Logistical, Financial, Encounter Management RFP", Object Management
Group Meeting
"Reference Model for Open Distributed Processing", Florida International University, July 1998
Notes
Feasibility
Overall feasibility of your proposed project
Show how you will implement the project:
Technical Approach
Detail the technology that will be used in the project.
Rationale in selecting technology.
How the various components will be organized and work in tandem.
Are solutions appropriate, effective for meeting the goals set forth in the project
definition.
Be specific with technology descriptions.
Append diagrams for clarity
What are the existing networking technologies, resources and services available
to the end users.
How technical and organizational system will work.
1. How it will operate with other systems
2. What alternatives have been examined and the reason why you considered
the approach you have chosen to be superior.
3. How it can grow to accommodate additional users
4. Plans for maintaining and/or upgrading the system
1. Interoperability: show how your system will work with others.
Discuss use of standards.
Provide justification if proprietary system is being used when open standards
version is available.
2. Technical alternatives: why the technical approach best meets your goals.
Project should take advantage of existing infrastructure and commercially
available telecommunications services. Justify building your own network
services.
3. Scalability: how will the system accommodate growth beyond the scale
defined for the grant period. Growth in terms of users, geographic region,
services—discuss the the systems ability to add more services after it is
completed.
4. Maintaining the system: upgrades and capacity as technology becomes
available.
Applicant qualifications:
Show how team can effectively deal with technical compleity and organizational
chanllenges associated with managin the project. Descibe qualifications of team
members, including organizations and partners. Commitment and experience to
deliver on time. Show experience in networking technology projects, serving
communities the project will serve, and with project management.
Append bios of key personnel and orgs.
Description of the qualifications of the personnel you intend to hire.
Budget, Implementation, Schedule and Timeline
Show how budget relates to project narrative.
Overview of the budget.
Identify all budget categories
Allow enough time to develop, implement and evaluate project.
Implementation schedule of milestones and tasks.
Use appendix for timeline
Sustainability:
Project should exhibit economic and organizational viability beyond the grant
period.
Discussion of anticipated ongoing expenses and potential sources of non-federal
funds to sustain the project.
Start-up partners and their responsibility for various segments of the project to
remain the same or change over time.
Definition
Discuss the problem you are trying to solve.
The solution you propose
The outcomes you expect
Show impact on the community and involved in the project
Proposed solution meets community’s needs and will have reasonable and
achievable outcomes.
Defining a specific need or problem.
Define problem and needs and show how network technology can solve them.
Focus on defining these problems.
Proposing a credible solution that employs network technologies.
How are you going to use networking technologies to address the problem.
How information services will address these problems.
Clearly link problem to solution.
Identifying realistic, measurable outcomes that you expect to result from
implementation of the project.
How will this make a difference—based on outcome.
Outcomes tied to problems and include a range aof measurements to determine
if need has been addressed.
What do you expect to change in your community?
Who will be impacted?
What specific, realistic outcomes do you expect to occur within the grant award
period?
Long term effect?