Embed
Email

Transcend_Task_List

Document Sample

Shared by: huanghengdong
Categories
Tags
Stats
views:
1
posted:
12/1/2011
language:
English
pages:
19
Create



Consider Work Location

Do we work the weekend of March 13

Did unused hours from February flow forward, or are they gone.



Design Work



Identify possible reference resources and publish location to team

Layout the detail scenario 3 Bruce/Lorraine/Eric

Detail the Interoperability Spec 4 Lorraine/Bruce

Above task will list all service specs required

for each above spec we need to complete in-scope design 8 Lorraine/Bruce/Clarance



Review potentially available resources/code for any and all sources



Define information for CDA

Identify what information will be pulled from Transcend 4 Jean

Get the TRANSCEND Trims 7 Cecil

Map Transcend to V3 CDA structure Jean

Design transforms to CDA 11 Jean/Andy

Identify / Define CDA Template Parameters for Document Builder Eric

Define Terminology Mapping for templates

Populate required mapping for ontology Cecil



Design method for retrieving information from Tolven Steve/Clarance



Design process for send CDA to target system 9 Ken



Design portal rendering of the CDA off target system Ken



Development Work



Design and Build rendering portal/UI

Duplicate



Inventory existing services with code Clarance



Document Exchange Service Eric/Clarance

Document Builder Service Eric/Clarance

Rendering of CDA on Target System 9 Ken

Terminology Service 8 Eric first task





Patient registry service

Provider registry service

Medication Service

Build Process Steps Clarance

Build Transforms Andy









Integration Work

Frequency of Build and Deployment

Daily Standup meetings Bruce

Integration Build 9

Test 9 Bruce

Move code to NCI SVN on a Daily basis Daily

Migrate to NCI environment 16 Eric has been talking to CDO/Bobby





Infrastructure Work







Get a deployed instance of the Tolven instance of Transcend



4 Cecil/John/Paul/Lorraine

Standup previous POC as starting point 4 Steve / Clarance

Standup instance of Tolven in VM1 4 Steve / Clarance

Standup TRANSCEND application in VM2 8 Steve / Clarance

Standup SVN Instance within Guidewire environment 4 Steve / Clarance



Get current Transcend architecture 3 Paul

Development Tools 4 Clarance

Development Environment 4 Clarance



Set up 2 vm and clone per dev

Identify Cloud Resources required 3 Eric

Acquire and standup Cloud resources 4 Eric









Longer Term Tasks:

interoperability specs

roadmap for service implementation

roadmap for Transcend

roadmap for interaction with caBIG teams



Resources:

Dev

Eric 60% Dev / Arch

Ken Bernstein 100% Dev

Clarance 100% Dev

Steve 100% Dev

Andy 48 hr Dev New to tolven



Arch

John Arch; System Expert; External Communication

Pull in when needed

Lorraine 60% PM; Arch New to POC

Bruce 100% PM New to POC

Jean Duteau 50% Info model New to POC

Cecil Terminology; Domain Expertise; External

Pull in when needed New to POC



Project Mgmt

Eve Inform as required

Kevin Inform as required

Paul Inform / Provide Direction





Risks:

Problems getting Tolven stood up

Problems getting TRANSCEND Information/Architecture/Code/Instance Stoodup

Problem standing up TRANSCEND

Lossing focus of team members

Managing the requests to alter direction / Shift scope.

Gaining access to Data Structures required

Assumes that Transend uses Tolven persistence mechanism i.e. trims

Sleepless Nights

Dilution of Team - Bringing in to many people reduces the likelihood of success for March 17 demo



Assumptions:

vEHR needs to exist so we will not use tolven plugins. Only data retrieval will be done as Tolven plugin.

Review









John/Cecil/Paul Scope may need to be scoped down to just create a CDA with Patient and Chemo/Medicaiton in

John/Eric









Consult with Onto Reason; Guidewire; Others?





