• Aucun résultat trouvé

The Role of MetaData in Querying Grid-Resident Medical Images

N/A
N/A
Protected

Academic year: 2022

Partager "The Role of MetaData in Querying Grid-Resident Medical Images"

Copied!
25
0
0

Texte intégral

(1)

The Role of MetaData in Querying Grid-Resident Medical Images

Tamás Hauer

University of West England – CERN

IST Workshop on Metadata Management in Grid and P2P Systems 16th December 2003

(2)

Outline

¾ The MammoGrid project

¾ Meta-Data and domain ontology (flexibility)

¾ Meta-Data, services and grid (openness)

¾ Query negotiator

¾ Outlook

(3)

Outline

¾The MammoGrid project

¾ Meta-Data and domain ontology

¾ Meta-Data, services and grid

¾ Query negotiator

¾ Outlook

(4)

The MammoGrid Project

¾

A grids solution for mammography

¾

EU-funded, 2002-2005

– CERN, Mirada Solutions

– Universities: UWE, Oxford, Pisa, Sassari

– Hospitals: Addenbrookes (Cambridge), Policlinico Universitario, Udine

¾

Proof-of-concept R&D:

– Grid + medicine

– Pan-European distributed X-ray image database – Possible target areas:

• Education

• Quality control

• Epidemiology research

• Standardized screening

• Communication aid

(5)

GRID

Federated System Solution

Hospital Italy

Healthcare Institute

University Database

Hospital UK

Shared meta-data Analysis-specific data

•Knowledge is stored alongside data

•Active (meta-)objects manage various versions of data and algorithms

•Small network bandwidth required

Clinician’s Workstations Query

Result Local

Query

Local Analysis Local

Analysis

Local Analysis Local

Analysis

Massively distributed data AND distributed analyses

Local Query

Local Query

Local Query

(6)

Outline

¾ The MammoGrid project

¾Meta-Data and domain ontology

¾ Meta-Data, services and grid

¾ Query negotiator

¾ Outlook

(7)

The Medical Domain

¾ Requirements:

– User community:

• process-oriented rather than information-oriented

• Heterogeneous (technician, radiologist, researcher,…)

– Research area Æhard-to-predict requirements – Regional differences

– Constantly changing knowledge-base

Flexibility, Extensibility is top priority Management of domain information Flexibility, Extensibility is top priority Management of domain information

(8)

The Medical Domain

¾ Entities

– Patients, Physicians, Hospitals, Equipment, … – Medical History (Drugs, Surgery, Pregnancy,…) – Studies, Images, Pathology results, …

– Annotation, Diagnosis, Treatment, …

– Treatment protocol, screening, … (workflow)

– Epidemiological study, research, …

(9)

The Medical Domain

Patient X

History At Present Performed

Study

Mother’s breast cancer

Three pregnancies

On Hormone Replacement

Weight=60kg

Smoking

Four Mammograms

Annotation:

lump in right breast

Diagnosis:

Possible cancer

Treatment:

Lumpectomy

Define semantics so that elements are queriable Bridge discrepancies between different standards

Associations between pixel data of digitized images and structured information Extension to other

modalities

CAD, “Find-one-like-it”

(10)

The Medical Domain

Typical workflow:

1. Register patient, scan image, add pathology data

2. Run SMF to bring image(s) to standardized format (possibly automatic)

3. Annotate image (define location, nature, size, etc… of finding(s) )

4. Run CAD

5. Define relationship between findings (temporal, spatial and pathological)

6. Write assessment of image, series, study. Associate to findings

(11)

The Medical Domain

Image Centric Approach:

•Digitized images (e.g. raw file)

•Semistructured information about the image

•Associate non-derived information (make it useful and interesting)

Image Derived Data:

Size, colormap…

CAD, SMF

Associated Data:

Patient, Study, Equipment, … Related Images

Annotation, Diagnosis, …

Meta-Data:

Semantics of derived Entities

Meta-Data:

Storage format, …

Meta-Data:

Semantics of the associated Entities

Meta-Data: semantics of derivations and relationships

•Describe the image format

•Define “classes” of derived and associated information

•Describe the relationships between the entities (of a record, of records)

(12)

Outline

¾ The MammoGrid project

¾ Meta-Data and domain ontology

¾Meta-Data, services and grid

¾ Query negotiator

¾ Outlook

(13)

Meta-Data, services and grid

¾ Requirements:

