add h230, h270, h271

Author: kardianos

coder_test.go

@@ -8,7 +8,7 @@ import (
 	"path/filepath"
 	"testing"
 
-	v25 "github.com/kardianos/hl7/h25"
+	v25 "github.com/kardianos/hl7/h250"
 	v251 "github.com/kardianos/hl7/h251"
 	"github.com/sanity-io/litter"
 )

genjson/HL7v2.3/Chapters/CH_02.json

@@ -0,0 +1 @@
+{"id":"CH_02","title":"Control/Query","description":"The Control/Query chapter of this Standard defines the generic rules that apply to all messages.  Subsequent sections define functionally specific messages to be exchanged among certain applications."}

genjson/HL7v2.3/Chapters/CH_03.json

@@ -0,0 +1 @@
+{"id":"CH_03","title":"Patient Administration","description":"The Patient Administration transaction set provides for the transmission of new or updated demographic and visit information about patients.  Since virtually any system attached to the network requires information about patients, the Patient Administration transaction set is one of the most commonly used. Generally, information is entered into an Patient Administration system and passed to the nursing, ancillary and financial systems either in the form of an unsolicited update or a response to a record - oriented query. "}

genjson/HL7v2.3/Chapters/CH_04.json

@@ -0,0 +1 @@
+{"id":"CH_04","title":"Order Entry","description":"The Order Entry transaction set provides for the transmission of orders or information about orders between applications that capture the order, by those that fulfill the order, and other applications as needed.  An order is a request for material or services, usually for a specific patient.  These services include medications from the pharmacy, clinical observations (e.g., vitals, I&Os) from the nursing service, tests in the laboratory, food from dietary, films from radiology, linens from housekeeping, supplies from central supply, an order to give a medication (as opposed to delivering it to the ward), etc."}

genjson/HL7v2.3/Chapters/CH_06.json

@@ -0,0 +1 @@
+{"id":"CH_06","title":"Financial Management","description":"The Finance chapter describes patient accounting transactions.  Other financial transactions may be added in the future.  Financial transactions can be sent between applications either in batches or online.  As defined in Chapter 2 on batch segments, multiple transactions may be grouped and sent through all file transfer media or programs when using the HL7 Encoding Rules."}

genjson/HL7v2.3/Chapters/CH_07.json

@@ -0,0 +1 @@
+{"id":"CH_07","title":"Observation Reporting","description":"This chapter describes the transaction set required for sending structured patient oriented clinical data from one computer system to another.  A common use of these transaction sets will be to transmit observations and results of diagnostic studies from the producing system (e.g., clinical laboratory system, EKG system) (the filler), to the ordering system (e.g., HIS order entry, physician's office system) (the placer).  However, the transaction set is not limited to such transactions.  Observations can be sent from producing systems to archival medical record systems ( not necessarily the order placer) and from such medical record systems to other systems that were not part of the ordering loop, e.g., an office practice system of the referring physician for inpatient test results ordered by an inpatient surgeon."}

genjson/HL7v2.3/Chapters/CH_08.json

@@ -0,0 +1 @@
+{"id":"CH_08","title":"Master Files","description":"In an open-architecture healthcare environment there often exists a set of common reference files used by one or more application systems.  Such files are called master files. These common reference files need to be synchronized across the various applications at a given site.  The Master Files Notification  message provides a way of maintaining this synchronization by specifying  a standard for the transmission of this data between applications."}

genjson/HL7v2.3/Chapters/CH_09.json

@@ -0,0 +1 @@
+{"id":"CH_09","title":"Medical Records/Information Management","description":"This chapter currently supports document management.  In the future, it is intended also to support the data exchange needs of applications supporting other medical record functions, including chart location and tracking, deficiency analysis, consents, and release of information.  The main purpose of the medical record is to produce an accurate, legal, and legible document that serves as a comprehensive account of healthcare services provided to a patient."}

genjson/HL7v2.3/Chapters/CH_10.json

@@ -0,0 +1 @@
+{"id":"CH_10","title":"Scheduling","description":"This chapter defines abstract messages for the purpose of communicating various events related to the scheduling of appointments for services or for the use of resources.  There are three basic types of messages defined in this transaction set:  request transactions and their responses, query transactions and their responses, and unsolicited transactions and their responses.  Request transactions communicate requests for the scheduling of appointments for services or for the use of resources.  These transactions occur between placer (requesting) applications and filler (processing) applications.  The query and unsolicited transaction sets provide for the exchange of scheduling information between systems.  The exchange of this information is achieved either actively or passively.  The active gathering of scheduling information is performed by issuing query transactions to a filler application from a querying application.  The passive gathering of this information is performed by accepting unsolicited transactions issued by a filler application."}

genjson/HL7v2.3/Chapters/CH_11.json

@@ -0,0 +1 @@
+{"id":"CH_11","title":"Patient Referral","description":"The Patient Referral chapter defines the message set used in patient referral communications between mutually exclusive healthcare entities.  These referral transactions frequently occur between entities with different methods and systems of capturing and storing data.  Such transactions frequently traverse a path connecting primary care providers, specialists, payors, government agencies, hospitals, labs, and other healthcare entities.  The availability, completeness, and currency of information for a given patient will vary greatly across such a spectrum."}