Started creating the POC CDA Iguide. (Pathology, Cancer Staging) Jean is blocked until he

Cecil to post Transcend code to SVN as a zip

Jean can create an rough Imp guide









rendering will be to apply the standard style sheet in a web browser









Write a servlet that call Document Exchange ,

render and display the CDA and XML









Probably need to look at what short cuts are required. Eric will suggestions on this for Monday.



Can start this immediately - Display the CDA as human readable and xml dump.

Add simple service onto the Cecil's Owl ontology





Use Dummy just better than previous POC

Use Dummy just better than previous POC

Model off of the POC build process









Is this Maven and Hudson Clarance









king to CDO/Bobby Eric to work on Monday. Likely will have environmentby end of Monday.









This needs to be coordinated so we don't badger

Mike. Needs to include data; Paul to look at

sources, John to talk to Mike Holgrath. / Lorraine

to follow up with Kevin H.

Ken can just turn it back on. It is an Amazon Server





May just be getting access; need to migrate to NCI at end



Paul to send to Links to resources.









Use Centos as VM os; Will take a day or two set tolven instance

Eric can discuss with CDO to get Tolven instances; Like in the Demo Pilot;Need to indentify whe

nd Chemo/Medicaiton info as initial target









Jean is blocked until he can the TRIMS









ons on this for Monday.

ot;Need to indentify where and what is required for demo environment

Create









Design Work







Layout the detail scenario 3 Bruce/Lorraine/Eric

Detail the Interoperability Specs

Enrollment Lorraine/Bruce

On Study Clinical Communication Lorraine/Bruce

PCO Lorraine/Bruce





Above task will list all service specs required

for each above spec we need to complete in-scope design 8 Lorraine/Bruce/Clarance



Review potentially available resources/code for any and all sources



Define information for CDA. Each task will be performed for each of the interoperability specs

Identify what information will be pulled from Transcend 4 Jean

Get the TRANSCEND Trims 7 Cecil

Map Transcend to V3 CDA structure Jean

Design transforms to CDA 11 Jean/Andy

Identify / Define CDA Template Parameters for Document Builder Eric

Define Terminology Mapping for templates

Populate required mapping for ontology Cecil



Design method for retrieving information from Tolven Steve/Clarance



Design process for send CDA to target system 9 Ken



Design portal rendering of the CDA off target system Ken



Development Work



Design and Build rendering portal/UI

Duplicate



Inventory existing services with code Clarance



Document Exchange Service Eric/Clarance

???

State Management

Interface Realization

Document Builder Service Eric/Clarance

Identify Component Information per CDA

Identify Sources

Velocity Script

Interface Realization



Rendering of CDA's on Target System 9 Ken

Terminology Service 8 Eric first task

Patient registry service

Tolven ADT Interface

Exposing Tolven logical Patient Registry

Implement Patient Reg Interface

Provider registry service

Tolven ADT Interface

Exposing Tolven logical Patient Registry

Implement Patient Reg Interface

Authorization Service

???





Identification Service

???





Authorization Service

???









Clarance



Andy

Integration Work

Frequency of Build and Deployment

Daily Standup meetings Bruce

Integration Build 9

Test 9 Bruce

Move code to NCI SVN on a Daily basis Daily

Migrate to NCI environment 16 Eric has been talking to CDO/Bobby





Infrastructure Work

Get a deployed instance of the Tolven instance of Transcend



4 Cecil/John/Paul/Lorraine

Standup previous POC as starting point 4 Steve / Clarance

Standup instance of Tolven in VM1 4 Steve / Clarance

Standup TRANSCEND application in VM2 8 Steve / Clarance

Standup SVN Instance within Guidewire environment 4 Steve / Clarance



Get current Transcend architecture 3 Paul

Development Tools 4 Clarance

Development Environment 4 Clarance



Set up 2 vm and clone per dev

Identify Cloud Resources required 3 Eric

