Versions Compared

Old Version 15

changes.mady.by.user Philip Trevvett

Saved on

compared with

New Version Current

changes.mady.by.user Sam Tsoi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Demo Downloads

Shrine Core Ontology:

https://open.med.harvard.edu/svn/shrine/trunk/-ontology/SHRINE_Demo_Downloads/trunk/ShrineDemo.sql

Adaptermappings for i2b2 Demo Data:

https://open.med.harvard.edu/svn/shrine/trunk/-ontology/SHRINE_Demo_Downloads/trunk/AdapterMappings_i2b2_DemoData.csvhttps://open.med.harvard.edu/svn/shrine/trunk/ontology/SHRINE_Demo_Downloads/AdapterMappings_i2b2_DemoData.xml

Ontology tips, do's and don'ts

No forced formatting through additional text in metadata field C_NAME

  • Most importantly, leading spaces should not be used for forced order of terms, and will result in errors when such terms are included in queries.
  • 1 exception: "zz " can be used as a prefix in C_NAME and will not be displayed.  A term can be forced to appear last in order of appearance by adding prefix  “zz “ to the C_NAME string. This is useful for terms like ‘unknown’ or ‘other’ which may not otherwise appear last in certain demographics categories.

Mapping Ontology to Local Site:

...

  • Ontology navigation for each data element in webclient
  • Ontology search by code in webclient works for each data element
  • Ontology search by name in webclient works for each data element

Test

Action

Ontology navigation for each data element in webclient

Open Webclient, navigate ontology hierarchy for each data-type

Ontology search by code in webclient works for each data element

Search in webclient for each datatype by code of term.  Expected term should return.

Ontology search by name in webclient works for each data element

Search in webclient for each datatype by name of term. Expected term should return.

AdapterMappings Load Checklist

  • Queries should execute with expected mapped/unmapped responses
  • All mapped terms should return patient count for each mapped site
  • Unmapped terms return ‘no mappable local items’

Test

Action

Confirm query returns via small sample test prior to programmatic test

Run sample of basic queries to confirm response

All mapped terms should complete query for each mapped site

Run Scan tool to programmatically test all ontology terms. Compare pre-generated list of mapped local terms to Scan tool results.

Unmapped terms return ‘no mappable local items’

Compare pre-generated list of unmapped local terms to Scan tool results

Data Update Load Checklist:

  • Data/Counts should return for new dates added
  • Counts for old dates should remain consistent
  • Total counts for all dates should increase

Test

Action

Data/Counts should return for new dates added

Execute single term queries with new dates specified.

Counts for old dates should remain consistent

Execute single term queries with previously loaded dates specified. Compare results with previously returned counts (prior to data update).

Total counts for all dates should increase

Execute single term queries with previously loaded dates specified. Compare results with previously returned counts for all dates (prior to data update).