genjson/HL7v2.3/Chapters/CH_12.json

@@ -0,0 +1 @@
+{"id":"CH_12","title":"Patient Care","description":"The Patient Care Technical Committee has designed the following messages to support the communication of problem-oriented records, including clinical problems, goals, and pathway information between computer systems.  The purpose of this chapter is to describe healthcare messages that need to be communicated between clinical applications for a given individual.  These message transactions can be sent in either batch or online mode.  As described in Chapter 2, multiple communication transactions may be grouped and sent between applications using a file transfer media or direct networked connection."}

genjson/HL7v2.3/DataTypes/AD.json

@@ -0,0 +1 @@
+{"id":"AD","type":"DataType","name":"Address","description":"Example: \r\n|10 ASH LN^#3^LIMA^OH^48132| ","dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"AD.1","type":"DataTypeComponent","position":"AD.1","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Street Address","description":"Street address "},{"id":"AD.2","type":"DataTypeComponent","position":"AD.2","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Other Designation","description":"Second line of address. In general, it qualifies address.  Examples:  Suite 555 or Fourth Floor"},{"id":"AD.3","type":"DataTypeComponent","position":"AD.3","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"City","description":null},{"id":"AD.4","type":"DataTypeComponent","position":"AD.4","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"State Or Province","description":"State or province should be represented by the official postal service codes for that country"},{"id":"AD.5","type":"DataTypeComponent","position":"AD.5","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Zip Or Postal Code","description":"Zip or postal codes should be represented by the official codes for that country.  In the US, the zip code takes the form 99999[-9999], while the Canadian postal code takes the form A9A-9A9"},{"id":"AD.6","type":"DataTypeComponent","position":"AD.6","length":0,"dataType":"ID","dataTypeName":"Coded values for HL7 tables","usage":"O","rpt":"1","tableId":"ISO3166","tableName":"Country Codes","name":"Country","description":"Defines  the country of the address.   ISO 3166 provides a list of country codes that may be used"},{"id":"AD.7","type":"DataTypeComponent","position":"AD.7","length":0,"dataType":"ID","dataTypeName":"Coded values for HL7 tables","usage":"O","rpt":"1","tableId":"0190","tableName":"Address type","name":"Address Type","description":"Type is optional and defined by HL7 table 0190 - Address type"},{"id":"AD.8","type":"DataTypeComponent","position":"AD.8","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Other Geographic Designation","description":"Other geographic designation includes county, bioregion, SMSA, etc"}]}

genjson/HL7v2.3/DataTypes/CE.json

@@ -0,0 +1 @@
+{"id":"CE","type":"DataType","name":"Coded Element","description":"This data type transmits codes and the text associated with the code.  To allow all six components of a CE data type to be valued, the maximum length of this data type must be at  least 60 (see Section 2.6.2, “Maximum length”)\r\n\r\nExample: \r\n|F-11380^CREATININE^I9^2148-5^CREATININE^LN| ","dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CE.1","type":"DataTypeComponent","position":"CE.1","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Identifier","description":"Sequence of characters (the code) that uniquely identifies the item being referenced by the <text>.  Different coding schemes will have different elements here"},{"id":"CE.2","type":"DataTypeComponent","position":"CE.2","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Text","description":"Name or description of the item in question.  E.g., myocardial infarction or X-ray impression.  Its data type is string (ST). "},{"id":"CE.3","type":"DataTypeComponent","position":"CE.3","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Name Of Coding System","description":"Each coding system is assigned a unique identifier.  This component will serve to identify the coding scheme being used in the identifier component.  The combination of the identifier and name of coding system components will be a unique code for a data item  Each system has a unique identifier. ASTM E123894, Diagnostic, procedure, observation, drug ID, and health outcomes coding systems are identified in the tables in Section 7.1.4, “Coding schemes.”  Others may be added as needed.  When an HL7 table is used for a CE data type, the name of coding system component is defined as HL7nnnn where nnnn is the HL7 table number."},{"id":"CE.4","type":"DataTypeComponent","position":"CE.4","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Alternate Identifier","description":"These three components are defined analogously to the above for the alternate or local coding system.  If the Alternate Text component is absent, and the Alternate Identifier is present, the Alternate Text will be taken to be the same as the Text component.  If the Alternate Coding System component is absent, it will be taken to mean the locally-defined system"},{"id":"CE.5","type":"DataTypeComponent","position":"CE.5","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Alternate Text","description":"These three components are defined analogously to the above for the alternate or local coding system.  If the Alternate Text component is absent, and the Alternate Identifier is present, the Alternate Text will be taken to be the same as the Text component.  If the Alternate Coding System component is absent, it will be taken to mean the locally-defined system"},{"id":"CE.6","type":"DataTypeComponent","position":"CE.6","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Name Of Alternate Coding System","description":"These three components are defined analogously to the above for the alternate or local coding system.  If the Alternate Text component is absent, and the Alternate Identifier is present, the Alternate Text will be taken to be the same as the Text component.  If the Alternate Coding System component is absent, it will be taken to mean the locally-defined system"}]}