– Data heavy (20MB/image) – storage, bandwidth – CPU heavy (image processing: CAD, SMF,…) – Geographically distributed, inhomogeneous,…

– “Plug-and-play” Æ discovery – Scalability, adaptability

– Confidentiality

•Service-oriented architecture

•Use grid-middleware

•Service-oriented architecture

•Use grid-middleware

(14)

Cambridge Hospital Udine Hospital

Oxford University

CERN

Meta-Data services and grid

Udine Hospital:

•I store mammograms

•You can talk to me via SOAP or DICOM

•I can run algorithms (CAD) for you

•You need to use XXX authentication format (so that I can verify your site and country)

•I authenticate myself with XXX or YYY format

•You can subscribe to …

Meta-Data describes service definition

(15)

Cambridge Hospital Udine Hospital

Oxford University

CERN

Meta-Data services and grid

Oxford University:

•I do not have storage

•I understand SOAP only

•I authenticate myself with XXX or YYY format

Meta-Data describes service

definition

(16)

Cambridge Hospital Udine Hospital

Oxford University

CERN

Meta-Data services and grid

(17)

Meta-Data services and grid

Grid metadata defines service ochestration mechanisms.

Follows OGSA specification Implements OGSI:

•Service handles

•Lifetime management

•Represents agreements

Grid data services:

Data Virtualization Grid Data Interfaces

•DataDescription

•DataAccess

•DataFactory

•DataManagement

Implemented by Data Services

•Flexible: plug-and-play system: each participant is responsible for managing its own metadata and can change its service description on-the-fly.

•Extensible: New sites can seamlessly join.

•Domain and Service ontology are defined independently

(18)

Outline

¾ The MammoGrid project

¾ Meta-Data and domain ontology (flexibility)

¾ Meta-Data, services and grid (openness)

¾Query negotiator

¾ Outlook

(19)

Query Negotiator

¾ Issues

– Data location, discovery – Query caching

– Bandwidth, network, etc.

– Do I need to run an algorithm for this?

? ?

¾ What belongs to the negotiator?

(20)

Query Negotiator

Client Query

Translator

Query Handler

Result Handler

User’s Terms

&

Domain MetaData

Local Database

Stored Query Database

(21)

Query Negotiator

Client Query

Translator

Query Analyzer

Local

Query Handler

Remote Query Handler

Result Handler

User’s Terms

&

Domain MetaData

Local Database

Stored Query Database

GRIDGRID

(22)

Query Negotiator

Query Translator

Query Analyzer

Local Query Handler

Remote Query Handler

Result Handler

Query Translator

Query Analyzer

Local Query Handler Remote

Query Handler

Result Handler GRID

(23)

Outline

¾ The MammoGrid project

¾ Meta-Data and domain ontology (flexibility)

¾ Meta-Data, services and grid (openness)

¾ Query negotiator

¾Outlook

(24)

Outlook

¾ Within the Mammogrid project we focus on three distinct areas where active metadata management is useful

¾ These provide key features such as flexibility, extensibility and efficiency

¾ The three meta-data management facilities work in an

orchestrated fashion to define the overall characteristics of the Mammogrid system.

¾ Later it will be interesting to define interfacing two grid- enabled projects (Mammogrid and eDiamond?)

¾ To that end it might turn out that there is room for a further meta-layer which defines (and unifies) our three (and

possibly more) meta-data concepts.

(25)

Thank You

Tamas.Hauer@cern.ch

Références

Documents relatifs

We aimed to perform histological comparison of muscle and tendon fibres taken from fresh cadavers (FC), formaldehyde- preserved cadavers (FPC) and Thiel’s embalmed cadavers, with

Because of this shared need of all extension approaches, we advocate that designers of the ”host” extended plug-in appear as good candidates to identify and provide these

We contend that such research could provide a set of guidelines that can be adopted by organisations in order to offer their employees a structured way to deal

Vertical strong ties bring direct support and solidarity, resulting in improved access to resources and priority over other projects; sparseness provides exposure to the full range

Cette capacité d’adaptation contribue à la durabilité de l’exploitation en lui permettant de composer avec un contexte variable, mais constitue également un élément de plus

The purpose of mastering the discipline is to form students ' systemic knowledge in the field of com- puter technology, informatization of medical activities, automation of

The semantic information model is fitted to the needs of information management in the domain of Technical Service and has been successfully used in a number of industrial

Having in mind previous experience in information system development, and facing the constantly rising number of requested data collection forms and reports we tried two