Meeting Minutes - Mayo Clinic Informatics

feelingmomInternet και Εφαρμογές Web

7 Δεκ 2013 (πριν από 3 χρόνια και 6 μήνες)

59 εμφανίσεις

CIMI Meeting

January 18
-
20, 2013

CIMI Scottsdale Meeting

Agenda

Friday January
18, 2013

Topic

Timeframe

Welcome and Overview


Stan Huff

8:00 a.m.
--

15 minutes

IHTSDO Value Set Authoring Tool


John Gutai

8:15 a.m.


45 minutes

HL7 Logistic Support
Services


Stan Huff

9:00 a.m.
--

30 minutes

Break

9:30 a.m.

Organizational Issues


Bu獩湥獳⁅n瑩瑹


䵥Mb敲獨楰


䱩L敮獥s慧a敥m敮瑳


Operating Model

10:00 a.m.


90
minutes

Example Instances from ADL Workbench


Tom Beale

11:30
p.m.


30 minutes

Lunch

12:00
p.m.

CIMI Scottsdale Meeting

Agenda

Friday January
18, 2013

Syntax for Specifying Example Data Instances


Stan Huff

1:00

p.m.



30 minutes

New Process Proposals

1:30 p.m.


60 minutes

Break

2:30 p.m.

Update on OMG and UML Models


Dave Carlson and Robert
Lario

3:00 p.m.


60 minutes

Terminology authoring
tools


Stan Huff


Requirements


Op瑩潮t


Av慩污扩汩瑹a


C潳t


䵡M慧敭敮t


䑥晩n攠獥汥s瑩潮tpr潣o獳

Pet敲e
䡥Hd汥l



I䡔卄传W潲止敮ch 䑥D潮o瑲a瑩潮

卮潷O睬

䑥D潮o瑲a瑩潮

4:00
p.m.


60 minutes

CIMI Scottsdale Meeting

Agenda

Saturday January 19, 2013

Topic

Timeframe

Model Authoring
Tools


Stan Huff


Op瑩潮t


Av慩污扩汩瑹a


C潳t


䵡M慧敭敮t


䑥晩n攠獥汥s瑩潮tpr潣o獳

8
:〰 愮m



60 minutes

Break

9:30 a.m.

Relationship of CIMI to International Standards and
Products


Stan Huff

10:30
a.m.


10
minutes

Registry/Repository
--

Stan Huff/Nicholas


Repository Proposal
--

Evert Jan
Hoijtink


䡩湧H



Mark Shafarman

10:40
a.m.
--

90
minutes

Lunch

--

Working Lunch

to Complete MTF Report

12:00 p.m.

Report from the
MTF
--

Linda Bird

12:30
a.m.
--

120
minutes

Break

2:30 p.m.

MTF Working Session

3:00 p.m.


120 minutes

Sunday January 20, 2013

MTF Working Session

8:00 a.m.
--

90 minutes

Break

9:30 a.m.

Identify and Prioritize Near Term
Projects
--

Stan Huff

10:00 a.m.


60 minutes

Review of Action Items and Next Steps

11:00 a.m.


60 minutes

https://www.surveymonkey.com/s/JLZ6522


Authoring Tool Options


UML authoring tool


Results4Care


EA


Stereotyping to create classes


Each data element class expresses data element type


Bind to codes


Other classes include modifiers


Available for free as an open source tool


Also have an import/export tool


Import


Excel


Intermountain


OpenEHR


Generate an UML representation


Export to CIMI ADL, HL7 v3, and view for clinicians


Internal validator


Users


there are other users, but do not know how many


Two Dutch users


sharing code sets, and generating v3 messages


Michael using to define DCMs for summary of care and to import spreadsheets for life science project


Model repository


Can check out


Can edit


Using terminology from a terminology server


Will use the core reference model


Validation as items are checked back in


Need one editor that meets these requirements


Probably a suite of tools, e.g., Value set editor + ?


How to get to a decision


Task force to develop requirements


Assess tools


Make recommendations to the full group


Needs to be done expeditiously


Spreadsheet proposal


Core columns with extension columns


Could start with AOM to define columns


Will need a way to maintain metadata


Need to be able to retain the relationships of the data


AOM


Is a
contraint

model


We have agreed to use AOM


Need to be careful about going fine grained. Can lose the relationships between data elements


Task Force


William


Linda


Joey


Harold


Dave


Galen


Mark


Alan


Niranjan


Michael



Timeframe




Short term


6 weeks


March 1, 2013


Long term


Registry/Repository


Building models


Requires software development type of capabilities, e.g., check
-
in, check
-
out


GitHub
/
Collabnet
/
LifeRay


