Draft Minutes
NV RHIO Interoperability and Infrastructure
Advisory Committee
December 21, 2006
Attendance:
Action Items
| Description |
Assigned To |
Target Date for Completion |
Status |
| Refine
the high level work plan that Mike presented to the group to start showing
some timelines, etc. |
Mike
Corrigan |
1/12/07 |
Open |
| Provide
areas of interest and subject matter expertise to Helayne Sweet for
Consolidation |
All |
1/5/07 |
Open |
| Distribute
High Level Architecture from Delaware |
Marion |
TBD |
Open |
| Start
Inventory Spreadsheet for fill in of what data exists, in what system,
how we will get it, etc. |
Helayne |
12/30/06 |
Open |
| Work
with JP to set up Share point |
Lauren |
ASAP |
Open |
| Follow
up with SharedHealth and InterSystems to get them on our calendar for
meetings in January |
Helayne |
ASAP |
Open |
| Follow
up on availability of Fairfax
Hospital as next site |
Dr.
Geoly to let Mike know |
ASAP |
Open |
Agenda and Minutes
Technology scenarios
Group agreed to think about concept first and then how to finance later.
We need to develop each of the technology scenarios in more depth. Continuing
to explore hub between hospital systems and physician practices – Dr. Geeoly
says this is already attainable now – already exists between hospitals. Problem
is how it is displayed. We need to focus on creating a more continuous database.
Point was raised that if we are looking to get demographics, lab/rad, and
medications then we need to incorporate more than just the hospitals.
Black box is outpatient. Suggestion is to get hospital data in first and
then back in to the other. Working hypothesis – more of
a hybrid model. Won’t have imaging data in this
model. Radiology report is what is needed versus the image.
Hybrid model seems to have consensus. Centralized databank of any kind –
need more of an infrastructure – could lead to a higher cost for participants.
We will need a central repository for some data sources – for example Lab
Corp doesn’t have a database you can access – all medical labs purge the data
– so exchange has to keep the database for this but for anything coming from
the hospital, the information stays at the hospital. Pointers to information
will be provided for information that stays at the source..
Performance is another issue. Concern on remote data –
physician practices don’t run 24x7 but hospitals do. May
need to pull data in from some locations.
Example Architectures
Marion can send the high level architecture from Delaware.
Mike discussed his discussion with Bill Yasnoff about the health data bank.
If you want the information available need to ensure it is up 24x7. This
really requires replicated data, and one advantage of the RHIO for providers
may be the provision of a back-up service. Helayne suggested scheduling to
have some others come in and talk about the different models – InterSystems
has a good model and is willing to come in and discuss the model that they
have been working on with other RHIOs. Group agreed some additional education
sessions would be helpful.
Data Call/Inventory
We need to continue to develop a list of providers and the data that they
can provide – what do we have already that can integrate with other things.
This is what we need to divide out. Payer number and patient number, and
provider number and patient number can be used to uniquely identify patients,
but there may be several of these per patient. Thrust is not toward a single
identifier. Demographic information and other approaches have been taken by
other RHIOs to group all the information of a patient together. The infrastructure
committee is the logical home for developing the approach to identification.
We need answers to the following: What existing inventory is there – payers,
providers, lab? What data is going to be contributed
into the hybrid? What is the system, how can we get that data in, etc. We
need to put together an inventory. We will start a spreadsheet to collect
data inventory to circulate across the group.
Outcomes and Metrics
Group agreed that Outcomes are key – time, usage is important to collect
as well. This is something if anyone has anything examples would be helpful
to share.
WorkPlan
Mike will fine tune the high level work breakdown structure. Send in areas
of interest to Helayne.
Administration
There is no current group to handle administration (e.g., RFP). This group
believes they might be responsible for some of the content of the RFP but
Steering Committee overall would need to approve.
Miscellaneous
Lauren said she would be glad to help JP regarding getting the Sharepoint
up. We will try to set up a conference call on the 12th of January
to accommodate those individuals that can’t attend in person. Dr. Geoly will
see if we can do it at Fairfax Hospital. If that doesn’t work out
can find another location - Bearing Point is another option for location.
Goal is have version 1 or 2 of plan and assignments.
Mike mentioned he is planning a community meeting for Reston Association
in March about RHIOs. Thinking about March 17th. This is part of the
RHIO Outreach effort and the Technology Group is glad to assist in preparing
for this.
