LexEVS Meeting Minutes - Value Set Architecture Planning Session - 2017.01.09

Attendees

Follow up value set workflow questions for Rob.

Review Value Set workflow process (Rob)

As part of the existing Value Set workflow process:

Discussion Points:

Rob indicated that that following tasks are completed in his workflow:

Remove resolved value set script - This removes all existing value set coding schemes
Remove definitions script is generated
Load definitions script is generated (based on a flag)
Script to resolve all 770 value set definitions is called
- This takes 2.5 days.

The following files and scripts are created as part of the workflow:

Value Set Definition XML file: The only parts that change programmatically are:

Neoplasm.xml has a different association:

NCI Report Writer

FDA, CDISC
Creates an XLS report file
Generating these reports
- Takes about 10 minutes
- Uses NCI coding scheme, not the resolved value set
- Released files are on the FTP site
Codebase: github.com/NCIEVS/nci-report-writer

Decision Points:

Investigate concept and subset - look at applying transitive closure here.
Determine if the Value Set Definition XML file is needed and consequences of removing it from their workflow.
Investigate loading resolved value sets - more than one at a time
- Use a Java process instead of a script.

Priority	Issue
1	Investigate ability to be able to determine if Resolved VS coding scheme has changed.
1	Investigate ability to update as needed (not have to load all 700 at the same time). Decrease time it takes to publish/deploy.
2	Investigate ability to be able to determine if Value Set Definition has changed.
2	Investigate ability to capture "Hierarchal Value Sets" as coding schemes with hierarchy. (inside value set)