Page History

By Feb. 1

Finalize review team - Determine registries subgroup members, agree on review process.

2/1-2/8

Agree

on

evaluation

questions,

set

review

taskforce

meeting

times

2/29

-

3/30

Review

ID

Match

options

(review

high

level

strawman

proposal

Benn

already

developed,

evaluate

OpenEMPI\

as

option

for

OSIdM4HE

ID

Match,

make

recommendation

about

next

steps

(write

new

app,

agree

on

strawman

for

high

level)

3/30

-

4/15

Agree

on

investment

structure

for

ID

Match

4/16

-

6/15

Write

ID

Match

code

or

develop

reference

implementation

with

OpenEMPI

6/16

-

8/15

Testing,

bring

up

as

parallel

service

at

UCSF

3/30-4/15

Plan

investment

structure

for

Registry

2/10

-

2/24

PSU,

OR,

and

KIM

respond

to

evaluation

questions

2/25

-

3/9

Evaluation

team

reviews

responses,

generates

more

detailed

questions

to

be

addressed

during

code

review

3/12

-

3/16

Code

review

of

PSU

Registry

3/19

-

3/23

Code

review

of

OpenRegistry

(Rutgers)

3/26

-

3/30

Review

KIM

registry

3/31

-

4/15

Develop

Registry

recommendation

for

OSIdM4HE