[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Trip Report from Manchester Object Management Group Meeting
Hi All,
I'd like to share with everyone my trip report for the Manchester
Object Management Group (OMG) Techinical Meeting. The trip report
mainly outlines events that occured within the healthcare domain task
force, CORBAmed. The report also outlines some Business Object Domain
Task Force, formerly the Common Facilities TF, and Architecture Board
acitivities. The next OMG meeting will take place during the second
week of June in Orlando, FL.
Enjoy,
Eric N.
--
Eric Navarro
Systems Architect
CPR/Object Technology, IT
Baptist Health Systems of South Florida
ericn@baptisthealth.net
Title: CORBAed Domain Task Force Plenary Session - 3/30/98
Manchester
OMG Technical Meeting Trip Report
Location: Manchester,
UK
Dates:
March 30, 1998 to April 4, 1998
Attendees: Eric Navarro
CORBAmed Domain Task
Force Plenary Session - 3/30/98
Brief CORBAmed and OMG introduction
by Harold Solbrig from 3M.
Brief Note: Votes for the
week will include a Healthcare Data Interpretation RFP, Life Science RFP
on Biomolecular Sequence Analysis, and Lexicon Query Final Submission.
Healthcare Data Interpretation
Facility RFP
Dave Kilman - Brief overview
of Healthcare Data Interpretation Facility RFP. Dave discussed the vagueness
of the RFP text, but it is believed that if the RFP gets too specific,
the responses may be affected and get narrowed.
Life Sciences Domain SIG
- Biomolecular Sequence Analysis
David George - Brief overview
of Life Sciences Biomolecular Sequence Analysis RFP. Basically a framework
for comprised of tools for manipulation, representation and analysis of
biomolecular data, specifically nucleic acid and protein sequences (genes
and their products).
Lexicon Query Service Final
Submission
Harold Solbrig - Brief overview
of Final Submission to the Lexicon Query Service.
Paul Cooper - Discussion of
European CORBAmed chapter. Trying to encourage European participation in
CORBAmed as well as trying to make sure that the differences between European
standards and American standards are include in CORBAmed specification
submissions. Will be introducing three main areas: Enterprise Management,
Patient Record Locator Service, and Card Management.
Decision Support Working
Group - 3/30/98
Work on verbage for Healthcare
Data Interpretation Facility RFP.
-
Recommendation to reword mandatory
question #10 to :"The HDIF submission shall include an informative use
cases and an object model diagram for the HDIF in UML notation. -- accepted.
-
Recommendation to drop the last
paragraph of mandatory question #3. -- accepted.
-
Recommendation to move mandatory
questions #6, #7, and #8 to the evaluation criteria because of their current
not yet adopted status. -- accepted.
-
Recommendation to drop mandatory
question #5. -- accepted.
Enterprise Management Working
Group - 3/30/98
View of Enterprise Management
as seen through the Star Project within the European community..
The Enterprise Management
Architecture seems to be more like a portion of a Healthcare Scheduling
Service and/or a Resource Management Service. The Enterprise Resource Management
can be summed up as:
-
Provides information on healthcare
services available within the territory.
-
Contains an outline description
of:
-
care organizations structure
-
resources and activities
-
a description of care organizations'
objects
-
It must be configured using
a Knowledge Manager.
The group began to bring up
services such as Credentialing, Patient IDentification Service, Lexicon
Query Service, Scheduling, Resource Management, Trader, etc. The Enterprise
Management sounds like a use of all these services together to provide
a service for an enterprise to find, identify and use resources and other
functionality across that enterprise.
Services defined under Enterprise
Management:
-
Scheduling
-
Authorizations
-
Organizational Structure
-
Resources
-
Procedures / Protocols
-
Service Planning / Management
There was talk within the group
that most of the work should be taken up with the Roadmap Group. The group
has begun to notice that there are inter-relationships with services that
have not been identified yet. The Roadmap WG should define these inter-relationships/interactions.
Roadmap Working Group
- 3/31/98
The Roadmap needs to be able
to allow CORBAmed to systematically issue RFIs/RFPs instead of ad hoc.
This would be accomplished by having an overall picture of the CORBAmed
Domain. This overall picture would include services and/or modules that
interoperated at some level.
Review of the Roadmap charter
- Overall the group agreed with the charter.
The main discussion focused
around the fact that some services are healthcare specific while others
are generic to the overall OMG body but that are needed by a particular
domain.
The idea of issuing and producing
a healthcare framework or healthcare template might set an example to other
domains. It will also serve the purpose of helping to coordinate between
domains, as the other domains will know what CORBAmed really needs.
Topics to discuss:
-
RFI for HST - Someone raised
an objection to the idea of an HST. They raised the point that the OMG
wants us to establish RFIs and RFPs to create specifications and not information
models. Someone else brought up the point that the OMG has been asking
for Roadmap type work so that the RFPs and technology specifications are
defined as to how they will be percieved to interoperate/intereact with
other services within and outside of CORBAmed. One more person brought
up the point that we are the OMG. The group decided that we need
an HST. It was also decided that in Orlando to have an RFI for submission.
-
Modality - we need to discuss
what modality to use for the RFI. By modality the group meant a means
to define the healthcare template in a common way so that any RFI put out
by the Roadmap group would have responses that were easily interpreted
and then further combined.
The group agreed to try and
determine the modality to use to try and describe the templates or frameworks
for the purpose of mandating it within the RFI. This way the responses
to the RFI will be coherent and understandable by everyone in the Roadmap
WG. A meeting has been scheduled for April 1st in the morning
to discuss the modality.
Patient Record Locator
Service - 3/31/98
The Patient Records Locator
Service in the star architecture is the Patient Reference Manager. The
Patient Reference Manager is comprised of Patient ID, public patient demographics,
References, and Access Criteria.
Etienne S. - The Patient
Record Locator is more of a Data Directory that helps to tie in Clinical
Data (which may be contained in the COAS), referral information, admission,
etc.
The Patient Data/Record Locator
can be viewed as a coordinator between information that is distributed
across clinical data services. The Patient Data/Record Locator is very
close to building our client application that will pull together information
from clinical data services.
The Patient Data Locator
seems to be a service that may me useful once COAS and some other clinical
data services (ie Image Access Service, Report Management, etc.) are adopted.
CORBAmed Domain Task Force
Plenary Session - 4/2/98
Reports from the Working
Groups:
Roadmap - new charter
has been accepted by the DTF. The group agreed to create a Green
Paper to act as a strawman for further discussion on the CHST. Several
organizations will try and begin creating the CHSTs and have samples that
the group will look over in Orlando. The Green Paper and the examples
will server the purpose of a first pass at what the CHST will look like.
If the group agrees on the way the CHST is described in the Green Paper
and within the examples, they may be included into an RFI for organizations
to respond.
Security - brief presentations
were conducted on certificates, smart cards and some talk on credentialling
went on within the Security WG. The Security WG has recommended that the
Credentialling WG change their name to something like Professional Certificates,
due to the naming conflict with the credentials within the CORBAsecurity
specification. Several RFPs will be drafted for the Helsinki time frame.
Biomedical Imaging -
Most of the session was used to discuss the Image Access Service RFP 98-03-24
and it will try to be issued at the Orlando meeting. The next draft RFP
will try and come out in the Orlando meeting. It will focus on Streamed
Image RFP.
Clinical Encounter Service
- From the original Encounter Management discussion in Salt Lake City
a Demographics Service was discussed. A white paper on Demographics was
published and is on the OMG server. More discussion will try to take
place in Orlando on the subject of a Demographics Service.
Enterprise Management
- Presented on the RICHE/STAR enterprise manager. Enterprise Management
is the collection of tings related to the management of a healthcare organization.
Enterprise Management includes: scheduling, authorizations, organizational
structure description, resources, procedures/protocols, and service planning/management.
Card Management -
Current uses of smartcards in Europe: healthcare professional (identification),
patient administration, patient data, and multifunctional.
Record Locator Service -
Presentations: Record location in STAR - PRM, Data Directory Service (Etienne
Saliez), Record Agents (Damon Berry), Integrated and navigable data (David
Jones). Record Locator Service has dependencies on COAS, PIDS, other clinical
data. The Record Locator is basically a directory service.
Transcription - Distributed
the white paper and began outlining a draft RFP. The draft RFP will be
ready to be voted on in Orlando.
Other Discussions:
Peter W. mentioned that
there were several requests outside CORBAmed that were asking for immunizations
and also eligibility.
Marketing:
There was a discussion on
Healthcare marketing efforts for CORBAmed. In the Orlando meeting there
will be a discussion on marketing efforts during two breakfast meetings
Voting:
CORBA Lexicon Query
Service with errata 98-03-22 & w/o errata 98-03-03
-
Motion to recommend to vote
for adoption at this meeting
-
Motion to recommend for adoption
Healthcare Data Interpretation
Facility 98-03-29
-
Motion to recommend for submission
Life Sciences Bimolecular
Sequence Analysis lifesci/98-03-05
-
Motion to recommend for submission
Business Object Domain
Task Force (BODTF) Plenary Session - 4/1/98
Workflow Management
Facility -
Workflow Evaluation Working
Group - The two remaining submitters are looking forward having the two
submissions merged. The evaluation working group did not have any suggestions
other than they wish that the two submissions be joined.
-
Motion to move the Workflow
submission deadline to July 4th, three weeks before the Helsinki,
Finland meeting.
Business Object Facility
-
Brief presentation on the
BOCA submission by Cory Casanave, Data Access Technologies
Discussed the role of BOCA
within the CORBA world. Also discussed that the BOCA submission touches
upon several other domains and platforms, such as OA&D, CORBA core,
and IDL.
Business Object Facility
Working Group - David Depinet presented to the group the Evaluation WG's
re-recommendation to adopt the BOCA.
-
Motion to adopt Business
Object Component Architecture
Several vendors have raised
the point that the technology should be adopted and that most of the time,
specifications that come out of OMG are not perfect the first time around.
The argument is in effect, get the specification out there and we'll revise
it later.
The OA&D has brought
up the point that the BOCA has come a long way and that both BOCA and UML
both conform to the Meta-Object Facility. Their only concern is that the
BOCA and UML meta-model have areas of overlap, beyond the current BOCA
to UML mapping, that should be taken care before the specification is adopted.
Vote Seconded
Approved
-
Motion to adopt BOCA Interoperability
98-03-05 and Errata 98-03-21
BOCA Interoperability Evaluation
Working Group - recommends for adoption after all changes that were recommended
have been added into specification.
Vote Seconded
Approved
-
Motion to adopt Common Business
Objects 98-03-02 and Errata 98-04-01
Common Business Objects
Evaluation Working Group - recommends to adopt CBOs either as a multiple
CBO submission or as individual CBO submissions.
Meeting Adjourned - 12:35PM
Architecture Board Plenary
Session - 4/2/98
Policies and Procedures
Two P&P recommendations
were recommended for approval to the Domain Technical (DTC) Committee and
Platform Technical Committee (PTC).
Request for Proposals
Realtime Dynamic Scheduling
Motion defeated
Fault Tolerance Using Redundant
Entities
Motion approved
Biomolecular Sequence Analysis
Motion approved
Healthcare Data Interpretation
Facility
Motion approved
Technology Adoptions
-
Lexicon Query Service
-
Motion to recommend to adopt
-
Motion approved
-
Currency
-
Motion to recommend to adopt
with amendments
-
Motion approved
-
Common Business Objects
-
Motion to recommend to adopt
-
Motion to amend the adoption
vote
-
Motion failed
-
Motion failed
-
Census from AB is to refine
submission and bring back to AB
-
Business Object Component Architecture
(BOCA) Interoperability
-
Motion to recommend to adopt
-
Motion failed
-
Census from AB is that the AB
will send to the submitters a list of architectural problems with the specification
within a two week time period. The idea is to clean up the specification.
-
Business Object Component Architecture
(BOCA)
-
Motion to recommend to adopt
-
Motion approved
-
Notification Service
-
Motion to recommend to adopt
-
Motion approved
Three more submissions were
looked at by the Architecture Board, but after the Notification Service,
the AB had a break session at 6:00PM. Any RFPs and Technology Adoptions
recommended by the Architecture Board are still subject to approval by
both the Domain Technical Committee or Platform Technical Committee votes
that were scheduled for Friday April 4th, 1998. The next OMG Technical
Meeting will occur in Orlando, Florida sometime in the second week of June
1998.