Skip to content

Commit c251311

Browse files
kardianoskardianos
committed
hl7: add remaining versions
1 parent 2037b49 commit c251311

File tree

1,362 files changed

+46299
-65
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,362 files changed

+46299
-65
lines changed

‎generate_all.bash

+7-3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,10 @@
11
#!/bin/bash
2-
go run ./hl7fetch/*.go -pkgdir h21 -root ./genjson -version 2.1
2+
go run ./hl7fetch/*.go -pkgdir h210 -root ./genjson -version 2.1
3+
go run ./hl7fetch/*.go -pkgdir h220 -root ./genjson -version 2.2
34
go run ./hl7fetch/*.go -pkgdir h231 -root ./genjson -version 2.3.1
4-
go run ./hl7fetch/*.go -pkgdir h25 -root ./genjson -version 2.5
5+
go run ./hl7fetch/*.go -pkgdir h240 -root ./genjson -version 2.4
6+
go run ./hl7fetch/*.go -pkgdir h250 -root ./genjson -version 2.5
57
go run ./hl7fetch/*.go -pkgdir h251 -root ./genjson -version 2.5.1
6-
go run ./hl7fetch/*.go -pkgdir h28 -root ./genjson -version 2.8
8+
go run ./hl7fetch/*.go -pkgdir h270 -root ./genjson -version 2.7
9+
go run ./hl7fetch/*.go -pkgdir h271 -root ./genjson -version 2.7.1
10+
go run ./hl7fetch/*.go -pkgdir h280 -root ./genjson -version 2.8

‎genjson/HL7v2.2/Chapters/CH_02.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
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.2/Chapters/CH_03.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"id":"CH_03","title":"Admission, Discharge, and Transfer","description":"The ADT transaction set provides for transmitting new or updated demographic and visit information about patients. Since virtually any system attached to the network requires information about patients, it is one of the most commonly used transaction sets. Generally, information is entered into an ADT system and passed to the nursing, ancillary and financial systems either in the form of an unsolicited update or in response to a record - oriented query. This chapter defines the transactions at the seventh level, i.e., the abstract messages.The examples included in this chapter were constructed using the HL7 Encoding Rules"}

‎genjson/HL7v2.2/Chapters/CH_04.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
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.2/Chapters/CH_06.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"id":"CH_06","title":"Finance ","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, multiple transactions may be grouped and sent through all file transfer media or programs when using the HL7 Encoding Rules."}

‎genjson/HL7v2.2/Chapters/CH_07.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
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.2/Chapters/CH_08.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
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.2/DataTypes/AD.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"id":"AD","type":"DataType","name":"Address","description":"All components are ST data type. The street or mailing address of a person or institution.","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":null},{"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":null},{"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":null},{"id":"AD.5","type":"DataTypeComponent","position":"AD.5","length":0,"dataType":"ID","dataTypeName":"Coded Value","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Zip Or Postal Code","description":null},{"id":"AD.6","type":"DataTypeComponent","position":"AD.6","length":0,"dataType":"ID","dataTypeName":"Coded Value","usage":"O","rpt":"1","tableId":"ISO3166","tableName":"Country Codes","name":"Country","description":null},{"id":"AD.7","type":"DataTypeComponent","position":"AD.7","length":0,"dataType":"ID","dataTypeName":"Coded Value","usage":"O","rpt":"1","tableId":"0190","tableName":"ADDRESS TYPE","name":"Type","description":null},{"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":null}]}

‎genjson/HL7v2.2/DataTypes/CE.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"id":"CE","type":"DataType","name":"Coded Element","description":"This data type transmits codes and the text associated with the code.\r\n\r\nExample: \r\n|54.21^Laparoscopy^I9^42112^^AS4| ","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":"ID","dataTypeName":"Coded Value","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 will be 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. For backward compatibility, if this component is absent, it will be taken to mean the CPT-4 with ASTM extensions, i.e., AS4. Other coding systems that might appear here are ICD-9, ICD-10, SNOMED, etc. Each system will be given a unique identifying string. The current ASTM 1238-88 diagnostic/procedure/observation/drug ID/health outcomes coding systems are identified in the tables below. Others may be added as needed."},{"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.2/DataTypes/CK.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
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 ID). 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":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Check Digit","description":null},{"id":"CK.3","type":"DataTypeComponent","position":"CK.3","length":0,"dataType":"ID","dataTypeName":"Coded Value","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 table 0061 - check digit scheme. "},{"id":"CK.4","type":"DataTypeComponent","position":"CK.4","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Assigning Facility ID","description":"The assigning facility ID is a unique name (up to six characters in length) of the system that stores the data. It is an ST data type. It is equivalent to the application ID of the placer or filler order number (see Chapter 4). Assigning facility ID's are unique across a given HL7 implementation."}]}

‎genjson/HL7v2.2/DataTypes/CM_AUI.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
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.2/DataTypes/CM_BATCH_TOTAL.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"id":"CM_BATCH_TOTAL","type":"DataType","name":"Cm For Batch Totals","description":"as many types of totals as needed for the batch may be carried by this field as separate components. Each component is an NM data type","dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CM_BATCH_TOTAL.1","type":"DataTypeComponent","position":"CM_BATCH_TOTAL.1","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Batch Total 1","description":null},{"id":"CM_BATCH_TOTAL.2","type":"DataTypeComponent","position":"CM_BATCH_TOTAL.2","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Batch Total 2","description":null},{"id":"CM_BATCH_TOTAL.3","type":"DataTypeComponent","position":"CM_BATCH_TOTAL.3","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"...","description":null}]}

‎genjson/HL7v2.2/DataTypes/CM_CCD.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
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 Value","usage":"O","rpt":"1","tableId":"0100","tableName":"WHEN TO CHARGE","name":"When To Charge","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.2/DataTypes/CM_DDI.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
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":"ST","dataTypeName":"String Data","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.2/DataTypes/CM_DLD.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"id":"CM_DLD","type":"DataType","name":"Discharge Location","description":null,"dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CM_DLD.1","type":"DataTypeComponent","position":"CM_DLD.1","length":0,"dataType":"ID","dataTypeName":"Coded Value","usage":"O","rpt":"1","tableId":"0113","tableName":"DISCHARGED TO LOCATION","name":"Code","description":null},{"id":"CM_DLD.2","type":"DataTypeComponent","position":"CM_DLD.2","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Description","description":null}]}

‎genjson/HL7v2.2/DataTypes/CM_DTN.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"id":"CM_DTN","type":"DataType","name":"Day Type And Number","description":null,"dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CM_DTN.1","type":"DataTypeComponent","position":"CM_DTN.1","length":0,"dataType":"ID","dataTypeName":"Coded Value","usage":"O","rpt":"1","tableId":"0149","tableName":"DAY TYPE","name":"Day Type","description":null},{"id":"CM_DTN.2","type":"DataTypeComponent","position":"CM_DTN.2","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Number Of Days","description":null}]}

‎genjson/HL7v2.2/DataTypes/CM_EIP.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"id":"CM_EIP","type":"DataType","name":"Parent Order","description":null,"dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CM_EIP.1","type":"DataTypeComponent","position":"CM_EIP.1","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Parent's Placer Order Number","description":"The first component contains the placer order number of the parent order. It is required when the order is a child"},{"id":"CM_EIP.2","type":"DataTypeComponent","position":"CM_EIP.2","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Parent's Filler Order Number","description":"The second component contains the filler order number of the parent order."}]}

‎genjson/HL7v2.2/DataTypes/CM_ELD.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"id":"CM_ELD","type":"DataType","name":"Error","description":null,"dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CM_ELD.1","type":"DataTypeComponent","position":"CM_ELD.1","length":0,"dataType":"ST","dataTypeName":"String Data","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Segment-id","description":null},{"id":"CM_ELD.2","type":"DataTypeComponent","position":"CM_ELD.2","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Sequence","description":null},{"id":"CM_ELD.3","type":"DataTypeComponent","position":"CM_ELD.3","length":0,"dataType":"NM","dataTypeName":"Numeric","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Field-position","description":null},{"id":"CM_ELD.4","type":"DataTypeComponent","position":"CM_ELD.4","length":0,"dataType":"CE","dataTypeName":"Coded Element","usage":"O","rpt":"1","tableId":"0060","tableName":"ERROR CODE","name":"Code Identifying Error","description":null}]}

‎genjson/HL7v2.2/DataTypes/CM_FILLER.json

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
{"id":"CM_FILLER","type":"DataType","name":"Number Of Processing Power Point","description":null,"dataType":null,"dataTypeName":null,"length":0,"usage":null,"rpt":null,"tableId":null,"tableName":null,"sample":"","fields":[{"id":"CM_FILLER.1","type":"DataTypeComponent","position":"CM_FILLER.1","length":0,"dataType":"ID","dataTypeName":"Coded Value","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Unique Filler Id","description":"Its first component is a string of up to 15 characters that identifies an order detail segment (e.g., OBR). It is assigned by the order filler (receiving) application. This string must uniquely identify the order (as specified in the order detail segment) from other orders in a particular filling application (e.g., clinical laboratory). This uniqueness must persist over time. "},{"id":"CM_FILLER.2","type":"DataTypeComponent","position":"CM_FILLER.2","length":0,"dataType":"ID","dataTypeName":"Coded Value","usage":"O","rpt":"1","tableId":null,"tableName":null,"name":"Filler Application Id","description":"The second component contains the filler application ID. The filler application ID is a string of up to six characters that uniquely defines the application from other applications on the network. The second component of the filler order number always identifies the actual filler of an order. "}]}

0 commit comments

Comments
 (0)