Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep
Home >> All >> org >> vmdb >> [ hl7 Javadoc ]

• org.vmdb.hl7: Javadoc index of package org.vmdb.hl7.


Package Samples:

• org.vmdb.hl7

Classes:

• ORUMessage: Observation Unsolicited (ORU) Message. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. Message class(es) form the main API for the library. In most cases, there will be simple methods for inserting and extracting values from the message structure as well as for parsing incoming messages or building outgoing messages in either delimited HL7 or the draft XML representation. The Observation Unsolicited (ORU) message is the approved method for submitting data to the Veterinary Medical Database (VMDB). This class implements a subset of the ...
• ORU_R01_GRP_1Loop: Group 1 (ORU_R01_GRP_1Loop) Loop. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The XML representation of HL7 2.x introduces the concepts of groups and lists that, while present in the construction rules of delimited HL7, are not explicitly named or labelled in the messages themselves. This class follows the XML version with explicitly constructed groups and lists which we've combined under the general term (borrowed from X12) of "loop." Most of the repetion and grouping facilitated by this "loop" logic is not used in the VMDB version ...
• HL7Message: Generic HL7 Message Structure. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. This almost virtual base class provides the common structure and functionality for all implemented specific messages. By using this class directly it is possible to build messages of types not yet implemented, but at considerably greater effort than using an implemented specific class. If you do build specific messages, you are encouraged to construct a specific subclass and submit it to VMDB for inclusion in the library. While you are not required to so extend ...
• HL7Segment: Base Class for All Types of HL7 Segments. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. A segment is a collection of related fields whose positions are specified in the segment rule. The primary function of the base class is to handle the complex processes of parsing and building segments from and to HL7 and XML. Each derived class provides a rule. The base class passes that rule to a RuleParser object which acts as a director with calls back to this object to read the input string, add fields, etc.. The base segment class also provides ...
• ORU_R01_GRP_2Loop: Group 2 (ORU_R01_GRP_2Loop) Loop. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The XML representation of HL7 2.x introduces the concepts of groups and lists that, while present in the construction rules of delimited HL7, are not explicitly named or labelled in the messages themselves. This class follows the XML version with explicitly constructed groups and lists which we've combined under the general term (borrowed from X12) of "loop." Most of the repetion and grouping facilitated by this "loop" logic is not used in the VMDB version ...
• ORU_R01_GRP_3Loop: Group 3 (ORU_R01_GRP_3Loop) Loop. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The XML representation of HL7 2.x introduces the concepts of groups and lists that, while present in the construction rules of delimited HL7, are not explicitly named or labelled in the messages themselves. This class follows the XML version with explicitly constructed groups and lists which we've combined under the general term (borrowed from X12) of "loop." Most of the repetion and grouping facilitated by this "loop" logic is not used in the VMDB version ...
• ORU_R01_GRP_4Loop: Group 4 (ORU_R01_GRP_4Loop) Loop. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The XML representation of HL7 2.x introduces the concepts of groups and lists that, while present in the construction rules of delimited HL7, are not explicitly named or labelled in the messages themselves. This class follows the XML version with explicitly constructed groups and lists which we've combined under the general term (borrowed from X12) of "loop." Most of the repetion and grouping facilitated by this "loop" logic is not used in the VMDB version ...
• ORU_R01_GRP_5Loop: Group 5 (ORU_R01_GRP_5Loop) Loop. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The XML representation of HL7 2.x introduces the concepts of groups and lists that, while present in the construction rules of delimited HL7, are not explicitly named or labelled in the messages themselves. This class follows the XML version with explicitly constructed groups and lists which we've combined under the general term (borrowed from X12) of "loop." Most of the repetion and grouping facilitated by this "loop" logic is not used in the VMDB version ...
• ORU_R01_LST_5Loop: List 5 (ORU_R01_LST_5Loop) Loop. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The XML representation of HL7 2.x introduces the concepts of groups and lists that, while present in the construction rules of delimited HL7, are not explicitly named or labelled in the messages themselves. This class follows the XML version with explicitly constructed groups and lists which we've combined under the general term (borrowed from X12) of "loop." Most of the repetion and grouping facilitated by this "loop" logic is not used in the VMDB version ...
• ORU_R01_LST_7Loop: List 7 (ORU_R01_LST_7Loop) Loop. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The XML representation of HL7 2.x introduces the concepts of groups and lists that, while present in the construction rules of delimited HL7, are not explicitly named or labelled in the messages themselves. This class follows the XML version with explicitly constructed groups and lists which we've combined under the general term (borrowed from X12) of "loop." Most of the repetion and grouping facilitated by this "loop" logic is not used in the VMDB version ...
• ORU_R01_LST_8Loop: List 8 (ORU_R01_LST_8Loop) Loop. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The XML representation of HL7 2.x introduces the concepts of groups and lists that, while present in the construction rules of delimited HL7, are not explicitly named or labelled in the messages themselves. This class follows the XML version with explicitly constructed groups and lists which we've combined under the general term (borrowed from X12) of "loop." Most of the repetion and grouping facilitated by this "loop" logic is not used in the VMDB version ...
• ORCSegment: Order Common (ORC) Segment. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The Common Order segment (ORC) is used to transmit fields that are common to all orders (all types of services that are requested). The premise of the VMDB message is that there is a standing order with all participating facilties to provide visit summary information to the VMDB. Thus, changes to visit information submitted to VMDB is, in fact, a change to the results of the standing order. While this segment is optional for initial transmission of visit summary ...
• OBXSegment: Observation/Result (OBX) Segment. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The OBX segment is used to transmit a single observation or observation fragment. It represents the smallest indivisible unit of a visit summary report. The OBX segment identifies the specific type of observation result being reported (OBX-3) and the specific value of the observation (OBX-5). Reporting to the VMDB focuses on OBX-3 and OBX-5 as the most informative elements of the message and thus, full effort should be made to make OBX-3 and OBX-5 as valid ...
• OBRSegment: Observation Request (OBR) Segment. Description: Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. Now is the time For VMDB reporting, the OBR defines the observations made during the patient visit. These fall into two general categories: physical observations about the patient and impressions concerning the patientŐs condition at the end of the visit. The values for these observations are reported in OBX segments, which are described below. There can be many OBXŐs per OBR, but only one OBR per PV1. Since all of the observations named in this segment are ...
• HL7Loop: Abstract Base Class for HL7 Loop Structures. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. A "Loop" is not really part of the HL7 specification, but it is a very useful concept from X12 and is necessary to properly implement repeatable groups of segments in XML. The Loop does not appear in the HL7 2.4 representation except as {...} groupings in the specification. It appears in the XML representation as <ORU_R01.LST.1>...</ORU_R01.LST.1> type tag pairs with segment tag pairs embedded within. For "formal" description of any ...
• HL7Element: Abstract Base Class for HL7 Data Type Elements. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. HL7 uses data elements in a nested structure of fields sometimes composed of components sometimes composed of subcomponents. The Generic HL7Element class forms the base of all our data type elements. It adds to knowledge of its own level (field, component, or subcomponent) and the machinery to build itself by parsing HL7 input under the direction of a RuleParser.
• RSPMessage: Query By Pattern Response (RSP) Message. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. This is a quickly assembled message type used to demonstrate extensibility of the general library model. A more production ready solution would have been to develope a full, general purpose QBP/RSP pair of messages and extend them to the specific case of the QBP-Z01 defined here, but the point was to show a quick and easy extension example.
• QBPMessage: Query By Parameters (QBP) Message. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. This is a quickly assembled message type used to demonstrate extensibility of the general library model. A more production ready solution would have been to develope a full, general purpose QBP/RSP pair of messages and extend them to the specific case of the QBP-Z01 defined here, but the point was to show a quick and easy extension example.
• MSHSegment: Message Header (MSH) Segment. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The MSH segment defines the intent, source, destination, and some specifics of the syntax of a message. Because this information is needed by the program in order to properly construct the segments that follow, the MSH should be populated before any additional segments are added. See HL7 Standard Chapter 2 for details.
• FNElement: Family Name (FN) Element. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The method names follow the convention established by other Element type classes. Names follow the HL7 documentation. Most of the methods exist only to demonstrate that data modellers have too much time on their hands and need to find day jobs. See the HL7 documentation for an explanation of each component.
• PIDSegment: Patient Identification (PID) Segment. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The PID segment is used as the primary means of communicating information concerning the veterinary patient identification. This segment is required for all VMDB reporting messages. For VMDB usage, only one PID segment per message is allowed. See HL7 Standard Chapter 3 for additional details.
• PV1Segment: Patient Visit (PV1) Segment. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The use of the PV1 segment in VMDB reporting is to provide visit-specific information. This segment is required for all ORU messages and only one PV1 segment may be included in a VMDB message. Only 6 elements in the segment are used for VMDB messages. See HL7 Standard Chapter 3 for details.
• StringList: String List Modified String Tokenizer. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. More or less take over from the StringTokenizer class but with two modifications. First, two sequential tokens result in an empty string rather than no token. Second getIndex and setIndex allow saving and restoring state to allow roll-back of reading from the list.
• SimpleElement: Single Implementation for All Simple HL7 Data Types. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. This one class handles all the data types that consist of a single string. The actual type is set by the calling program with the constructor or setType() method. Validity checking is left to the calling routine.
• XCNElement: Extended Composite ID Number and Name for Persons (XCN) Element. Description: HL7 Network Connectivity For VMDB. Copyright: Copyright (c) 2002-2003. Company: M&M Informatics. The method names follow the convention established by other Element type classes. Names follow the HL7 documentation. See the HL7 documentation for an explanation of each component.

Home | Contact Us | Privacy Policy | Terms of Service