Acquire and standup Cloud resources 4 Eric



caIntegrator Hub Transaction Support

CDA Transaction

Enrollment

On Study I

On Study II

On Study III

PCO

Patient Registry Interactions

Provider Registry Interactions

Document Builder Interactions (???)



Longer Term Tasks:

interoperability specs

roadmap for service implementation

roadmap for Transcend

roadmap for interaction with caBIG teams









Resources:

Dev

Eric 60% Dev / Arch

100%

Ken Bernstein Dev

Clarance 100% Dev

Steve 100% Dev

Andy 48 hr Dev New to tolven



Arch

Arch; System Expert; External Communication

John Pull in when needed

Lorraine 60% PM; Arch New to POC

Bruce 100% PM New to POC

Jean Duteau 50% Info model New to POC

Terminology; Domain Expertise; External

Cecil Pull in when needed New to POC



Project Mgmt

Eve Inform as required

Kevin Inform as required

Paul Inform / Provide Direction







Risks:

Problems getting Tolven stood up

Problems getting TRANSCEND Information/Architecture/Code/Instance Stoodup

Problem standing up TRANSCEND

Lossing focus of team members

Managing the requests to alter direction / Shift scope.

Gaining access to Data Structures required

Assumes that Transend uses Tolven persistence mechanism i.e. trims

Sleepless Nights

Dilution of Team - Bringing in to many people reduces the likelihood of success for March 17 demo



Assumptions:

vEHR needs to exist so we will not use tolven plugins. Only data retrieval will be done as Tolven plugin.

Review









John/Cecil/Paul Scope may need to be scoped down to just create a CDA with Patient and Chemo/Medicaiton in



John/Eric

John/Eric

John/Eric









Consult with Onto Reason; Guidewire; Others?





Started creating the POC CDA Iguide. (Pathology, Cancer Staging) Jean is blocked until he

Cecil to post Transcend code to SVN as a zip

Jean can create an rough Imp guide









rendering will be to apply the standard style sheet in a web browser









Write a servlet that call Document Exchange ,

render and display the CDA and XML









Probably need to look at what short cuts are required. Eric will suggestions on this for Monday.

Can start this immediately - Display the CDA as human readable and xml dump.

Add simple service onto the Cecil's Owl ontology

Use Dummy just better than previous POC









Use Dummy just better than previous POC









Model off of the POC build process









Is this Maven and Hudson Clarance









king to CDO/Bobby Eric to work on Monday. Likely will have environmentby end of Monday.

This needs to be coordinated so we don't badger

Mike. Needs to include data; Paul to look at

sources, John to talk to Mike Holgrath. / Lorraine

to follow up with Kevin H.

Ken can just turn it back on. It is an Amazon Server





May just be getting access; need to migrate to NCI at end



Paul to send to Links to resources.









Use Centos as VM os; Will take a day or two set tolven instance

Eric can discuss with CDO to get Tolven instances; Like in the Demo Pilot;Need to indentify whe

r March 17 demo





one as Tolven plugin.

nd Chemo/Medicaiton info as initial target









Jean is blocked until he can the TRIMS









ons on this for Monday.

ot;Need to indentify where and what is required for demo environment



Other docs by huanghengdong
pozvanka popela 2011
Views: 0  |  Downloads: 0
Making Connections_18_
Views: 0  |  Downloads: 0
20100121125409223
Views: 0  |  Downloads: 0
385-390
Views: 0  |  Downloads: 0
09-uncertainty
Views: 0  |  Downloads: 0
2010Cal
Views: 0  |  Downloads: 0
Schedule by Date September 2011
Views: 3  |  Downloads: 0
supmpr
Views: 0  |  Downloads: 0
Science and our Food Supply video guide
Views: 0  |  Downloads: 0
By registering with docstoc.com you agree to our
privacy policy

You are almost ready to download!

You are almost ready to download!