WO1999018502A1 - Method for data communication involving message files created by standard-compliant equipment - Google Patents
Method for data communication involving message files created by standard-compliant equipment Download PDFInfo
- Publication number
- WO1999018502A1 WO1999018502A1 PCT/US1998/019853 US9819853W WO9918502A1 WO 1999018502 A1 WO1999018502 A1 WO 1999018502A1 US 9819853 W US9819853 W US 9819853W WO 9918502 A1 WO9918502 A1 WO 9918502A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- standard
- compliant
- message file
- network access
- operatively connected
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Definitions
- This invention relates generally to electronic communication of medical-related information between geographically-remote user sites, and particularly to the transmission of medical images and related information originally formatted in an equipment interface standard via a communication pathway using network access devices (NADs) capable of simulating the operation of the corresponding standard-compliant equipment.
- NADs network access devices
- each manufacturer of diagnostic or imaging equipment traditionally utilized a proprietary format or protocol, and custom interfaces were required to permit equipment from different vendors to connect to the same network or medical information management system.
- each manufacturer of display equipment, workstations, archiving or storage systems, and output devices utilized different protocols and interfaces, and data being input to or output from a medical information management program required extensive filtering and reformatting to be compatible with other peripherals or databases.
- DICOM Digital Imaging Communication In Medicine
- NEMA National Electrical Manufacturers Association
- DICOM defines the interface which permits any DICOM-compliant medical imaging device or related equipment or computer system to communicate directly with one another and exchange medical images or data.
- DICOM serves as a specification which manufacturers use when designing a product, and has two levels of application: connectivity (message exchange standards responsible for establishing connections and exchanging properly structured messages so an information object sent by one application will be completely received by another) and interoperability (the ability to process and manipulate those medical images or objects).
- DICOM defines several image objects on which certain "services" can be performed or applied. These services form the basis for DICOM-compliant applications for medical images transmitted between devices, although DICOM does not standardize the underlying image acquisition parameters themselves. Connectivity between two pieces of equipment is evaluated via a "conformance statement" defining or describing the data format and image handling capabilities of the receiving device. The conformance statement also conveys some (but not all) of the information relevant to interoperability, and consequently "plug-and-play" capabilities between two devices cannot be ensured by the DICOM Standard at the interoperability level except for very simple applications.
- DICOM Standard has proven useful for communicating medical images and related data between directly linked image-acquisition and image-processing devices, its compliance requirements can restrict the options available for transmitting medical images or data between remote locations in a generic format capable of cross-modality use or manipulation by a recipient, or via conventional wide bandwidth data transmission pathways (i.e., proprietary pathways, WANs, the Internet, and so forth) that involve steps such as encryption, fragmentation, serialization, remote archiving, or appending transmission, routing, tracking, or commerce-support information to the file.
- Data or medical images are also transmitted as discrete objects, rather than grouped together as complete patient files or electronic envelopes containing data of distinct types, sizes, data depths, acquisition or transmission parameters, and so forth.
- a destination DICOM device may itself only be open to receiving strictly-formatted DICOM messages, and may "block" the transmission of any message that is not a strictly-formatted DICOM message to any subsequent personal computer or user connected on that network path.
- the present invention provides a method to deliver DICOM message files between geographically remote locations from one DICOM compliant device to another utilizing conventional transmission pathways without requiring a direct link between those DICOM devices.
- it provides a method to deliver DICOM message files from a DICOM compliant device to a non-DICOM recipient for subsequent use or manipulation of associated medical images and data.
- a store-and-forward process is used while emulating the DICOM association dialog between the originating and receiving sites.
- the originating site transmits a DICOM message file that is received by a network access device (NAD) located at or reasonably near the originating site, and the NAD simulates the presence and configuration of a selected DICOM compliant device.
- NAD network access device
- the NADs may serve as gateways or filters so that messages may be transmitted to or shared by DICOM devices which would not otherwise be capable of directly communicating with one another, to the extent that partial or complete image content can be interpreted by a DICOM device if supplied by the NAD with appropriate DICOM formatting instructions.
- Packaging is added to the DICOM message file for transmission over a suitable pathway, and the resultant file is then sent across the pathway to a destination site's NAD.
- the destination site's NAD simulates the presence and configuration of a selected originating DICOM device in order to open an association with the ultimate destination DICOM device (or recipient's software application) and deliver the complete DICOM message plus any other relevant data incorporated into the package or file.
- the simulation actions are transparent to both DICOM devices. It may be appreciated by those skilled in the art that the system and method of this invention permits transmission of DICOM-formatted messages between dedicated DICOM- compliant devices via a variety of alternate network connections which include any suitable transmission pathway.
- the system permits connecting DICOM-compliant devices to a local area network (LAN) without blocking or interrupting the flow of DICOM and non- DICOM data on that LAN, and permits workstations, personal computers, and peripheral devices to be connected in series or parallel with DICOM-compliant devices which are capable only of sending or receiving strictly-formatted DICOM messages.
- LAN local area network
- Some of the additional features and advantages of this system and method include the capability to implement DICOM across a normal wide area network (WAN).
- Direct connection of DICOM devices across a WAN can tie up the originating work station during the time it takes to send data and wait for confirmation.
- the data is transferred to the originating NAD across the LAN at LAN speeds, thereby freeing the workstation, the professional using that workstation, and possibly the workstation's storage resources in a more time-efficient manner.
- Ultimate destination devices do not have to be "up” or operational at all times for messages to be transmitted, due to the store and forward process facilitated by the NAD connections.
- This structure allows DICOM message files to be stored at either the originating NAD or the destination NAD.
- the conventional "point-to-point" configuration requires the originating DICOM site to poll the destination DICOM site periodically to determine when the destination becomes active. While the destination DICOM site is inactive, the corresponding workstation storage resources are also unavailable. Only after the destination DICOM site becomes active can the sending process be initiated and the storage resources utilized.
- the system and method of this invention negates these limitations or deficiencies at both the origination and destination sites.
- DICOM devices can only open one association at a time. In other words, one DICOM device can talk to one and only one other DICOM device at a given instant. If a
- DICOM message file needs to be sent to multiple locations — for example, an archive and a consulting physician — the sending process must be performed multiple times.
- DICOM messages can be routed in any manner desired, including secure or private single destinations, multiple or batch- processed transmissions to one or more sites, publish-to-many-site transmissions, or combinations thereof. Grouped message files can be separated or divided and forwarded to the appropriate recipients according to operator instructions, or predetermined routing codes entered into a database associated with the originating or recipient NAD or as a service provided by the operator of the transmission pathway.
- the operator of the transmission pathway can provide adjunct services, such as off-site archiving, encryption, billing, and a variety of other services.
- a related advantage is that multiple workstations at a medical site can simultaneously open an association with the originating NAD. This increases efficiency by eliminating the bottleneck which occurs in point-to-point applications. Thus, none of the workstations are waiting for another workstation to: (1) establish an exclusive link to the DICOM device, (2) complete their sending or receiving process, or (3) terminate their exclusive link.
- a commercial transaction-tracking or verification service can scan the DICOM message for selected elements, thus providing an entirely distinct method for monitoring imaging costs or equipment usage by medical institutions, insurers, and other users. Resources such as tracking or billing capabilities and verification services operate without slowing message transfer rates, and are transparent to users.
- the system also provides a heightened level of security for verifying image integrity, archiving and retransmitting images, and preventing network tampering. If desired, individual destination locations can be locked in or out — thus preventing inadvertent or unauthorized transmissions to other locations, or dictating that certain transmissions only go to a specified destination — to safeguard patient confidentiality and enhance administrative oversight.
- the system also permits a greater degree of flexibility and customization regarding security and oversight. Security may be implemented individually on a message- by-message basis, or depending upon factors or criteria such user identification, patient classification, message content, departmental or organizational distinctions, or other levels or schemes as may be desired by a particular facility or network administrator.
- Figure 1 is a diagram of a basic communication pathway between two DICOM- compliant devices serving as sender and recipient of a formatted message, with originating and destination network access devices (NADs) simulating operation of the sender and recipient devices; and
- NADs network access devices
- Figure 2 is a diagram showing a more complex communication pathway than that of Figure 1, with multiple recipient sites and additional post-transmission devices or applications.
- an originating DICOM device 12 is operatively and sequentially connected to an originating network access device (NAD) 14, a wide area network (WAN) 16 or other electronic communication or transmission pathway of any type conventionally known or hereafter developed, a destination NAD 18, and the destination DICOM device 20.
- the originating NAD 14 simulates any one of many receiving DICOM devices 20, and the destination NAD 18 simulates any one of many originating DICOM devices 12.
- a peripheral device 22 such as a workstation or personal computer can similarly be connected to the originating NAD 14 or the destination NAD 18 via a network (LAN) connection at the corresponding site.
- the peripheral device 22 may be connected directly to the NAD 14, 18 in parallel with the corresponding DICOM device 12, 20, or in series with that DICOM device 12, 20.
- the peripheral device 22 or the DICOM device 12, 20 may be the intermediate in a series connection, but where a personal computer or workstation is the peripheral device 22, it is preferably the intermediary connected directly to the NAD 14, 18.
- One or more DICOM devices 12, 20 physically situated either proximately or remotely relative to the NAD 14, 18 may be operatively connected to that NAD 14, 18 using a LAN, WAN, or other connection that is suitable and appropriate for the particular facilities, uses, and circumstances.
- the ratio of DICOM devices 12, 20 to NADs 14, 18 may be 1 :1 or nearly 1 :1, or several DICOM devices 12, 20 located at physically remote locations within a single complex, at adjacent facilities, or even spread around a region such as a campus or small town can share a single NAD 14, 18.
- the DICOM standard specifies that the data stream is a value representation of all the patient information including images "as is.”
- the original DICOM message file from the originating DICOM device 12 is kept intact as it is processed through the originating NAD 14 and transmitted via the pathway 16, however a "packaging layer” or “electronic envelope” is added that provides transportation cues, display information, database field information, and any other applications or functionality dictated by the transmission system.
- a packetaging layer or "electronic envelope” is added that provides transportation cues, display information, database field information, and any other applications or functionality dictated by the transmission system.
- Applications are added to specify ultimate source and ultimate destination information, as well as other relevant information regarding content or transmission instructions.
- Information needed to open the association is captured and validated against predetermined criteria, and may be modified, appended, or replaced as desired (for example, by the service provider 24) to accomplish intended results regarding the message transmission or receipt, device compatibility, security, transaction processing, and so forth.
- the transfer syntax (specifying information such as the level of service class: Network Image Transfer, Network Print Management, etc.) is captured to negotiate an association with the receiving endpoint, whether it is the destination DICOM device 20, terminal, personal computer, or peripheral device.
- the system 10 also captures all information that deals with the format of the data in order to deliver the display parameters to the ultimate destination DICOM device 20.
- the system 10 scans the DICOM message for data in selectable DICOM elements.
- the data in these elements are logged to a transaction history data file associated with the current DICOM message data set being transferred. This data can be used to provide billing based on some variable such as total megabytes transferred, or megabytes per patient ID, per insurance provider, per modality, per department, and so forth. Any one or multiple DICOM elements can be selected, and private data elements are similarly supported by adding them to the scan list.
- multiple originating DICOM devices 12 may be connected to one or more originating NAD 14 at the sender's location, either independently or through a LAN, and the originating NAD 14 may also serve as or be incorporated into a connection to other elements of the LAN such as workstation terminals, personal computers, and a variety of peripheral devices 22 for data storage, image display, printing or plotting, and so forth.
- the originating NAD 14 may be operatively connected via the transmission pathway 16 to an unlimited number of destination NADs 18, each of which may operatively connected to a destination DICOM device 20 or to other peripheral devices 22.
- a group of message files or objects such as medical images or patient data (designated a, _>, c, d,...) may be obtained from several originating DICOM devices 12 through one originating NAD 14, and subsequently transmitted to and received by separate destination NADs 18 and distinct destination DICOM devices 20 or peripheral devices 22.
- Each destination NAD 18 also serves as an originating NAD 14 for messages transmitted in the opposite direction, and any pattern or array of file message source and recipient sites may be accommodated.
- Message files may be transmitted singularly, in bulk transmissions to one site, or in a publish-to-many-sites format.
- DICOM devices 12 representing exemplary modalities (film digitizer, digital radiography unit, scanner, and ultrasound) all can open associations with the first originating NAD 14. Originating NAD 14 sends the data across the transmission pathway 16 to the DICOM devices 20 or peripherals 22 representing distinct exemplary modalities associated with the second and third destination NADs 18. Associations are opened between the destination NADs 18 and their associated destination peripherals 22.
- the file a from the film digitizer 12 goes to the archive 22 at the third destination NAD 18, the file b from the digital radiography unit 12 goes to the viewing station 22 at the third destination NAD 18, the file c from the scanner 12 goes to the 3-D display 22 at the second destination NAD 18, and the file d from the ultrasound imaging device 12 also goes to the viewing station 22 at the second destination NAD 18.
- the film digitizer 12, digital radiography unit 12, scanner 12, and ultrasound imaging device 12 may be strictly-formatted DICOM-compliant devices 12, or alternately may be peripherals 22 attached to the originating NAD 14 which received DICOM-formatted message files (such as medical images) directly from a DICOM device 12 or via another source.
- the archive 22, viewing station 22, and 3-D display 22 may be peripheral devices 22 capable of receiving DICOM-formatted message files (such as medical images) in addition to non-DICOM messages, or strictly-formatted DICOM-compliant devices 12 capable of receiving only DICOM-formatted message files.
- a service provider 24 may connect to the network pathway 16 to access the NADs 14, 18, as well as to control or monitor the transmission of message files.
- the service provider 24 may perform a wide variety of functions in addition to establishing, operating, and managing the communications pathway 16 (in the case of a proprietary or dedicated pathway 16), such as routing message files, archiving images and patient data, and tracking and billing expenses for the use of equipment 12 or the transmission of message files.
- the service provider 24 may accomplish tracking and billing functions by scanning the packaged message or electronic envelope as it is transmitted via the network pathway 16, or the originating NAD 14 or destination NAD 18 may be capable of scanning relevant information from outgoing or incoming message files and storing that information in a database for later acquisition by the service provider 24 or an operator on the associated LAN.
- the transmitted message files may be archived at the NAD 14, 18 sites, or in a remote location, such as the facility of the service provider 24, with billing or tracking information appended to the files or culled from the archived files for later processing. What is claimed is:
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP98948465A EP1025495A1 (en) | 1997-10-02 | 1998-09-23 | Method for data communication involving message files created by standard-compliant equipment |
AU95033/98A AU9503398A (en) | 1997-10-02 | 1998-09-23 | Method for data communication involving message files created by standard-compliant equipment |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US94003797A | 1997-10-02 | 1997-10-02 | |
US08/940,037 | 1997-10-02 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1999018502A1 true WO1999018502A1 (en) | 1999-04-15 |
Family
ID=25474115
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1998/019853 WO1999018502A1 (en) | 1997-10-02 | 1998-09-23 | Method for data communication involving message files created by standard-compliant equipment |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1025495A1 (en) |
AU (1) | AU9503398A (en) |
WO (1) | WO1999018502A1 (en) |
ZA (1) | ZA988844B (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001099407A1 (en) * | 2000-06-22 | 2001-12-27 | Radvault, Inc. | Medical image management system and method |
US6678703B2 (en) | 2000-06-22 | 2004-01-13 | Radvault, Inc. | Medical image management system and method |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5581558A (en) * | 1995-03-29 | 1996-12-03 | Lucent Technologies Inc. | Apparatus for bridging non-compatible network architectures |
US5786770A (en) * | 1995-06-02 | 1998-07-28 | Dsc Communications Corporation | Message handling in a telecommunications network |
US5802285A (en) * | 1992-05-29 | 1998-09-01 | Icl Personal Systems Oy | Wide area network (WAN) interface for a transmission control protocol/internet protocol (TCP/IP) in a local area network (LAN) |
US5822563A (en) * | 1993-12-31 | 1998-10-13 | Bull S.A. | Process for simulating a server architecture from a client architecture |
US5835735A (en) * | 1995-03-03 | 1998-11-10 | Eastman Kodak Company | Method for negotiating software compatibility |
US5838948A (en) * | 1995-12-01 | 1998-11-17 | Eagle Design Automation, Inc. | System and method for simulation of computer systems combining hardware and software interaction |
-
1998
- 1998-09-23 EP EP98948465A patent/EP1025495A1/en not_active Withdrawn
- 1998-09-23 WO PCT/US1998/019853 patent/WO1999018502A1/en not_active Application Discontinuation
- 1998-09-23 AU AU95033/98A patent/AU9503398A/en not_active Abandoned
- 1998-09-28 ZA ZA988844A patent/ZA988844B/en unknown
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5802285A (en) * | 1992-05-29 | 1998-09-01 | Icl Personal Systems Oy | Wide area network (WAN) interface for a transmission control protocol/internet protocol (TCP/IP) in a local area network (LAN) |
US5822563A (en) * | 1993-12-31 | 1998-10-13 | Bull S.A. | Process for simulating a server architecture from a client architecture |
US5835735A (en) * | 1995-03-03 | 1998-11-10 | Eastman Kodak Company | Method for negotiating software compatibility |
US5581558A (en) * | 1995-03-29 | 1996-12-03 | Lucent Technologies Inc. | Apparatus for bridging non-compatible network architectures |
US5786770A (en) * | 1995-06-02 | 1998-07-28 | Dsc Communications Corporation | Message handling in a telecommunications network |
US5838948A (en) * | 1995-12-01 | 1998-11-17 | Eagle Design Automation, Inc. | System and method for simulation of computer systems combining hardware and software interaction |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001099407A1 (en) * | 2000-06-22 | 2001-12-27 | Radvault, Inc. | Medical image management system and method |
GB2382701A (en) * | 2000-06-22 | 2003-06-04 | Radvault Inc | Medical image management system and method |
US6678703B2 (en) | 2000-06-22 | 2004-01-13 | Radvault, Inc. | Medical image management system and method |
Also Published As
Publication number | Publication date |
---|---|
ZA988844B (en) | 1999-06-30 |
EP1025495A1 (en) | 2000-08-09 |
AU9503398A (en) | 1999-04-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10419405B2 (en) | Systems and devices for encrypting, converting and interacting with medical images | |
US11735312B2 (en) | Systems and methods for converting and delivering medical images to mobile devices and remote communications systems | |
US6574742B1 (en) | Method for storing and accessing digital medical images | |
US11818107B2 (en) | Systems and devices for encrypting, converting and interacting with medical images | |
US20070124310A1 (en) | Distributed Computing System to Enable the Secure Exchange of Information Between Remotely Located Healthcare Applications | |
EP2862327B1 (en) | Systems and devices for encrypting, converting and interacting with medical images | |
US20160037057A1 (en) | Systems and devices for encrypting, converting and interacting with medical images | |
US20080208757A1 (en) | Systems and Methods for Processing Claims in Real-Time | |
WO2005083620A2 (en) | A system and method for processing audit records | |
US20030188200A1 (en) | Processes, apparatus and systems for secure messaging | |
KR20170085496A (en) | Systems and methods for encrypting, converting and interacting with medical images | |
US20090157837A1 (en) | Ndma socket transport protocol | |
US20070223793A1 (en) | Systems and methods for providing diagnostic imaging studies to remote users | |
Robertson et al. | Hospital, radiology, and picture archiving and communication systems | |
US20050257257A1 (en) | Method and apparatus for two-way transmission of medical data | |
US11948678B2 (en) | Systems and devices for encrypting, converting and interacting with medical images | |
EP1025495A1 (en) | Method for data communication involving message files created by standard-compliant equipment | |
Levine et al. | Challenges encountered while implementing a multivendor teleradiology network using DICOM 3.0 | |
US20020035634A1 (en) | Data exchange method and communication protocol used during same | |
Moore et al. | Workstation acquisition node for multicenter imaging studies | |
Toussaint et al. | Should allocation of functions between HIS/RIS and PACS be standardized? |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
NENP | Non-entry into the national phase |
Ref country code: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1998948465 Country of ref document: EP |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
WWP | Wipo information: published in national office |
Ref document number: 1998948465 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1998948465 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: CA |