1 / 14

LIDC Phase 1 Implementation: Need Tracking & Secure Transfer Software

Develop software for tracking work-list, secure transfer, anonymization, marking tools, and XML reading messages for LIDC implementation. Monitor assignments and completion status.

joancollins
Download Presentation

LIDC Phase 1 Implementation: Need Tracking & Secure Transfer Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LIDC Message System: Development for Phase 1 implementation 12 Need tracking software at each site for work-list X 1 Secure transfer in-house to LIDC computer Site anonymization computer A SSH or secure FTP for transfer, with a script developed as required All 4 reads must be received (and at end of unblinded reviews, reconciled) by computer A OtherSubject data fields Linked to case Image send of 1 to computers B,C,D,E 11 2 6 10 Possible NCI based status display program 13 3 7 1 XML Reading Assignment message sent to computers B,C.D,E) (All colors) Denotes tasks to be developed and integrated XML Reading Response Message, With Contour file and review data, Sent back only to sending site, computer A, for each case 3,4,5,6 5 9 4 Marking tools must be available for each computer for radiologist marking (Gray) Denotes Blinded Review tasks 8 B,C,D,E 7,8,9,10 (Yellow) Denotes UnBlinded review tasks Remote “other site” computers

  2. 1. Anonymization • Such as the U. Michigan software • Anonymize • Scrub certain fields • Set others to NULL • See Process Model 2.4 for details

  3. 2. Broadcast Anonymized Image data • In DICOM format • Using rsync or other mechanism

  4. 3. Initial Reading Assignment XML Message (First Blinded Review) • In specified message format • With specified message content • Coded to Identify as Blinded Review • Case id • Reader id • Etc. • Broadcast to Sites B, C, D, E

  5. 4. Blinded Review - Marking Tool • Assigned reader at each site (B, C, D, E) uses review and marking software • Creates Boundaries for Nodules > =3 mm • Marks centroid for Nodules < 3mm • Marks centroid for Non-Nodules > =3mm • Labels each object (Nodule or Non-Nodule) as described in Process Model 2.4 • Software converts boundaries from internal format to LIDC TG-2 specified format in XML

  6. 5. Blinded Review Response XML Message • In specified message format • With specified message content • Coded to Identify as Blinded • Case id, Reader id • Boundary data also in specified XML format • Radiologist Reading CDEs (Labelings, etc.)

  7. 6. Receive Blinded Reviews • Receive Reviews at Originating Site At end of Blinded review • Store Individual Reads in local (Level 1) dB • Create pMap?? • Merge the required number (4) of remote site reviews to create XML file with composite reviews

  8. 7. Unblinded Reading Assignment XML Message • When all required (4) Blinded Reviews have been received and compiled, then • Send Unblinded Reading Assignment Message: • In specified message format • With specified message content • Coded to Identify as UnBlinded Review • Case id • Reader id • Etc. • Transmit Composite Blinded Review Data (created in Step 6) as part of message • Broadcast to Sites B, C, D, E

  9. 8. Unblinded Review - Marking Tool • Assigned reader at each site (B, C, D, E) uses review and marking software • Each Reader sees all markings of all readers (anonymized) • Each Reader sees their own markings uniquely distinguished • Each Reader Creates their own Unblinded Review by Editing their Blinded Review results • Accepting or Rejecting Their own Markings • Accepting or Rejecting the Markings of Others • Allow Editing of Boundaries • Allow Editing of Object Labeling (or Labeling of new objects) • Software converts boundaries from internal format to LIDC TG-2 specified format in XML

  10. 9. UnBlinded Review Response XML Message • In specified message format • With specified message content • Coded to Identify as UnBlinded • Case id, Reader id • Boundary data in specified XML format • Radiologist Reading CDEs (Labelings, etc.)

  11. 10. Receive UnBlinded Reviews • Receive Reviews at Originating Site At end of UnBlinded review • Store Individual UnBlinded Reads in local (Level 1) dB • Perform reconciliation. • Create pMap

  12. 11. Other Subject Data • At other points in time, Site A may enter other data that will be linked to case or nodule: • Pathology (of an individual nodule) • Ethnicity • Smoking History • To be entered at Local (Level 1) database

  13. 12. Monitoring • Software needed at each site to Monitor and help manage: • Each case submitted (by Site A), to track • Reader Assignments • Completion Status • Each Reader (at Site A), to track • Case assignments • Assignment Type (Blinded/Unblinded) • Completion Status

  14. 13. Possible NCI Based Status Reporting • Centralized location to which all messages are sent • Status of all cases centrally displayed

More Related