Application framework of objects for the provision of DICOM services

• US 5,668,998 A
• Filed: 04/26/1995
• Issued: 09/16/1997
• Est. Priority Date: 04/26/1995
• Status: Expired due to Term

• Current Assignee: CareStream Health Incorporated
• Original Assignee: Eastman Kodak Company
• Inventors: Zimmerman, Betsy Ann, Mason, Donald
• Primary Examiner(s): Oberley, Alvin E.
• Assistant Examiner(s): Richey, Michael T.
• Application Number:
  US08/429,397
• Time in Patent Office: 874 Days
• Field of Search: 395/680, 395/683, 395/702, 395/701, 395/924
• US Class Current: 717/104
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: Y10S 706/924 Medical

Abstract

A application program interface is provided to a toolkit framework of service objects which enable rapid creation of application computer programs which implement the services and protocol of the Digital Imaging and Communication in Medicine (DICOM) standard. A framework of service objects is provided which enables a programmer to easily develop application methods which provide DICOM services or other custom services. An object-oriented application interface is provided. The service objects provide a familiar connection between the familiar DICOM standard service objects and a group of associated methods within the framework. The associated methods work together to provide a DICOM service. Service Class User and Service Class Provider objects manage service object communications and are derived from baseclasses in the framework.

Claims

1. A method for creating application programs that provide DICOM services on a computer comprising the steps of:

(a) providing a framework of service objects mapped to a DICOM standard;

(b) providing a baseclass for each service object in the framework;

(c) deriving a plurality of related service objects from the framework;

(d) providing a service handler and service provider for each derived service object;

(e) providing an application interface to the framework of service objects;

(f) accepting from the application interface a request for service request to generate an application program to provide the requested service;

(g) determining a set of related objects to perform the requested service;

(h) providing a first mapping from the related service objects to a set of methods which perform a selected service;

(i) providing a DICOM service by invoking the execution of the related objects selected by the mapping; and

(j) providing a unique association between the service handler and the service provider;

(k) providing a map between the association and the service handler and the service provider;

(l) providing object-oriented call-backs between the service handler and the service provider; and

(m) sending and receiving messages between the service handler and the service provider over the unique association;

(n) instantiating a service object;

(o) providing a service class provider;

(p) providing a unique association between the service object and service class provider; and

(q) providing a service interface object to encapsulate information and data.

2. The method of claim 1 further comprising the steps of:

(j) providing a transport layer;

(k) providing an association layer;

(l) providing a presentation layer;

(m) providing a service primitives layer; and

(n) providing an information object layer.

3. The method of claim 1 wherein the step of providing an application layer further comprises the steps of:

reading a unique identifier from a service request;

providing a data base containing unique identifier context information;

negotiating a unique context having specific service class provider and service class user roles;

providing a data dictionary; and

validating message elements against the data dictionary.

4. The method of claim 3 further comprising the steps of:

assigning attributes to unique identifiers comprising a mapping between a service request and applications available within the PACS.

5. The method of claim 1 wherein the step of providing an information object layer further comprises the steps of:

validating information object semantics and construction;

setting/getting attributes remotely; and

validating syntax.

6. The method of claim 5 further comprising the steps of:

providing an information model type for each patient root, study root, print/study-only, print session-root, and print session; and

providing an information object type for each basic study descriptor, compute radiography, computed topography, magnetic resonance, nuclear medicine, print session, secondary capture, and ultra-sound.

7. The method of claim 1 further comprising the steps of:

providing a data base implementation base on a user-defined hierarchical information model comprised of DICOM attributes; and

enabling an application to change existing structures and indices.