Weekly Open-Source EHR - Architecture Work Group (AWG) Telecom
August 28, 2012 OSEHRA AWG AGENDA-MINUTES
Last Updated 9 AM EDT, 28-Aug-12
DATE & TIME: Every Tuesday 4:00 PM - 5:00 PM EDT
CALL IN: The new AWG Dial-in:
1-650-479-3207, Access code: 662 014 630
Meeting Access at:
https://osehra.webex.com/osehra/onstage/g.php?t=a&d=662014630
DOCUMENTS at:
http://www.osehra.org/node/47/content/documents
DISCUSSION at:
http://www.osehra.org/node/47/content/discussions
WIKI at:
http://www.osehra.org/node/47/content/wikis
Web Browser HTML SYSTEM ARCHITECTURE at:
http://architecture.osehra.org
VISUAL CROSS-REFERENCE of PACKAGES/ROUTINES/GLOBALS are at:
http://code.osehra.org/dox/ for 2011-9-6 release
http://code.osehra.org/dox_beta/ for 2012-12-6 FOIA release
E-MAIL DISTRIBUTION LIST:
archit...@groups.osehra.org – you must be
registered to post/receive. Please register with Architecture Group
• Joining OSEHRA is free; please join at
www.OSEHRA.org .
• To receive AWG e-mail, join the OSEHRA AWG at:
http://www.osehra.org/groups
• Add your comments and suggestions to the AWG “discussion forum” or
“Wiki”.
VA POSITION ON OSEHRA PARTICIPATION: Senior VA leadership encourages
employees and contractors to actively participate in technical
discussions without pre-approval; but, employees and contractors must
NOT commit the government to a particular course-of-action without
appropriate management pre-approval.
AWG PLAN OF ACTIONS & MILESTONES
• 17 Sep 2011 Initial 2011 System Architecture baseline
• 06 Dec 2011 validated 2011 System Architecture baseline
• 17 Mar 2012 “strawman” Product Definition and Roadmap
• 17 Jun 2012 “ironman” Production Definition and Roadmap.
• 01 Oct 2012 Product definition for all 126 hospitals (pending
funding)
AGENDA/MINUTES (slides at:
http://www.osehra.org/node/47/content/documents
) under AWG minutes
(Related slides & spread sheets are posted at the
“Documents” link given above)
1. Start: Introductions and Roll Call
2. Minutes: Approve last week’s minutes and review/update this week’s
agenda
Action Items: review open action items
1. Patrick Pearcy to provide availability of OSEHRA project space
within the Harris government sandbox.
21 Aug Minutes: Rick Marshall of VISTA Expertise Network will discuss
repurposing VistA to conform to modern Software Engineering “best
Practices.” What is possible/ practical, considering Rick has already
proposed bringing the MUMPS specification up to a modern Object
Language, supporting SOA:
GIVEN SITUATION: VA mandated software engineering “best practices”
are to separate and loosely couples:
• Data services, Business Rule services, Application Code services,
Presentation layer services
• Common services (e.g., Enterprise Service Bus, security)
• Business Services and orchestrated business workflow & “value chain”
services
RICKS POINTS:
1. Best Practices = Standardization Innovation being crushed
o User type ? <CR> Help is a good best-practice/standardization
o Principle of Localization is a true “best practice”
2. Integration versus decoupling (e.g., objects can be integrated to
produce a decoupled capability)
3. Relational Model results in maximum flexibility
4. Car example
o Object Oriented model is best if you want to reuse the car, as a
whole
o Relational model is best, if you want the flexibility to build
something else from the car parts.
5. Proper repurposing is at a small level, such as Problem List, done
by RGI
6. VistA CPRS applications can be wrapped as reusable services
o protocol unwinder is an example
7. CONCLUSION: Object Design principles are more important than an
Object extension to MUMPS.
8. Potential Future Topic: How to separate VistA business rules, code
and data
28 Aug Topic: Steve Hufnagel lead review of “Recommendation Slides”
for OSEHRA Board and IPO.
4-Sep-12 Topic: MongoDB and Security by Chris Scheich,10gen
MongoDB is an open source, document-oriented database designed with
both scalability and developer agility in mind. Instead of storing
your data in tables and rows as you would with a relational database,
in MongoDB you store JSON-like documents with dynamic schemas. The
goal of MongoDB is to bridge the gap between key-value stores (which
are fast and scalable) and relational databases (which have rich
functionality).
Using BSON (binary JSON), developers can easily map to modern object-
oriented languages without a complicated ORM layer. This new data
model simplifies coding significantly, and also improves performance
by grouping relevant data together internally.
MongoDB maintains many of the great features of a relational
database – like indexes and dynamic queries. But by changing the data
model from relational to document-oriented, you gain many advantages,
including greater agility through flexible schemas and easier
horizontal scalability.
More and more developers are looking for alternatives to the
relational database, and MongoDB is the leading alternative. MongoDB
offers a number of compelling advantages:
• Agility: MongoDB simplifies development. Data in MongoDB is stored
in JSON-like documents with dynamic schemas, providing flexibility
during the development process.
• Scalability: With built-in support for horizontal scalability,
MongoDB allows users to build and grow their applications more
rapidly. With auto-sharding, you can easily distribute data across
many nodes. Replica sets enable high availability, with automatic
failover and recovery of database nodes within or across data centers.
• Enterprise Readiness
o Robust technology: Unlike many noSQL databases, MongoDB supports
full consistency and transactional updates. Data integrity is
guaranteed through journaling and replication.
o Leading enterprise customers: MongoDB isn’t just for web startups:
the 5 largest organizations using MongoDB average over $70 billion in
annual revenue, larger than Boeing, Goldman Sachs, or Pfizer.
o Clear vision: MongoDB aims to provide greater agility and
scalability for many applications by eliminating joins and relational
modeling. We expect to coexist with relational databases and provide
many of the features developers have come to expect like indexes and
full consistency.
o Strong team: 10gen, the company which builds and supports MongoDB,
is led by seasoned executives and technologists with senior leadership
experience at many of the worlds leading technology companies,
including 2 executives and 4 senior engineers with over 50 years
combined experience at Oracle. 10gen is backed by leading venture
capital firms who invested in established leaders like Oracle, Cisco
and Apple as well as rapidly growing internet companies like Zynga and
Twitter.
o The support you need: 10gen offers a broad range of services from
24x7 enterprise support to training, architecture consulting,
deployment planning, and systems monitoring. In addition, 10gen has
full ownership of the MongoDB code and can offer commercial licenses
for organizations unable to use open-source-licensed software.
o Community: MongoDB has the strongest and most vibrant community
among alternative databases. Adoption is growing, with customers
ranging from Fortune 10 enterprises to fast growing internet companies
like foursquare. There are thousands of production deployments of
MongoDB, thousands of job searches in progress for MongoDB developers,
thousands of developers attending MongoDB conferences, and thousands
of user messages exchanged each month on MongoDB forums.
iEHR References are available on the TMA Vendor Information web page
located at the following URL:
•
http://www.tricare.mil/tma/ipo/vendor.aspx
The Technical Specifications Overview Document is comprised of six
sections and two Appendices, and can be found at the following URL:
•
http://www.tricare.mil/tma/ipo/documents/TechnicalSpecificationPackage.pdf
Information contained in section 2.0 through 6.0 is further described
by files which can be accessed through the following links:
• 2.0 Enterprise Architecture
• 3.0 Enabling Infrastructure Capabilities
• 4.0 Clinical Requirements
• 5.0 Privacy Security and Info Assurance Reqs
• 6.0 Additional Information and Requirements