- From: Patrick Stickler <patrick.stickler@nokia.com>
- Date: Fri, 2 Apr 2004 11:38:02 +0300
- To: "ext Dirk Colaert" <Dirk.Colaert@quadrat.be>
- Cc: "'public-rdf-dawg@w3.org'" <public-rdf-dawg@w3.org>
This sounds like "best match", which would require some forumula for ranking alternative results, which may be alot of work. I personally like this use case, and think it definitely reflects real-world needs. I'm just wondering if it's (a) too big to take on and (b) something that needs more research/exploration before standardizing. ??? Patrick On Apr 01, 2004, at 16:11, ext Dirk Colaert wrote: > > > Name: > Physician places an order > > Description: > A physician enters an order for a chest x-ray. He works in a huge multi > campus hospital with multiple radiology departments. > We have an RDF doc describing properties of the departments and > relations > between them. > Example: > -Campus A is a children's hospital > -Radiology department B is part of hospital A > -Radiology department C is specialized in examinations of the type D > -Urgent requests should be handled on the same campus (if > specialization > permits) > -Requesting department E has as first collaboration choice: department > F > -Specialization precedes first choice > -There is a schedule for after work hours > Etc .... > > The poor physician is agnostic of these rules. The only thing he > wishes is > placing his order and see where this examination will be executed, > given the > facts: Patient is child, examination = Chest x-ray and not urgent, > referring > department is 'E', ordering time = today 10 pm, etc... > > I presume the query is not fired by the physician but by a 'routing > engine' > being called by the physician's application. So, maybe the name of the > use > case should be 'routing engine routes order'. > > The result of the query should be a list of departments, sorted on > aptness > to execute the order. > The query should give the constraints and ask for a resolution (no > matter > how complex this system in practice might be) > > This use case shows the need to add constraints in the query and shows > the > need for not only querying for information but also for a resolution > of a > problem (which might be the same thing) > > Hope this helps. > > ___________________________________ > Dr. Dirk Colaert MD > Production, Information Systems Architect > Agfa > HealthCare Informatics > call +32 3 444 84 08 > fax +32 3 444 84 01 > > > -- Patrick Stickler Nokia, Finland patrick.stickler@nokia.com
Received on Friday, 2 April 2004 03:40:05 UTC