GitHub

can host software development project. Free if software is publically available. $7/
mos

for 5 accounts


Collabnet



has more capabilities


LifeRay



Has conceptual indexing. Open Source collaborative tool. Mayo may be willing to stand up
LifeRay

for CIMI


Hive5


Offers separate section for building models and then promote them to public availability. Has indexing.


Intermountain


Has a repository. Could offer a partition to CIMI


Managing contributed models


Could index models being contributed


Would have one gold standard repository of CIMI models


For publishing purposes would have one big repository


Models could be distributed and be located by using Google


Distributed models would be harder to track usage


Workflows


How do contributed models get to the point of being published? These may have an intermediate stage where they have their ow
n s
torage


CIMI developed models that have a place where they can be worked on


Published models are in one publically available repository or possibly
distrbuted


What is a CIMI Model


Conformance is the basic level.


CIMI will have one official model that can be translated by users to their models


Fit for use


Will raise liability issues


Professional societies could take the models and use them in their own profiles. We would track in the repository if a socie
ty
has approved a model.


We would track metadata on the models that would include who has


IHTSDO has a quality assurance process. Specifies criteria for evaluating content. CIMI could look at these criteria


Can have an approved CIMI model. There can be extensions to the CIMI model. SNOMED has processes for extensions that might b
e r
elevant to CIMI. CIMI could host extensions, but not consider
them “official” CIMI models. We should have the capability to support this


Distributed repositories


Registry says that the model is certified by CIMI and can point to where the model can be retrieved


ISO Standard for Quality Metrics


Being proposed


Specific c criteria based on CIMI reference model


Publication of Extensions


Could use an URI to identify extensions


Need an identifier for archetypes. This does not exist in
OpenEHR


Need to have an identifier scheme


CIMI will not approve extension models


Four categories
--

submissions to CIMI for review in the development of a model, models CIMI is working on, approved models, ex
tensions/derivative models


Need a process to obtain ongoing feedback and update the models


Proposal for Moving Forward


Stan will summarize the discussion and circulate for comments


Evert will share the requirements document that they
have developed.


Welcome
and Overview


Stan Huff

8:00 a.m.
--

15 minutes




IHTSDO
Value Set Authoring Tool


John Gutai

8:15 a.m.


45 minutes




HL7
Logistic Support Services

9:00 a.m.
--

30 minutes




IP
Issues


Nicholas
Oughtibridge

10:00
a.m.


45 minutes



Business
Entity


License
agreement for
contributor


License
agreement for users

Governance and Operations


Nicholas
Oughtibridge

10:45 a.m.
--

90
minutes


Organizational


CIMI
Artifact

CIMI
Inc


Provides or contracts for services


Accepts payments


Can enters into contracts for services


Obtains legal, auditing, and accounting services

There is a payment to be a member of CIMI Inc. This is unrelated to payments made to
be part of the Modeling Collaborative

C
an be a member of CIMI Inc. without being a member of the Modeling Collaborative

Governed by a board elected by the CIMI Inc. members

CIMI Modeling Collaborative

Develop, manage, and govern models and tools


Comprised of Contributors and Participants

Contributors are voting members

Contributors enter into a mutual agreements

Contributors may pay dues by mutual agreement

Establishes a management committee

Requests CIMI Inc. to arrange services

Establishes and manages IP Policies

Membership Categories


Contributors


Contribute models


Get voting rights


Pay dues


Participants


J
oin discussions,


May be users of models,


D
o not vote


Do not pay dues

Membership
--

Jamie Ferguson

12:30 p.m.


30
minutes


Example Instances from ADL Workbench


Tom Beale

1:00 p.m.


30
minutes



Update
on OMG and UML Models



Dave
Carlson and Robert
Lario

1:30 p.m.


60 minutes



Terminology Authoring Tools

3:00 p.m.


60 minutes


Requirements


Options


Availability


Cost


Management


Define selection process


Peter
Hendler

--

IHTSDO Workbench Demonstration


SnowOwl

Demonstration


Model Authoring Tools

4:00 p.m.


60
minutes


Options


Availability


Cost


Management


Define selection process


Saturday

Relationship of CIMI to International Standards and
Products

8:00 a.m.


30
minutes


Registry/Repository

8:30 a.m.
--

60
minutes



Report from the MTF


10:30 a.m.
--

90 minutes


MTF Working Session

1:00 p.m.


90
minutes


Sunday

MTF Working Session

8:00 a.m.
--

90
minutes


Identify and Prioritize Near Term
Projects

10:00 a.m.


60
minutes


Review of Action Items and Next
Steps

11:00 a.m.


60
minutes


Plans for next meeting