genjson/HL7v2.3/DataTypes/CK.json

@@ -0,0 +1 @@
+{"id":"CK","type":"DataType","name":"Composite ID With Check Digit","description":"This data type is used for certain fields that commonly contain check digits, e.g., PID-3-patient ID (internal).  If a site is not using check digits for a particular CK field, the second and third components are not valued.\r\n\r\nExample:   \r\n|128952^6^M11^ADT01| ","dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CK.1","type":"DataTypeComponent","position":"CK.1","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"ID Number","description":null},{"id":"CK.2","type":"DataTypeComponent","position":"CK.2","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Check Digit","description":"The check digit in this data type is not an add-on produced by the message processor.  It is the check digit that is part of the identifying number used in the sending application.  If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null"},{"id":"CK.3","type":"DataTypeComponent","position":"CK.3","length":0,"dataType":"ID","dataTypeName":"Coded values for HL7 tables","usage":"O","rpt":"1","tableId":"0061","tableName":"Check digit scheme","name":"Code Identifying The Check Digit Scheme Employed","description":"The check digit scheme codes are defined in HL7 table 0061 - Check digit scheme"},{"id":"CK.4","type":"DataTypeComponent","position":"CK.4","length":0,"dataType":"HD","dataTypeName":"Hierarchic Designator","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Assigning Authority","description":"The assigning authority is a unique name of the system that creates the data.  It is an HD data type.  It is equivalent to the application ID of the placer or filler order number (see Chapter 4).  Assigning authorities are unique across a given HL7 implementation"}]}

genjson/HL7v2.3/DataTypes/CM_ABS_RANGE.json

@@ -0,0 +1 @@
+{"id":"CM_ABS_RANGE","type":"DataType","name":"Absolute Range","description":null,"dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CM_ABS_RANGE.1","type":"DataTypeComponent","position":"CM_ABS_RANGE.1","length":0,"dataType":"CM_RANGE","dataTypeName":"Wertebereich","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Range","description":null},{"id":"CM_ABS_RANGE.2","type":"DataTypeComponent","position":"CM_ABS_RANGE.2","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Numeric Change","description":null},{"id":"CM_ABS_RANGE.3","type":"DataTypeComponent","position":"CM_ABS_RANGE.3","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Percent Per Change","description":null},{"id":"CM_ABS_RANGE.4","type":"DataTypeComponent","position":"CM_ABS_RANGE.4","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Days","description":null}]}

genjson/HL7v2.3/DataTypes/CM_AUI.json

@@ -0,0 +1 @@
+{"id":"CM_AUI","type":"DataType","name":"Authorization Information","description":null,"dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CM_AUI.1","type":"DataTypeComponent","position":"CM_AUI.1","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Authorization Number","description":null},{"id":"CM_AUI.2","type":"DataTypeComponent","position":"CM_AUI.2","length":0,"dataType":"DT","dataTypeName":"Date","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Date","description":null},{"id":"CM_AUI.3","type":"DataTypeComponent","position":"CM_AUI.3","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Source","description":null}]}

genjson/HL7v2.3/DataTypes/CM_CCD.json

@@ -0,0 +1 @@
+{"id":"CM_CCD","type":"DataType","name":"Charge Time","description":null,"dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CM_CCD.1","type":"DataTypeComponent","position":"CM_CCD.1","length":0,"dataType":"ID","dataTypeName":"Coded values for HL7 tables","usage":"O","rpt":"1","tableId":"0100","tableName":"When to charge","name":"When To Charge Code","description":null},{"id":"CM_CCD.2","type":"DataTypeComponent","position":"CM_CCD.2","length":0,"dataType":"TS","dataTypeName":"Time Stamp","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Date/time","description":null}]}

genjson/HL7v2.3/DataTypes/CM_DDI.json

@@ -0,0 +1 @@
+{"id":"CM_DDI","type":"DataType","name":"Daily Deductible","description":null,"dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CM_DDI.1","type":"DataTypeComponent","position":"CM_DDI.1","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Delay Days","description":null},{"id":"CM_DDI.2","type":"DataTypeComponent","position":"CM_DDI.2","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Amount","description":null},{"id":"CM_DDI.3","type":"DataTypeComponent","position":"CM_DDI.3","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Number Of Days","description":null}]}

genjson/HL7v2.3/DataTypes/CM_DIN.json

@@ -0,0 +1 @@
+{"id":"CM_DIN","type":"DataType","name":"Activation Date","description":null,"dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CM_DIN.1","type":"DataTypeComponent","position":"CM_DIN.1","length":0,"dataType":"TS","dataTypeName":"Time Stamp","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Date","description":null},{"id":"CM_DIN.2","type":"DataTypeComponent","position":"CM_DIN.2","length":0,"dataType":"CE","dataTypeName":"Coded Element","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Institution Name","description":null}]}