The printable 7-bit ASCII character set. (This is the default if this field is omitted) |
8859/1 |
The printable characters from the ISO 8859/1 Character set |
8859/2 |
The printable characters from the ISO 8859/2 Character set |
8859/3 |
The printable characters from the ISO 8859/3 Character set |
8859/4 |
The printable characters from the ISO 8859/4 Character set |
8859/5 |
The printable characters from the ISO 8859/5 Character set |
8859/6 |
The printable characters from the ISO 8859/6 Character set |
8859/7 |
The printable characters from the ISO 8859/7 Character set |
8859/8 |
The printable characters from the ISO 8859/8 Character set |
8859/9 |
The printable characters from the ISO 8859/9 Character set |
ISO IR14 |
Code for Information Exchange (one byte)(JIS X 0201-1976). Note that the code contains a space, i.e. "ISO IR14". |
ISO IR87 |
Code for the Japanese Graphic Character set for information interchange (JIS X 0208-1990), Note that the code contains a space, i.e. "ISO IR87". |
ISO IR159 |
Code of the supplementary Japanese Graphic Character set for information interchange (JIS X 0212-1990). Note that the code contains a space, i.e. "ISO IR159". |
UNICODE |
The world wide character standard from ISO/IEC 10646-1-1993[3] |
Note:
The field separator character must still be chosen from the printable
7-bit ASCII character set.
The repetitions of this field to specify different character sets apply only to
fields of the, FT, ST, and TX data types.
The field MSH-18-character set is an optional, repeating field of data
type ID, using IDs outlined in HL7 Table 0211 - Alternat
e
character sets (or equivalents from "ISO 2375").
* if the field is not valued, the default single-byte character set (ASCII
("ISO IR6")) should be assumed. No other character sets are allowed in the
message.
* if the field repeats, but the first element is NULL (i.e., present but
unvalued), the single-byte ASCII ("ISO IR6") is assumed as the default
character set.
* if the sequence is present and the first element is specified, this character
set is regarded as the default character set for the message. This must be a
single-byte character set (i.e., "ISO IR6", "ISO IR13", "ISO IR14", "ISO
IR100", etc.).
* elements in the remainder of the sequence (i.e., elements 2..n) are alternate
character sets that may be used. These may include multi-byte character sets
(i.e., JIS X 0208).
* the default character set should always be a single-byte character set. It
should always have "ISO IR6" (ISO 646) or "ISO IR14" (JIS X 0201-1976) in the
G0 area.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains the principal language of the message. Codes
come from ISO 639.
Definition:
When any alternative character sets are used (as specified in the second or
later components of MSH-18 character sets), and if any special handling
scheme is needed, this component is to specify the scheme used, according to
HL7 Table 0356- Alternate character set
handling
scheme as defined below:
Value |
Description |
|---|---|
ISO 2022-1994 |
This standard is titled "Information Technology - Character Code Structure and Extension Technique". This standard specifies an escape sequence from basic one byte character set to specified other character set, and vice versa. The escape sequence explicitly specifies what alternate character set to be evoked. Note that in this mode, the actual ASCII escape character is used as defined in the referenced ISO document. As noted in 1.6.1., escape sequences to/from alternate character set should occur within HL7 delimiters. In other words, HL7 delimiters are basic one byte characters only, and just before and just after delimiters, character encoding status should be the basic one byte set. |
2.3 |
The character set switching mode specified in HL7 2.3, sections <IP_ADDRESS>.1, and 2.9.2. Note that the escape sequences used in this mode do not use the ASCII "esc" character. They are "HL7 escape sequences" as defined in HL7 2.3, sec. 2.9 as defined in ISO 2022-1994 (Also, note that sections <IP_ADDRESS>.1and 2.9.2 in HL7 2.3 correspond to sections <IP_ADDRESS>.1and 2.9.2 in HL7 2.4.) |
<null> |
This is the default, indicating that there is no character set switching occurring in this message. |
Definition:
Sites may use this field to assert adherence to a Conformance Statement
published by HL7 or by a site. Conformance Statements contain detailed
explanations of grammar, syntax, and usage for a particular message or set of
messages. Examples of the use of Conformance Statements appear in Chapter 5,
"Query."
Repetition of this field allows more flexibility in creating and naming
conformance statements. For example, the first repetition could reference a
standard conformance statement, and the second, just some changes to it.
Values for HL7-standard conformance statements appear in HL7 Table 0449 -
Confor
mance
statements as defined below.
Value |
Description |
|---|---|
Note: As HL7 technical committees ballot conformance statements, table 449 will be populated with their identifiers. No identifiers have been issued as of v 2.4. As with any HL7 table, this table may be extended with site-defined identifiers.
The
NTE segment is defined here for inclusion in messages defined in other
chapters. It is commonly used for sending notes and comments.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM # |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
4 |
SI |
O |
00096 |
Set ID - NTE |
||
2 |
8 |
ID |
O |
0105 |
00097 |
Source of Comment |
|
3 |
65536 |
FT |
O |
Y |
00098 |
Comment |
|
4 |
250 |
CE |
O |
0364 |
01318 |
Comment Type |
Definition: This field may be used where multiple NTE segments are included in a message. Their numbering must be described in the application message definition.
Definition:
This field is used when source of comment must be identified. This table may
be extended locally during implementation. Refer to HL7 Table 0105 -
Source of com
ment
for valid values.
Value |
Description |
|---|---|
L |
Ancillary (filler) department is source of comment |
P |
Orderer (placer) is source of comment |
O |
Other system is source of comment |
Definition:
This field contains the comment contained in the segment.
Note: In the current HL7 version, this is a FT rather than a TX data
type. Since there is no difference between a FT data type without any embedded
formatting commands, and a TX data type, this change is compatible with the
previous version.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: This field contains a value to identify the type of comment text
being sent in the specific comment record. Refer to User-defined
Table 0364 - Comment type for suggested values.
Value |
Description |
|---|---|
PI |
Patient Instructions |
AI |
Ancillary Instructions |
GI |
General Instructions |
1R |
Primary Reason |
2R |
Secondary Reason |
GR |
General Reason |
RE |
Remark |
DR |
Duplicate/Interaction Reason |
Note: A field already exists on the NTE record that identifies the Sources of Comment (e.g., ancillary, placer, other). However some applications need to support other types of comment text (e.g., instructions, reason, remarks, etc.). A separate NTE segment can be used for each type of comment (e.g., instructions are on one NTE and remarks on another NTE).
Message |
Description |
Chapter |
|---|---|---|
ACK |
General acknowledgment message |
2 |
ADR |
ADT response |
3 |
ADT |
ADT message |
3 |
BAR |
Add/change billing account |
6 |
CRM |
Clinical study registration message |
7 |
CSU |
Unsolicited study data message |
7 |
DFT |
Detail financial transactions |
6 |
DOC |
Document response |
9 |
DSR |
Display response |
5 |
EAC |
Automated equipment command message |
13 |
EAN |
Automated equipment notification message |
13 |
EAR |
Automated equipment response message |
13 |
EDR |
Enhanced display response |
2 |
EQQ |
Embedded query language query |
2 |
ERP |
Event replay response |
2 |
ESR |
Automated equipment status update acknowledgment message |
13 |
ESU |
Automated equipment status update message |
13 |
INR |
Automated equipment inventory request message |
13 |
INU |
Automated equipment inventory update message |
13 |
LSR |
Automated equipment log/service request message |
13 |
LSU |
Automated equipment log/service update message |
13 |
MCF |
Delayed Acknowledgment (Retained for backward compatibility only) |
2 |
MDM |
Medical document management |
9 |
MFD |
Master files delayed application acknowledgment |
8 |
MFK |
Master files application acknowledgment |
8 |
MFN |
Master files notification |
8 |
MFQ |
Master files query |
8 |
MFR |
Master files response |
8 |
NMD |
Application management data message |
14 |
NMQ |
Application management query message |
14 |
NMR |
Application management response message |
14 |
OMD |
Dietary order |
4 |
OMG |
General clinical order message |
4 |
OML |
Laboratory order message |
4 |
OMN |
Non-stock requisition order message |
4 |
OMP |
Pharmacy/treatment order message |
4 |
OMS |
Stock requisition order message |
4 |
OMS |
Stock requisition order message |
4 |
ORD |
Dietary order acknowledgment message |
4 |
ORF |
Query for results of observation |
7 |
ORG |
General clinical order acknowledgment message |
4 |
ORL |
Laboratory acknowledgment message (unsolicited) |
7 |
ORM |
Pharmacy/treatment order message |
4 |
ORN |
Non-stock requisition - General order acknowledgment message |
4 |
ORP |
Pharmacy/treatment order acknowledgment message |
4 |
ORR |
General order response message response to any ORM |
4 |
ORS |
Stock requisition - Order acknowledgment message |
4 |
ORU |
Unsolicited transmission of an observation message |
7 |
OSQ |
Query response for order status |
4 |
OSR |
Query response for order status |
4 |
OUL |
Unsolicited laboratory observation message |
7 |
PEX |
Product experience message |
7 |
PGL |
Patient goal message |
12 |
PIN |
Patient insurance information |
11 |
PMU |
Add personnel record |
15 |
PPG |
Patient pathway message (goal-oriented) |
12 |
PPP |
Patient pathway message (problem-oriented) |
12 |
PPR |
Patient problem message |
12 |
PPT |
Patient pathway goal-oriented response |
12 |
PPV |
Patient goal response |
12 |
PRR |
Patient problem response |
12 |
PTR |
Patient pathway problem-oriented response |
12 |
QBP |
Query by parameter |
5 |
QCK |
Deferred query |
2 |
QCN |
Cancel query |
5 |
QRY |
Query, original mode |
3 |
QSB |
Create subscription |
5 |
QSX |
Cancel subscription/acknowledge message |
5 |
QVR |
Query for previous events |
5 |
RAR |
Pharmacy/treatment administration information |
4 |
RAS |
Pharmacy/treatment administration message |
4 |
RCI |
Return clinical information |
11 |
RCL |
Return clinical list |
11 |
RDE |
Pharmacy/treatment encoded order message |
4 |
RDR |
Pharmacy/treatment dispense information |
4 |
RDS |
Pharmacy/treatment dispense message |
4 |
RDY |
Display based response |
5 |
REF |
Patient referral |
11 |
RER |
Pharmacy/treatment encoded order information |
4 |
RGR |
Pharmacy/treatment dose information |
4 |
RGV |
Pharmacy/treatment give message |
4 |
ROR |
Pharmacy/treatment order response |
4 |
RPA |
Return patient authorization |
11 |
RPI |
Return patient information |
11 |
RPL |
Return patient display list |
11 |
RPR |
Return patient list |
11 |
RQA |
Request patient authorization |
11 |
RQC |
Request clinical information |
11 |
RQI |
Request patient information |
11 |
RQP |
Request patient demographics |
11 |
RQQ |
Event replay query |
2 |
RRA |
Pharmacy/treatment administration acknowledgment message |
4 |
RRD |
Pharmacy/treatment dispense acknowledgment message |
4 |
RRE |
Pharmacy/treatment encoded order acknowledgment message |
4 |
RRG |
Pharmacy/treatment give acknowledgment message |
4 |
RRI |
Return referral information |
11 |
RSP |
Segment pattern response |
5 |
RTB |
Tabular response |
5 |
SIU |
Schedule information unsolicited |
10 |
SPQ |
Stored procedure request |
2 |
SQM |
Schedule query message |
10 |
SQR |
Schedule query response |
10 |
SRM |
Schedule request message |
10 |
SRR |
Scheduled request response |
10 |
SSR |
Specimen status request message |
13 |
SSU |
Specimen status update message |
13 |
SUR |
Summary product experience report |
7 |
TBR |
Tabular data response |
2 |
TCR |
Automated equipment test code settings request message |
13 |
TCU |
Automated equipment test code settings update message |
13 |
UDM |
Unsolicited display update message |
2 |
VQQ |
Virtual table query |
2 |
VXQ |
Query for vaccination record |
4 |
VXR |
Vaccination record response |
4 |
VXU |
Unsolicited vaccination record update |
4 |
VXX |
Response for vaccination query with multiple PID matches |
4 |
Value |
Description |
|---|---|
A01 |
ADT/ACK - Admit/visit notification |
A02 |
ADT/ACK - Transfer a patient |
A03 |
ADT/ACK - Discharge/end visit |
A04 |
ADT/ACK - Register a patient |
A05 |
ADT/ACK - Pre-admit a patient |
A06 |
ADT/ACK - Change an outpatient to an inpatient |
A07 |
ADT/ACK - Change an inpatient to an outpatient |
A08 |
ADT/ACK - Update patient information |
A09 |
ADT/ACK - Patient departing - tracking |
A10 |
ADT/ACK - Patient arriving - tracking |
A11 |
ADT/ACK - Cancel admit/visit notification |
A12 |
ADT/ACK - Cancel transfer |
A13 |
ADT/ACK - Cancel discharge/end visit |
A14 |
ADT/ACK - Pending admit |
A15 |
ADT/ACK - Pending transfer |
A16 |
ADT/ACK - Pending discharge |
A17 |
ADT/ACK - Swap patients |
A18 |
ADT/ACK - Merge patient information (for backward compatibility only) |
A19 |
QRY/ADR - Patient query |
A20 |
ADT/ACK - Bed status update |
A21 |
ADT/ACK - Patient goes on a "leave of absence" |
A22 |
ADT/ACK - Patient returns from a "leave of absence" |
A23 |
ADT/ACK - Delete a patient record |
A24 |
ADT/ACK - Link patient information |
A25 |
ADT/ACK - Cancel pending discharge |
A26 |
ADT/ACK - Cancel pending transfer |
A27 |
ADT/ACK - Cancel pending admit |
A28 |
ADT/ACK - Add person information |
A29 |
ADT/ACK - Delete person information |
A30 |
ADT/ACK - Merge person information (for backward compatibility only) |
A31 |
ADT/ACK - Update person information |
A32 |
ADT/ACK - Cancel patient arriving - tracking |
A33 |
ADT/ACK - Cancel patient departing - tracking |
A34 |
ADT/ACK - Merge patient information - patient ID only (for backward compatibility only) |
A35 |
ADT/ACK - Merge patient information - account number only (for backward compatibility only) |
A36 |
ADT/ACK - Merge patient information - patient ID and account number (for backward compatibility only) |
A37 |
ADT/ACK - Unlink patient information |
A38 |
ADT/ACK - Cancel pre-admit |
A39 |
ADT/ACK - Merge person - patient ID (for backward compatibility only) |
A40 |
ADT/ACK - Merge patient - patient identifier list |
A41 |
ADT/ACK - Merge account - patient account number |
A42 |
ADT/ACK - Merge visit - visit number |
A43 |
ADT/ACK - Move patient information - patient identifier list |
A44 |
ADT/ACK - Move account information - patient account number |
A45 |
ADT/ACK - Move visit information - visit number |
A46 |
ADT/ACK - Change patient ID (for backward compatibility only) |
A47 |
ADT/ACK - Change patient identifier list |
A48 |
ADT/ACK - Change alternate patient ID (for backward compatibility only) |
A49 |
ADT/ACK - Change patient account number |
A50 |
ADT/ACK - Change visit number |
A51 |
ADT/ACK - Change alternate visit ID |
A52 |
ADT/ACK - Cancel leave of absence for a patient |
A53 |
ADT/ACK - Cancel patient returns from a leave of absence |
A54 |
ADT/ACK - Change attending doctor |
A55 |
ADT/ACK - Cancel change attending doctor |
A60 |
ADT/ACK - Update allergy information |
A61 |
ADT/ACK - Change consulting doctor |
A62 |
ADT/ACK - Cancel change consulting doctor |
B01 |
PMU/ACK - Add personnel record |
B02 |
PMU/ACK - Update personnel record |
B03 |
PMU/ACK - Delete personnel re cord |
B04 |
PMU/ACK - Active practicing person |
B05 |
PMU/ACK - Deactivate practicing person |
B06 |
PMU/ACK - Terminate practicing person |
C01 |
CRM - Register a patient on a clinical trial |
C02 |
CRM - Cancel a patient registration on clinical trial (for clerical mistakes only) |
C03 |
CRM - Correct/update registration information |
C04 |
CRM - Patient has gone off a clinical trial |
C05 |
CRM - Patient enters phase of clinical trial |
C06 |
CRM - Cancel patient entering a phase (clerical mistake) |
C07 |
CRM - Correct/update phase information |
C08 |
CRM - Patient has gone off phase of clinical trial |
C09 |
CSU - Automated time intervals for reporting, like monthly |
C10 |
CSU - Patient completes the clinical trial |
C11 |
CSU - Patient completes a phase of the clinical trial |
C12 |
CSU - Update/correction of patient order/result information |
I01 |
RQI/RPI - Request for insurance information |
I02 |
RQI/RPL - Request/receipt of patient selection display list |
I03 |
RQI/RPR - Request/receipt of patient selection list |
I04 |
RQD/RPI - Request for patient demographic data |
I05 |
RQC/RCI - Request for patient clinical information |
I06 |
RQC/RCL - Request/receipt of clinical data listing |
I07 |
PIN/ACK - Unsolicited insurance information |
I08 |
RQA/RPA - Request for treatment authorization information |
I09 |
RQA/RPA - Request for modification to an authorization |
I10 |
RQA/RPA - Request for resubmission of an authorization |
I11 |
RQA/RPA - Request for cancellation of an authorization |
I12 |
REF/RRI - Patient referral |
I13 |
REF/RRI - Modify patient referral |
I14 |
REF/RRI - Cancel patient referral |
I15 |
REF/RRI - Request patient referral status |
J01 |
QCN/ACK - Cancel query/acknowledge message |
J02 |
QSX/ACK - Cancel subscription/acknowledge message |
K11 |
RSP - Segment pattern response |
K13 |
RTB - Tabular response |
K15 |
RDY - Display response |
K21 |
RSP - Get person demographics response |
K22 |
RSP - Find candidates response |
K23 |
RSP - Get corresponding identifiers response |
K24 |
RSP - Allocate identifiers response |
K25 |
RSP - Personnel Information by Segment Response |
M01 |
MFN/MFK - Master file not otherwise specified (for backward compatibility only) |
M02 |
MFN/MFK - Master file - staff practitioner |
M03 |
MFN/MFK - Master file - test/observation (for backward compatibility only) |
M04 |
MFN/MFK - Master files charge description |
M05 |
MFN/MFK - Patient location master file |
M06 |
MFN/MFK - Clinical study with phases and schedules master file |
M07 |
MFN/MFK - Clinical study without phases but with schedules master file |
M08 |
MFN/MFK - Test/observation (numeric) master file |
M09 |
MFN/MFK - Test/observation (categorical) master file |
M10 |
MFN/MFK - Test /observation batteries master file |
M11 |
MFN/MFK - Test/calculated observations master file |
M12 |
MFN/MFK - Master file notification message |
N01 |
NMQ/NMR - Application management query message |
N02 |
NMD/ACK - Application management data message (unsolicited) |
O01 |
ORM - Order message (also RDE, RDS, RGV, RAS) |
O02 |
ORR - Order response (also RRE, RRD, RRG, RRA) |
O03 |
OMD - Diet order |
O04 |
ORD - Diet order acknowledgment |
O05 |
OMS - Stock requisition order |
O06 |
ORS - Stock requisition acknowledgment |
O07 |
OMN - Non-stock requisition order |
O08 |
ORN - Non-stock requisition acknowledgment |
O09 |
OMP - Pharmacy/treatment order |
O10 |
ORP - Pharmacy/treatment order acknowledgment |
O11 |
RDE - Pharmacy/treatment encoded order |
O12 |
RRE - Pharmacy/treatment encoded order acknowledgment |
O13 |
RDS - Pharmacy/treatment dispense |
O14 |
RRD - Pharmacy/treatment dispense acknowledgment |
O15 |
RGV - Pharmacy/treatment give |
O16 |
RRG - Pharmacy/treatment give acknowledgment |
O17 |
RAS - Pharmacy/treatment administration |
O18 |
RRA - Pharmacy/treatment administration acknowledgment |
O19 |
OMG - General clinical order |
O20 |
ORG/ORL - General clinical order response |
O21 |
OML - Laboratory order |
022 |
ORL - General laboratory order response message to any OML |
P01 |
BAR/ACK - Add patient accounts |
P02 |
BAR/ACK - Purge patient accounts |
P03 |
DFT/ACK - Post detail financial transaction |
P04 |
QRY/DSP - Generate bill and A/R statements |
P05 |
BAR/ACK - Update account |
P06 |
BAR/ACK - End account |
P07 |
PEX - Unsolicited initial individual product experience report |
P08 |
PEX - Unsolicited update individual product experience report |
P09 |
SUR - Summary product experience report |
P10 |
BAR/ACK -Transmit Ambulatory Payment Classification(APC) |
PC1 |
PPR - PC/ problem add |
PC2 |
PPR - PC/ problem update |
PC3 |
PPR - PC/ problem delete |
PC4 |
QRY - PC/ problem query |
PC5 |
PRR - PC/ problem response |
PC6 |
PGL - PC/ goal add |
PC7 |
PGL - PC/ goal update |
PC8 |
PGL - PC/ goal delete |
PC9 |
QRY - PC/ goal query |
PCA |
PPV - PC/ goal response |
PCB |
PPP - PC/ pathway (problem-oriented) add |
PCC |
PPP - PC/ pathway (problem-oriented) update |
PCD |
PPP - PC/ pathway (problem-oriented) delete |
PCE |
QRY - PC/ pathway (problem-oriented) query |
PCF |
PTR - PC/ pathway (problem-oriented) query response |
PCG |
PPG - PC/ pathway (goal-oriented) add |
PCH |
PPG - PC/ pathway (goal-oriented) update |
PCJ |
PPG - PC/ pathway (goal-oriented) delete |
PCK |
QRY - PC/ pathway (goal-oriented) query |
PCL |
PPT - PC/ pathway (goal-oriented) query response |
Q01 |
QRY/DSR - Query sent for immediate response |
Q02 |
QRY/QCK - Query sent for deferred response |
Q03 |
DSR/ACK - Deferred response to a query |
Q04 |
EQQ - Embedded query language query |
Q05 |
UDM/ACK - Unsolicited display update message |
Q06 |
OSQ/OSR - Query for order status |
Q07 |
VQQ - Virtual table query |
Q08 |
SPQ - Stored procedure request |
Q09 |
RQQ - event replay query |
Q16 |
QSB - Create subscription |
Q17 |
QVR - Query for previous events |
Q21 |
QBP - Get person demographics |
Q22 |
QBP - Find candidates |
Q23 |
QBP - Get corresponding identifiers |
Q24 |
QBP - Allocate identifiers |
Q25 |
QBP - Personnel Information by Segment Query |
Q26 |
ROR - Pharmacy/treatment order response |
Q27 |
RAR - Pharmacy/treatment administration information |
Q28 |
RDR - Pharmacy/treatment dispense information |
Q29 |
RER - Pharmacy/treatment encoded order information |
Q30 |
RGR - Pharmacy/treatment dose information |
QNC |
Varies - Query cancellation |
R01 |
ORU/ACK - Unsolicited transmission of an observation message |
R02 |
QRY - Query for results of observation |
R03 |
QRY/DSR Display-oriented results, query/unsol. update (for backward compatibility only) (Replaced by Q05) |
R04 |
ORF - Response to query; transmission of requested observation |
ROR |
ROR - Pharmacy prescription order query response |
R07 |
EDR - Enhanced Display Response |
R08 |
TBR - Tabular Data Response |
R09 |
ERP - Event Replay Response |
R21 |
OUL - Unsolicited laboratory observation |
S01 |
SRM/SRR - Request new appointment booking |
S02 |
SRM/SRR - Request appointment rescheduling |
S03 |
SRM/SRR - Request appointment modification |
S04 |
SRM/SRR - Request appointment cancellation |
S05 |
SRM/SRR - Request appointment discontinuation |
S06 |
SRM/SRR - Request appointment deletion |
S07 |
SRM/SRR - Request addition of service/resource on appointment |
S08 |
SRM/SRR - Request modification of service/resource on appointment |
S09 |
SRM/SRR - Request cancellation of service/resource on appointment |
S10 |
SRM/SRR - Request discontinuation of service/resource on appointment |
S11 |
SRM/SRR - Request deletion of service/resource on appointment |
S12 |
SIU/ACK - Notification of new appointment booking |
S13 |
SIU/ACK - Notification of appointment rescheduling |
S14 |
SIU/ACK - Notification of appointment modification |
S15 |
SIU/ACK - Notification of appointment cancellation |
S16 |
SIU/ACK - Notification of appointment discontinuation |
S17 |
SIU/ACK - Notification of appointment deletion |
S18 |
SIU/ACK - Notification of addition of service/resource on appointment |
S19 |
SIU/ACK - Notification of modification of service/resource on appointment |
S20 |
SIU/ACK - Notification of cancellation of service/resource on appointment |
S21 |
SIU/ACK - Notification of discontinuation of service/resource on appointment |
S22 |
SIU/ACK - Notification of deletion of service/resource on appointment |
S23 |
SIU/ACK - Notification of blocked schedule time slot(s) |
S24 |
SIU/ACK - Notification of opened ("unblocked") schedule time slot(s) |
S25 |
SQM/SQR - Schedule query message and response |
S26 |
SIU/ACK Notification that patient did not show up for schedule appointment |
T01 |
MDM/ACK - Original document notification |
T02 |
MDM/ACK - Original document notification and content |
T03 |
MDM/ACK - Document status change notification |
T04 |
MDM/ACK - Document status change notification and content |
T05 |
MDM/ACK - Document addendum notification |
T06 |
MDM/ACK - Document addendum notification and content |
T07 |
MDM/ACK - Document edit notification |
T08 |
MDM/ACK - Document edit notification and content |
T09 |
MDM/ACK - Document replacement notification |
T10 |
MDM/ACK - Document replacement notification and content |
T11 |
MDM/ACK - Document cancel notification |
T12 |
QRY/DOC - Document query |
U01 |
ESU/ACK - Automated equipment status update |
U02 |
ESR/ACK - Automated equipment status request |
U03 |
SSU/ACK - Specimen status update |
U04 |
SSR/ACK - specimen status request |
U05 |
INU/ACK - Automated equipment inventory update |
U06 |
INR/ACK - Automated equipment inventory request |
U07 |
EAC/ACK - Automated equipment command |
U08 |
EAR/ACK - Automated equipment response |
U09 |
EAN/ACK - Automated equipment notification |
U10 |
TCU/ACK - Automated equipment test code settings update |
U11 |
TCR/ACK - Automated equipment test code settings request |
U12 |
LSU/ACK - Automated equipment log/service update |
U13 |
LSR/ACK - Automated equipment log/service request |
V01 |
VXQ - Query for vaccination record |
V02 |
VXX - Response to vaccination query returning multiple PID matches |
V03 |
VXR - Vaccination record response |
V04 |
VXU - Unsolicited vaccination record update |
Varies |
MFQ/MFR - Master files query (use event same as asking for e.g., M05 - location) |
W01 |
ORU - Waveform result, unsolicited transmission of requested information |
W02 |
QRF - Waveform result, response to query |
Value |
Events |
|---|---|
ACK |
Varies |
ADR_A19 |
A19 |
ADT_A01 |
A01, A04, A08, A13 |
ADT_A02 |
A02 |
ADT_A03 |
A03 |
ADT_A05 |
A05, A14, A28, A31 |
ADT_A06 |
A06, A07 |
ADT_A09 |
A09, A10, A11, A12 |
ADT_A15 |
A15 |
ADT_A16 |
A16 |
ADT_A17 |
A17 |
ADT_A18 |
A18 |
ADT_A20 |
A20 |
ADT_A21 |
A21, A22, A23, A25, A26, A27, A29, A32, A33 |
ADT_A24 |
A24 |
ADT_A30 |
A30, A34, A35, A36, A46, A47, A48, A49 |
ADT_A37 |
A37 |
ADT_A38 |
A38 |
ADT_A39 |
A39, A40, A41, A42 |
ADT_A43 |
A43, A44 |
ADT_A45 |
A45 |
ADT_A50 |
A50, A51 |
ADT_A52 |
A52, A53, A55 |
ADT_A54 |
A54 |
ADT_A60 |
A60 |
ADT_A61 |
A61, A62 |
BAR_P01 |
P01 |
BAR_P02 |
P02 |
BAR_P05 |
P05 |
BAR_P06 |
P06 |
BAR_P10 |
P10 |
CRM_C01 |
C01, C02, C03, C04, C05, C06, C07, C08 |
CSU_C09 |
C09, C10, C11, C12 |
DFT_P03 |
P03 |
DOC_T12 |
T12 |
DSR_P04 |
P04 |
DSR_Q01 |
Q01 |
DSR_Q03 |
Q03 |
EAC_U07 |
U07 |
EAN_U09 |
U09 |
EAR_U08 |
U08 |
EDR_R07 |
R07 |
EQQ_Q04 |
Q04 |
ERP_R09 |
R09 |
ESR_U02 |
U02 |
ESR_U02 |
U02 |
ESU_U01 |
U01 |
INR_U06 |
U06 |
INU_U05 |
U05 |
LSU_U12 |
U12, U13 |
MDM_T01 |
T01, T03, T05, T07, T09, T11 |
MDM_T02 |
T02, T04, T06, T08, T10 |
MFD_MFA |
MFA |
MFK_M01 |
M01, M02, M03, M04, M05, M06, M07, M08, M09, M10, M11 |
MFN_M01 |
M01 |
MFN_M02 |
M02 |
MFN_M03 |
M03 |
MFN_M04 |
M04 |
MFN_M05 |
M05 |
MFN_M06 |
M06 |
MFN_M07 |
M07 |
MFN_M08 |
M08 |
MFN_M09 |
M09 |
MFN_M10 |
M10 |
MFN_M11 |
M11 |
MFN_M12 |
M12 |
MFQ_M01 |
M01, M02, M03, M04, M05, M06 |
MFR_M01 |
M01, M02, M03, M04, M05, M06 |
NMD_N02 |
N02 |
NMQ_N01 |
N01 |
NMR_N01 |
N01 |
OMD_O03 |
O03 |
OMG_O19 |
O19 |
OML_O21 |
O21 |
OMN_O07 |
007 |
OMP_O09 |
O09 |
OMS_O05 |
O05 |
ORD_O04 |
O04 |
ORF_R04 |
R04 |
ORG_O20 |
O20 |
ORL_O22 |
022 |
ORM_O01 |
O01 |
ORN_008 |
O08 |
ORP_O10 |
O10 |
ORR_O02 |
O02 |
ORR_O02 |
O02 |
ORS_O06 |
O06 |
ORU_R01 |
R01 |
OSQ_Q06 |
Q06 |
OSR_Q06 |
Q06 |
OUL_R21 |
R21 |
PEX_P07 |
P07, P08 |
PGL_PC6 |
PC6, PC7, PC8 |
PMU_B01 |
B01, B02 |
PMU_B03 |
B03 |
PMU_B04 |
B04, B05 |
PPG_PCG |
PCC, PCG, PCH, PCJ |
PPP_PCB |
PCB, PCD |
PPR_PC1 |
PC1, PC2, PC3 |
PPT_PCL |
PCL |
PPV_PCA |
PCA |
PRR_PC5 |
PC5 |
PTR_PCF |
PCF |
QBP_Q11 |
Q11 |
QBP_Q13 |
Q13 |
QBP_Q15 |
Q15 |
QBP_Q21 |
Q21, Q22, Q23,Q24, Q25 |
QCK_Q02 |
Q02 |
QCN_J01 |
J01, J02 |
QRY_A19 |
A19 |
QRY_P04 |
P04 |
QRY_PC4 |
PC4, PC9, PCE, PCK |
QRY_Q01 |
Q01 |
QRY_Q02 |
Q02 |
QRY_Q26 |
Q26 |
QRY_Q27 |
Q27 |
QRY_Q28 |
Q28 |
QRY_Q29 |
Q29 |
QRY_Q30 |
Q30 |
QRY_R02 |
R02 |
QRY_T12 |
T12 |
QSB_Q16 |
Q16 |
QVR_Q17 |
Q17 |
RAS_O17 |
O17 |
RCI_I05 |
I05 |
RCL_I06 |
I06 |
RDE_O01 |
O01 |
RDR_RDR |
RDR |
RDS_O13 |
O13 |
RDY_K15 |
K15 |
REF_I12 |
I12, I13, I14, I15 |
RER_RER |
RER |
RGR_RGR |
RGR |
RGV_O15 |
O15 |
ROR_ROR |
ROR |
RPA_I08 |
I08, I09. I10, 1II |
RPI_I0I |
I01, I04 |
RPL_I02 |
I02 |
RPR_I03 |
I03 |
RQA_I08 |
I08, I09, I10, I11 |
RQC_I05 |
I05, I06 |
RQI_I0I |
I01, I02, I03, I07 |
RQP_I04 |
I04 |
RQQ_Q09 |
Q09 |
RRA_O02 |
O02 |
RRA_O18 |
O18 |
RRD_O14 |
O14 |
RRE_O12 |
O12 |
RRG_O16 |
O16 |
RRI_I12 |
I12, I13, I14, I15 |
RSP_K11 |
K11 |
RSP_K21 |
K21 |
RSP_K22 |
K22 |
RSP_K23 |
K23, K24 |
RTB_K13 |
K13 |
SPQ_Q08 |
Q08 |
SQM_S25 |
S25 |
SQR_S25 |
S25 |
SRM_S01 |
S01, S02, S03, S04, S05, S06, S07, S08, S09, S10, S11 |
SRR_S01 |
S01, S02, S03, S04, S05, S06, S07, S08, S09, S10, S11 |
SSR_U04 |
U04 |
SSU_U03 |
U03 |
SUR_P09 |
P09 |
SUR_P09 |
P09 |
TBR_R08 |
R08 |
TBR_R09 |
R09 |
TCU_U10 |
U10, U11 |
UDM_Q05 |
Q05 |
VQQ_Q07 |
Q07 |
VXQ_V01 |
V01 |
VXR_V03 |
V03 |
VXU_V04 |
V04 |
VXX_V02 |
V02 |
ORU_W01 |
W01 |
QRF_W02 |
W02 |
The
LEN column in the data types table specifies the maximum length where there is
an agreed upon specification across chapters
Value |
Description |
LEN |
Table# |
Comment |
HL7 Section Reference |
|---|---|---|---|---|---|
AD |
Address |
0399/0190 |
Replaced by XAD as of v 2.3 |
2.9.1 |
|
CD |
Channel definition |
For waveform data only; See Chapter 7, Section 7.16.2 for full specifications. |
2.9.2 |
||
CE |
Coded element |
250 |
0396 |
2.9.3 |
|
CF |
Coded element with formatted values |
0396 |
2.9.4 |
||
CK |
Composite ID with check digit |
250 |
0061/0363 |
2.9.5 |
|
CM |
Composite |
Deprecated in v 2.3; retained for backward compatibility only. |
2.9.6 |
||
CN |
Composite ID number and name |
250 |
0360/0297/0363 |
Replaced by XCN as of v 2.3 |
2.9.7 |
CNE |
Coded with no exceptions |
250 |
0396 |
2.9.8 |
|
CP |
Composite price |
0205/0298 |
Replaces MO as of v 2.3. |
2.9.9 |
|
CQ |
Composite quantity with units |
In future versions, CQ fields should be avoided because the same data can usually be sent as two separate fields, one with the value and one with the units as a CE data type. |
2.9.10 |
||
CWE |
Coded with exceptions |
250 |
0396 |
2.9.11 |
|
CX |
Extended composite ID with check digit |
250 |
0061/0363/0203/ |
2.9.12 |
|
DLN |
Driver's license number |
0333 |
2.9.13 |
||
DR |
Date/time range |
2.9.14 |
|||
DT |
Date |
2.9.15 |
|||
ED |
Encapsulated data |
0191/0291/0299 |
Supports ASCII MIME-encoding of binary data. |
2.9.16 |
|
EI |
Entity identifier |
0363/0301 |
2.9.17 |
||
FC |
Financial class |
0064 |
2.9.18 |
||
FN |
Family name |
Appears ONLY in the PN and other PN-containing data types (PPN, XCN, XPN). |
2.9.19 |
||
FT |
Formatted text |
65536 |
2.9.20 |
||
HD |
Hierarchic designator |
0300/0301 |
2.9.21 |
||
ID |
Coded values for HL7 tables |
2.9.22 |
|||
IS |
Coded value for user-defined tables |
2.9.23 |
|||
JCC |
Job code/class |
0327/0328 |
2.9.24 |
||
MA |
Multiplexed array |
For waveform data only, see Chapter 7, Section <IP_ADDRESS>. |
2.9.25 |
||
MO |
Money |
Intent is that it appear only as a component of data type CP. Used independently in chapter 8, section 8.10.3. |
2.9.26 |
||
NA |
Numeric array |
For waveform data only, see Chapter 7, Section <IP_ADDRESS>. |
2.9.27 |
||
NM |
Numeric |
2.9.28 |
|||
PL |
Person location |
0302/0303/0304/0306/0305/0307/0308 |
2.9.29 |
||
PN |
Person name |
48 |
0360 |
Replaced by XPN as of v 2.3 |
2.9.30 |
PPN |
Performing person time stamp |
250 |
0360/0297/0363/0200/0061/0465/0448/0444 |
equivalent of an XCN joined with a TS |
2.9.31 |
PT |
Processing type |
0103/0207 |
2.9.32 |
||
QIP |
Query input parameter list |
2.9.33 |
|||
QSC |
Query selection criteria |
0209/0210 |
2.9.34 |
||
RCD |
Row column definition |
0440 |
2.9.35 |
||
RI |
Repeat interval |
0335 |
For scheduling data only. See Chapter 10 |
2.9.36 |
|
RP |
Reference pointer |
0191/0291 |
2.9.37 |
||
SAD |
Street Address |
Appears ONLY in the XAD data type. |
2.9.38 |
||
SCV |
Scheduling class value pair |
For scheduling data only. See Chapter 10 |
2.9.39 |
||
SI |
Sequence ID |
2.9.40 |
|||
SN |
Structured numeric |
2.9.41 |
|||
SRT |
Sort order |
0397 |
2.9.42 |
||
ST |
String |
199 |
2.9.43 |
||
TM |
Time |
2.9.44 |
|||
TN |
Telephone number |
Replaced by XTN as of v 2.3 |
2.9.45 |
||
TQ |
Timing/quantity |
For detailed specifications see Chapter 4, Section 4.3. |
2.9.46 |
||
TS |
Time stamp |
2.9.47 |
|||
TX |
Text data |
65536 |
2.9.48 |
||
VH |
Visiting hours |
0267 |
2.9.49 |
||
VID |
Version identifier |
0104 |
2.9.50 |
||
XAD |
Extended address |
250 |
0399/0190/0289/0288/0465 |
Replaces AD as of v 2.3 |
2.9.51 |
XCN |
Extended composite ID number and name |
250 |
360/297/363/200/61/203/465/448/444 |
Replaces CN as of v 2.3 |
2.9.52 |
XON |
Extended composite name and ID number for organizations |
250 |
0204/0061/0363/0203/0465 |
2.9.53 |
|
XPN |
Extended person name |
250 |
0360/0200/0465/0448/0444 |
Replaces PN as of v 2.3. |
2.9.54 |
XTN |
Extended telecommunications number |
250 |
0201/0202 |
Replaces TN as of v 2.3 |
2.9.55 |
Chapter
7 is the steward for the Coding Systems table. The table is copied here for
reader convenience.
Value |
Description |
Comment / Source |
Category |
99zzz or L |
Local general code (where z is an alphanumeric character) |
Locally defined codes for purpose of sender or receiver. Local codes can be identified by L (for backward compatibility) or 99zzz (where z is an alphanumeric character). |
General code |
ACR |
American College of Radiology finding codes |
Index for Radiological Diagnosis Revised, 3rd Edition 1986, American College of Radiology, Reston, VA. |
Specific Non-Drug Code |
ART |
WHO Adverse Reaction Terms |
WHO Collaborating Centre for International Drug Monitoring, Box 26, S-751 03, Uppsala, Sweden. |
Drug code |
AS4 |
ASTM E1238/ E1467 Universal |
American Society for Testing & Materials and CPT4 (see Appendix X1 of Specification E1238 and Appendix X2 of Specification E1467). |
Specific Non-Drug Code |
AS4E |
AS4 Neurophysiology Codes |
ASTM's diagnostic codes and test result coding/grading systems for clinical neurophysiology. See ASTM Specification E1467, Appendix 2. |
Specific Non-Drug Code |
ATC |
American Type Culture Collection |
Reference cultures (microorganisms, tissue cultures, etc.), related biological materials and associated data. American Type Culture Collection, 12301 Parklawn Dr, Rockville MD, 20852.<PHONE_NUMBER>. http://www.atcc.org |
Specific Non-Drug Code |
C4 |
CPT-4 |
American Medical Association, P.O. Box 10946, Chicago IL 60610. |
Specific Non-Drug Code |
C5 |
CPT-5 |
(under development - same contact as above) |
Specific Non-Drug Code |
CAS |
Chemical abstract codes |
These include unique codes for each unique chemical, including all generic drugs. The codes do not distinguish among different dosing forms. When multiple equivalent CAS numbers exist, use the first one listed in USAN. USAN 1990 and the USP dictionary of drug names, William M. Heller, Ph.D., Executive Editor, United States Pharmacopeial Convention, Inc., 12601 Twinbrook Parkway, Rockville, MD 20852. |
Drug code |
CD2 |
CDT-2 Codes |
American Dental Association's Current Dental Terminology (CDT-2) code. American Dental Association, 211 E. Chicago Avenue,. Chicago, Illinois 60611. |
Specific Non-Drug Code |
CDCA |
CDC Analyte Codes |
As above, for CDCM |
|
CDCM |
CDC Methods/Instruments Codes |
Public Health Practice Program Office, Centers for Disease Control and Prevention, 4770 Buford Highway, Atlanta, GA, 30421. Also available via FTP: ftp.cdc.gov/pub/laboratory _info/CLIA and Gopher: gopher.cdc.gov:70/11/laboratory_info/CLIA |
Drug code |
CDS |
CDC Surveillance |
CDC Surveillance Codes. For data unique to specific public health surveillance requirements. Epidemiology Program Office, Centers for Disease Control and Prevention, 1600 Clifton Rd, Atlanta, GA, 30333.<PHONE_NUMBER>. |
Specific Non-Drug Code |
CE |
CEN ECG diagnostic codes |
CEN PT007. A quite comprehensive set of ECG diagnostic codes (abbreviations) and descriptions published as a pre-standard by CEN TC251. Available from CEN TC251 secretariat, c/o Georges DeMoor, State University Hospital Gent, De Pintelaan 185-5K3, 9000 Gent, Belgium or Jos Willems, University of Gathuisberg, 49 Herestraat, 3000 Leuven, Belgium. |
Specific Non-Drug Code |
CLP |
CLIP |
Simon Leeming, Beth Israel Hospital, Boston MA. Codes for radiology reports. |
Specific Non-Drug Code |
CPTM |
CPT Modifier Code |
Available for the AMA at the address listed for CPT above. These codes are found in Appendix A of CPT 2000 Standard Edition. (CPT 2000 Standard Edition, American Medical Association, Chicago, IL). |
Specific Non-Drug Code |
CST |
COSTART |
International coding system for adverse drug reactions. In the USA, maintained by the FDA, Rockville, MD. |
Drug code |
CVX |
CDC Vaccine Codes |
National Immunization Program, Centers for Disease Control and Prevention, 1660 Clifton Road, Atlanta, GA, 30333 |
Drug code |
DCL |
DICOM Class Label |
From the Message Standards Classes table of the SNOMED-DICOM-Microglossary. College of American Pathologists, Skokie, IL, 60077-1034 |
Specific Non-Drug Code |
DCM |
DICOM modality codes |
Dean Bidgood, MD; Duke University Medical Center, Durham NC. Digital Imaging and Communications in Medicine (DICOM). From NEMA Publications PS-3.1 - PS 3.12: The ACR-NEMA DICOM Standard. National Electrical Manufacturers Association (NEMA). Rosslyn, VA, 22209., 1992, 1993, 1995 |
Specific Non-Drug Code |
DQL |
DICOM Query Label |
HL7 Image Management Special Interest Group, Health Level Seven, Ann Arbor, MI. |
Specific Non-Drug Code |
E |
EUCLIDES |
Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60. |
Specific Non-Drug Code |
E5 |
Euclides quantity codes |
Available from Euclides Foundation International nv (see above) |
Specific Non-Drug Code |
E6 |
Euclides Lab method codes |
Available from Euclides Foundation International nv, Excelsiorlaan 4A, B-1930 Zaventem, Belgium; Phone: 32 2 720 90 60. |
Specific Non-Drug Code |
E7 |
Euclides Lab equipment codes |
Available from Euclides Foundation International nv (see above) |
Specific Non-Drug Code |
ENZC |
Enzyme Codes |
Enzyme Committee of the International Union of Biochemistry and Molecular Biology. Enzyme Nomenclature: Recommendations on the Nomenclature and Classification of Enzyme-Catalysed Reactions. London: Academic Press, 1992. |
Specific Non-Drug Code |
FDDC |
First DataBank Drug Codes |
National Drug Data File. Proprietary product of First DataBank, Inc.<PHONE_NUMBER>, or http://www.firstdatabank.com. |
Drug code |
FDDX |
First DataBank Diagnostic Codes |
Used for drug-diagnosis interaction checking. Proprietary product of First DataBank, Inc. As above for FDDC. |
Drug code |
FDK |
FDA K10 |
Dept. of Health & Human Services, Food & Drug Administration, Rockville, MD 20857. (device & analyte process codes). |
Specific Non-Drug Code |
HB |
HIBCC |
Health Industry Business Communications Council, 5110 N. 40th St., Ste 120, Phoenix, AZ 85018. |
Specific Non-Drug Code |
HCPCS |
HCFA Common Procedure Coding System |
HCPCS: contains codes for medical equipment, injectable drugs, transportation services, and other services not found in CPT4. |
Specific Non-Drug Code |
HHC |
Home Health Care |
Home Health Care Classification System; Virginia Saba, EdD, RN; Georgetown University School of Nursing; Washington, DC. |
Specific Non-Drug Code |
HI |
Health Outcomes |
Health Outcomes Institute codes for outcome variables available (with responses) from Stratis Health (formerly Foundation for Health Care Evaluation and Health Outcomes Institute), 2901 Metro Drive, Suite 400, Bloomington, MN, 55425-1525;<PHONE_NUMBER> (voice);<PHONE_NUMBER> (fax<EMAIL_ADDRESS>See examples in the Implementation Guide. |
Specific Non-Drug Code |
HL7nnnn |
HL7 Defined Codes where nnnn is the HL7 table number |
Health Level Seven where nnnn is the HL7 table number |
General code |
HPC |
HCFA Procedure Codes (HCPCS) |
Health Care Financing Administration (HCFA) Common Procedure Coding System (HCPCS) including modifiers.[4] |
http://www.hcfa.gov/stats/anhcpcdl.ht[m]www.ntis.go[v]
Specific Non-Drug Code |
|||
I10 |
ICD-10 |
World Health Publications, Albany, NY. |
Specific Non-Drug Code |
I10P |
ICD-10 Procedure Codes |
Procedure Coding System (ICD-10-PCS.) See http://www/hcfa.gov/stats/icd10.icd10.htm for more information. |
Specific Non-Drug Code |
I9 |
ICD9 |
World Health Publications, Albany, NY. |
Specific Non-Drug Code |
I9C |
ICD-9CM |
Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105 (includes all procedures and diagnostic tests). |
Specific Non-Drug Code |
IBT |
ISBT |
International Society of Blood Transfusion. Blood Group Terminology 1990. VOX Sanquines 1990 58(2):152-169. |
Specific Non-Drug Code |
IC2 |
ICHPPC-2 |
International Classification of Health Problems in Primary Care, Classification Committee of World Organization of National Colleges, Academies and Academic Associations of General Practitioners (WONCA), 3rd edition. An adaptation of ICD9 intended for use in General Medicine, Oxford University Press. |
Specific Non-Drug Code |
ICDO |
International Classification of Diseases for Oncology |
International Classification of Diseases for Oncology, 2nd Edition. World Health Organization: Geneva, Switzerland, 1990. Order from: College of American Pathologists, 325 Waukegan Road, Northfield, IL, 60093-2750.<PHONE_NUMBER>. |
Specific Non-Drug Code |
ICS |
ICCS |
Commission on Professional and Hospital Activities, 1968 Green Road, Ann Arbor, MI 48105. |
Specific Non-Drug Code |
ICSD |
International Classification of Sleep Disorders |
International Classification of Sleep Disorders Diagnostic and Coding Manual, 1990, available from American Sleep Disorders Association, 604 Second Street SW, Rochester, MN 55902 |
Specific Non-Drug Code |
ISOnnnn |
ISO Defined Codes where nnnn is the ISO table number |
International Standards Organization where nnnn is the ISO table number |
General code |
IUPP |
IUPAC/IFCC Property Codes |
International Union of Pure and Applied Chemistry/International Federation of Clinical Chemistry. The Silver Book: Compendium of terminology and nomenclature of properties in clinical laboratory sciences. Oxford: Blackwell Scientific Publishers, 1995. Henrik Olesen, M.D., D.M.Sc., Chairperson, Department of Clinical Chemistry, KK76.4.2, Rigshospitalet, University Hospital of Copenhagen, DK-2200, Copenhagen. http://inet.uni-c.dk/~qukb7642/ |
Specific Non-Drug Code |
IUPC |
IUPAC/IFCC Component Codes |
Codes used by IUPAC/IFF to identify the component (analyte) measured. Contact Henrik Olesen, as above for IUPP. |
Specific Non-Drug Code |
JC8 |
Japanese Chemistry |
Clinical examination classification code. Japan Association of Clinical Pathology. Version 8, 1990. A multiaxial code including a subject code (e.g., Rubella = 5f395, identification code (e.g., virus ab IGG), a specimen code (e.g., serum =023) and a method code (e.g., ELISA = 022) |
Specific Non-Drug Code |
LB |
Local billing code |
Local billing codes/names (with extensions if needed). |
General code |
LN |
Logical Observation Identifier Names and Codes (LOINC®) |
Regenstrief Institute, c/o LOINC, 1050 Wishard Blvd., 5th floor, Indianapolis, IN 46202. 317/630-7433. Available from the Regenstrief Institute server at http://www. Regenstrief.org/loinc/loinc.htm. Also available via HL7 file server: FTP/Gopher (www.mcis.duke.edu/standards/ termcode/loinclab and www.mcis.duke.edu/standards/termcode/loinclin) and World Wide Web (http:// www.mcis.duke.edu/ standards/termcode/loincl.htm). January 2000 version has identifiers, synonyms and cross-reference codes for reporting over 26,000 laboratory and related observations and 1,500 clinical measures. |
Specific Non-Drug Code |
MCD |
Medicaid |
Medicaid billing codes/names. |
Specific Non-Drug Code |
MCR |
Medicare |
Medicare billing codes/names. |
Specific Non-Drug Code |
MDDX |
Medispan Diagnostic Codes |
Codes Used for drug-diagnosis interaction checking. Proprietary product. Hierarchical drug codes for identifying drugs down to manufacturer and pill size. MediSpan, Inc., 8425 Woodfield Crossing Boulevard, Indianapolis, IN 46240. Tel:<PHONE_NUMBER>. WWW: http://www.espan.com/medispan/pages/ medhome.html. As above for MGPI. |
Drug code |
MEDC |
Medical Economics Drug Codes |
Proprietary Codes for identifying drugs. Proprietary product of Medical Economics Data, Inc.<PHONE_NUMBER>. |
Drug code |
MEDR |
Medical Dictionary for Drug Regulatory Affairs (MEDDRA) |
Dr. Louise Wood, Medicines Control Agency, Market Towers, 1 Nine Elms Lane, London SW85NQ, UK Tel: (44)0<PHONE_NUMBER> WWW: http://www.open.gov.uk/mca/mcahome.htm |
Drug code |
MEDX |
Medical Economics Diagnostic Codes |
Used for drug-diagnosis interaction checking. Proprietary product of Medical Economics Data, Inc.<PHONE_NUMBER>. |
Drug code |
MGPI |
Medispan GPI |
Medispan hierarchical drug codes for identifying drugs down to manufacturer and pill size. Proprietary product of MediSpan, Inc., 8425 Woodfield Crossing Boulevard, Indianapolis, IN 46240. Tel:<PHONE_NUMBER>. |
Drug code |
MVX |
CDC Vaccine Manufacturer Codes |
As above, for CVX |
Drug code |
NDA |
NANDA |
North American Nursing Diagnosis Association, Philadelphia, PA. |
Specific Non-Drug Code |
NDC |
National drug codes |
These provide unique codes for each distinct drug, dosing form, manufacturer, and packaging. (Available from the National Drug Code Directory, FDA, Rockville, MD, and other sources.) |
Drug code |
NIC |
Nursing Interventions Classification |
Iowa Intervention Project, College of Nursing, University of Iowa, Iowa City, Iowa |
Specific Non-Drug Code |
NPI |
National Provider Identifier |
Health Care Finance Administration, US Dep't. of Health and Human Services, 7500 Security Blvd., Baltimore, MD 21244. |
Specific Non-Drug Code |
OHA |
Omaha System |
Omaha Visiting Nurse Association, Omaha, NB. |
Specific Non-Drug Code |
OHA |
Omaha |
Omaha Visiting Nurse Association, Omaha, NB. |
Specific Non-Drug Code |
POS |
POS Codes |
HCFA Place of Service Codes for Professional Claims (see http://www.hcfa.gov/medicare/poscode.htm). |
Specific Non-Drug Code |
RC |
Read Classification |
The Read Clinical Classification of Medicine, Park View Surgery, 26 Leicester Rd., Loughborough LE11 2AG (includes drug procedure and other codes, as well as diagnostic codes). |
Specific Non-Drug Code |
SDM |
SNOMED- DICOM Microglossary |
College of American Pathologists, Skokie, IL, 60077-1034. (formerly designated as 99SDM). |
Specific Non-Drug Code |
SNM |
Systemized Nomenclature of Medicine (SNOMED) |
Systemized Nomenclature of Medicine, 2nd Edition 1984 Vols 1, 2, College of American Pathologists, Skokie, IL. |
Specific Non-Drug Code |
SNM3 |
SNOMED International |
SNOMED International, 1993 Vols 1-4, College of American Pathologists, Skokie, IL, 60077-1034.. |
Specific Non-Drug Code |
SNT |
SNOMED topology codes (anatomic sites) |
College of American Pathologists, 5202 Old Orchard Road, Skokie, IL 60077-1034. |
Specific Non-Drug Code |
UC |
UCDS |
Uniform Clinical Data Systems. Ms. Michael McMullan, Office of Peer Review Health Care Finance Administration, The Meadows East Bldg., 6325 Security Blvd., Baltimore, MD 21207;<PHONE_NUMBER>. |
Specific Non-Drug Code |
UMD |
MDNS |
Universal Medical Device Nomenclature System. ECRI, 5200 Butler Pike, Plymouth Meeting, PA 19462 USA. Phone:<PHONE_NUMBER>, Fax:<PHONE_NUMBER>. |
Device code |
UML |
Unified Medical Language |
National Library of Medicine, 8600 Rockville Pike, Bethesda, MD 20894. |
Specific Non-Drug Code |
UPC |
Universal Product Code |
The Uniform Code Council. 8163 Old Yankee Road, Suite J, Dayton, OH 45458;<PHONE_NUMBER> |
Specific Non-Drug Code |
UPIN |
UPIN |
Medicare/HCFA's universal physician identification numbers, available from Health Care Financing Administration, U.S. Dept. of Health and Human Services, Bureau of Program Operations, 6325 Security Blvd., Meadows East Bldg., Room 300, Baltimore, MD 21207 |
Specific Non-Drug Code |
W1 |
WHO record # drug codes (6 digit) |
World Health organization record number code. A unique sequential number is assigned to each unique single component drug and to each multi-component drug. Eight digits are allotted to each such code, six to identify the active agent, and 2 to identify the salt, of single content drugs. Six digits are assigned to each unique combination of drugs in a dispensing unit. The six digit code is identified by W1, the 8 digit code by W2. |
Drug code |
W2 |
WHO record # drug codes (8 digit) |
World Health organization record number code. A unique sequential number is assigned to each unique single component drug and to each multi-component drug. Eight digits are allotted to each such code, six to identify the active agent, and 2 to identify the salt, of single content drugs. Six digits are assigned to each unique combination of drugs in a dispensing unit. The six digit code is identified by W1, the 8 digit code by W2. |
Drug code |
W4 |
WHO record # code with ASTM extension |
With ASTM extensions (see Implementation Guide), the WHO codes can be used to report serum (and other) levels, patient compliance with drug usage instructions, average daily doses and more (see Appendix X1 the Implementation Guide). |
Drug code |
WC |
WHO ATC |
WHO's ATC codes provide a hierarchical classification of drugs by therapeutic class. They are linked to the record number codes listed above. |
Drug code |
The
actual interpretation of Yes/No is context sensitive. Individual chapters will
further refine the meaning of Yes/No in their specific context.
Value |
Description |
|---|---|
Y |
Yes |
N |
No |
LAB
acknowledges the message that ADT sent identified as ZZ9380. (LAB and ADT, the
sending and receiving system IDs, are site-defined.) Both systems are
associated with the same FACILITY, 767543. The AA code in the MSA
segment indicates that the message was accepted by the application.
MSH|^~\&|LAB|767543|ADT|767543|19900314130405||ACK^^ACK_ACK|XX3657|P|2.4<cr>
MSA|AA|ZZ9380<cr>
The
AR code in MSA indicates that the application rejected the message for
functional reasons. The optional ERR segment includes here that the 16th field
of the PID segment with the SET ID value of 1 had an error which was defined by
the locally-established code X3L. The optional text message UNKNOWN COUNTY
CODE in the link is designed to help programmers and support personnel while
reviewing message logs.
MSH|^~\&|LAB|767543|ADT|767543|199003141304-0500|| ACK^^ACK_ACK
|XX3657|P|2.4<cr>
MSA|AR|ZZ9380|UNKNOWN COUNTY CODE<cr>
ERR|PID^1^16^X3L<cr>
The
sender initiates the link with a message that has no functional content. The
sequence number is 0. The message type and event code are not used.
MSH|^~\&|ADT|767543|LAB|767543|199003141304-0500||^|XX3657|P|2.4|0<cr>
The responder uses a general acknowledgment. The expected sequence number is
1.
MSH|^~\&|LAB|767543|ADT|767543|199003141304-0500|| ACK^^ACK_ACK
|ZZ9380|P|2.4<cr>
MSA|AA|XX3657||1<cr>
This
summarizes the methodology for splitting a single logical HL7 message among two
or more actual HL7 messages. The actual specifications for this, the segment
definitions of the ADD and DSC segments, and examples are in Section 2.14.2,
"Continuation messages and segments".
Continuing of messages is a generic methodology that can be used for all HL7
message types. It can be used to split based on segment boundaries, on field
boundaries, and to split a single field among several messages. It utilizes
two specific segments, ADD and DSC, as well as a field in the message header,
MSH-14-Continuation pointer.
When a message is continued, a unique continuation value is used. This same
value will appear in MSH-14 and DSC-1 as appropriate for a single pair of
messages. This allows messages to be "chained together".
Here are two examples of ways to create continuation pointers for fragmented
messages. The only absolute requirement is that when the sending application
values the continuation pointer, the receiving application can appropriately
reconstruct the message.
Sitecode-interfaceapplicationcode-date-sequentialcounterwithindate
This will guarantee uniqueness of this field.
e.g. BWH-LDS-19990331-27 for the 27th large message to be created on
March 31, within the Discharge Summary interfaces at BWH
An alternative method of valuing the continuation pointer:
Sitecode-interfaceapplicationcode-medicalrecordnumber-datetime
e.g. MGH-PCIS-1234567-19980331121314 for a message created on March 31, at
12:13:14pm for patient medical record number 1234567, within the PCIS
interfaces at MGH
Sending Application Note: In the ADD segment, a trailing field delimiter, i.e.
the vertical bar character, after the final field, has explicit meaning. The
sending application should not include a trailing field delimiter for the last
field in the ADD segment unless it has completely valued the entire field from
the message being continued.
Receiving Application Note: The receiving application will need to be concerned
with a single segment and a single field being continued.
Receiving a message with an empty ADD segment followed by a DSC segment is the
notification that the segment preceding the ADD is being continued in a
subsequent message. Note that the continuing message may not be the next one
received! The receiver must match up the continuation pointer value from
MSH-14 of subsequent messages to the DSC-1 continuation pointer value of the
prior message. Also if the continuing message contains an ADD segment, the
receiver should continue appending to the fields from the segment being
continued with values from the ADD segment. For example, if OBX-5 is being
continued, the continuation will appear in ADD-1 of the continuing message. If
there were a value for OBX-13 of the original message, that would appear in
ADD-9 of the continuing message, assuming that the remainder of the OBX segment
fit into the single ADD segment.
Question: if continuing a message after the completion of a complete segment,
should the continuing message have an empty ADD segment or not? Answer: No.
This means that a continuing message need not have an ADD segment, if the
continued message was split on a segment boundary.
Notation conventions: items within angle brackets are comments and not intended
to represent a portion of an actual message. For example, <this is a
comment>.
Note the multiple continuation pointer values, one for each pair of physical
messages.
Message 1
MSH|...|<field-13>||...
PID|...
ORC|...
OBR|...
OBX|1|FT|^Discharge Summary|1|This is the first sentence of a long
message. This is the second sentence of a long message.
<snip>
This is the 967th sentence of "
ADD|
DSC|BWH-LDS-19990405-6|
Message 2
MSH|...|<field-13>|BWH-LDS-19990405-6|
ADD|a long message. This is the 968th sentence of a long
message.
<snip>
This is the 1001st line of
<there should be no trailing field delimiter after the last field in
this ADD segment>
DSC|BWH-LDS-19990405-7|
Message 3
MSH|...|<field-13>|BWH-LDS-19990405-7|
ADD|a long message. This is the 1002nd sentence of a long message.
<snip> This is the final sentence of this long
message!|||||F||199707211325|
DG1|...
<end of message>
The following examples discuss an unsolicited transmission of an observation
message, ORU^R01.
The expected result values in OBX-5, Observation Value, for reports (e.g.
autopsy, pathology) may exceed the message length restrictions of one or more
interfaces.
Thus the OBX-5, Observation Value data element will be split into more than one
message.
Here's an example intended to illustrate the interpretation of Chapter 2 and 7.
It reflects a single logical message broken up into three distinct messages.
Example 1, a single field being split across three messages
Message #1: ---------------------------------------------------------------
Note: MSH-14, continuation pointer, is empty.
MSH|...|<field-13>||...
PID|...
ORC|...
OBR|...
OBX|1|FT|^Discharge Summary|1|This is the first sentence of a long
message. This is the second sentence of a long message.
<snip>
This is the 967th sentence of "
ADD|
DSC|<continuation-pointer-value-1>|F
Message #2: --------------------------------------------------------------
Note: MSH-14, continuation pointer, is valued with the same value as in DSC-1,
continuation pointer from the message this is continuing, in this case Message
#1.
MSH|...|<field-13>|<continuation-pointer-value-1>|
ADD|a long message. This is the 968th sentence of a long
message.
<snip>
This is the 1001st line of
<there should be no trailing field delimiter after the last field in this
ADD segment>
DSC|<continuation-pointer-value-2>|F
Message #3: ---------------------------------------------------------------
Note: MSH-14, continuation pointer, is valued with the same value as in DSC-1,
continuation pointer from the message this is continuing, in this case Message
#1.
MSH|...|<field-13>|<continuation-pointer-value-2>|
ADD|a long message. This is the 1002nd sentence of a long message.
<snip> This is the final sentence of this long
message!|||||F||199707211325|
<remaining segments after the big OBX from the original message go here,
after the ADD segment>
PR1|...
DG1|...
Example 2, a single message being split across two messages, but on segment
boundaries
Message #1: ---------------------------------------------------------------
Note: MSH-14, continuation pointer, is empty.
MSH|...|<field-13>||...
PID|...
ORC|...
OBR|...
OBX|1|FT|^Discharge Summary|1|This is the first sentence of a long
message. This is the final sentence of this long discharge
summary!|||||F||199707211325|
DSC|<continuation-pointer-value-3>|F
Message #2: --------------------------------------------------------------
Note: MSH-14, continuation pointer, is valued with the same value as
in DSC-1, continuation pointer from the message this is continuing, in this
case Message #1.
Note that no ADD segment is necessary, since a segment is not being split
across two messages.
MSH|...|<field-13>|<continuation-pointer-value-3>|
PR1|...
DG1|...
This example shows the lab system using the Master Files specification to send two update test dictionary entries to an ICU system. The OM1 (observation dictionary) segment, currently under development by HL7 and ASTM, carries the dictionary information. Several varieties of acknowledgment are shown. The choice of acknowledgment mode is site-specific.
MSH|^~\&|LABxxx|ClinLAB|ICU||19910918060544||MFN^M03|MSGID002|P|2.2
MFI|LABxxx^Lab Test Dictionary^L|UPD|||AL
MFE|MUP|199109051000|199110010000|12345^WBC^L
OM1|...
MFE|MUP|199109051015|199110010000|6789^RBC^L
OM1|...
Original mode acknowledgment of the HL7 message according to MFI Response Level
Code of AL.
MSH|^~\&|ICU||LABxxx|ClinLAB|19910918060545||MFK|MSGID99002|P|2.2
MSA|AA|MSGID002
MFI|LABxxx^Lab Test Dictionary^L|UPD|||MFAA
MFA|MUP|199110010000|199110010040|S|12345^WBC^L
MFA|MUP|199110010000|199110010041|S|6789^RBC^L
MSH|^~\&|LABxxx|ClinLAB|ICU||19910918060544||MFN^M03|MSGID002|P|2.2|||AL|AL
MFI|LABxxx^Lab Test Dictionary^L|UPD|||AL
MFE|MUP|199109051000|199110010000|12345^WBC^L
OM1|...
MFE|MUP|199109051015|199110010000|6789^RBC^L
OM1|...
MSH|^~\&|ICU||LABxxx|ClinLAB|19910918060545||MSA|MSGID99002|P|2.2
MSA|CA|MSGID002
MSH|^~\&|ICU||LABxxx|ClinLAB|19911001080504||MFK|MSGID5002|P|2.2|||AL|
MSA|AA|MSGID002
MFI|LABxxx^Lab Test Dictionary^L|UPD|||MFAA
MFA|MUP|199109051000|199110010040|S|12345^WBC^L
MFA|MUP|199109051015|199110010041|S|6789^RBC^L
MSH|^~\&|LABxxx|ClinLAB|ICU||19911001080507||ACK|MSGID444|P|2.2
MSA|CA|MSGID5002
Note:
If the MFN message in Section <IP_ADDRESS>, "Enhanced mode example" had not
required an application acknowledgment at the message level (i.e., the
application acknowledgment code of the MSH segment = NE), the (Master Files
Chapter defined) MFD message could be used to provide a delayed application
level acknowledgment not tied to the original MFN message.
The following example includes an acknowledgment for an MFE segment not in the
original message. This additional MFE was sent via another MFN message.
MSH|^~\&|LABxxx|ClinLAB|ICU||19910918060544||MFN^M03|MSGID002|P|2.2|||AL|NE
MFI|LABxxx^Lab Test Dictionary^L|UPD|||AL
MFE|MUP|199109051000|199110010000|12345^WBC^L
OM1|...
MFE|MUP|199109051015|199110010000|6789^RBC^L
OM1|...
MSH|^~\&|ICU||LABxxx|ClinLAB|19910918060545||MSA|MSGID99002|P|2.2
MSA|CA|MSGID002
MSH|^~\&|ICU||LABxxx|ClinLAB|19911001080504||MFD|MSGID65002|P|2.2|||AL|
MFI|LABxxx^Lab Test Dictionary^L|UPD|||MFAA
MFA|MUP|199109051000|199110010040|S|12345^WBC^L
MFA|MUP|199109051015|199110010041|S|6789^RBC^L
MFA|MUP|199109051025|199110010041|S|4339^HGB^L
MSH|^~\&|LABxxx|ClinLAB|ICU||19911001080507||ACK|MSGID444|P|2.2
MSA|CA|MSGID65002
The
following items are being discussed in the Control/Query technical committee
for addition to future versions of HL7:
1) Rationalization and clarification of event structures.
2) Creation of a network server for HL7 tables so that updates to them can be
made public immediately, rather than waiting until the publication of the next
version of the Standard.
3) Consideration of security. There are in general two types: application
level security, which is partially addressed by the security field in
the MSH segment. The second type, network security, needs to be addressed in
the HL7 Implementation Guide. There are several commercially available
encryption-based approaches to network level security.
4) Reviewing network application management messages for possible upgrade
requirements.
5) Creation of Implementation Technology Specifications (ITSs: encoding rules
equivalents) for Version 3.
6) Specification of query functionality for version 3.
Available from ISO 1 Rue de Varembe, Case Postale 56, CH 1211, Geneva, Switzerland.[2 ]
Available from ISO 1 Rue de Varembe, Case Postale 56, CH 1211, Geneve,
Switzerland[3] Available from The Unicode
Consortium, P.O. Box 700519, San Jose, CA 95170-0519. See
http://www/unicode.org/unicode/consortium/consort.html[4 The HCPCS code is divided into three "levels." Level I
includes the entire CPT-4 code by reference. Level II includes the American
Dental Association's Current Dental Terminology (CDT-2) code by reference.
Level II also includes the genuine HCPCS codes, approved and maintained jointly
by the Alpha-Numeric Editorial Panel, consisting of HCFA, the Health Insurance
Association of America, and the Blue Cross and Blue Shield Association. Level
III are codes developed locally by Medicare carriers. The HCPCS modifiers are
divided into the same three levels, I being CPT-4 modifiers, II CDT-2 and
genuine HCPCS modifiers, and III being locally agreed
mod]ifiers.
The genuine HCPCS codes and modifiers of level II can be
found at [. HCFA distributes the HCPCS codes via
the National Technical Information Service (NTIS, ) and NTIS distribution
includes the CDT-2 part of HCPCS Level II, but does not include the CPT-4 part
(Level I). HCFA may distribute the CPT-4 part to its contractors.


My name is Nicholas. I began programming only a couple of months ago and I have been having fun making things along the way.
This webpage showcases some of the projects I have completed since I began coding. Check back on this site for updated material.


{% load static %}
{{editProd.itemName}}
Log Out
Dashboard
Shops
Categories
Products
Click to update basic Product information
{% csrf_token %}
Product Name:
Product Description:
{{editProd.itemDescription}}
Price:
Link to Product Image:
# of available products:
Update Product
Click to assign to your Shop
{% csrf_token %}
Chose the Shop:
{% for shop in ownerShops %}
{{shop.shopName}}
{% endfor %}
Add Shop
Click to assign Categories
{% csrf_token %}
Select Categories
{% for cat in allCats %}
{{cat.catName}}
{% endfor %}
Add Category
Delete Product


Verifying an Alien Dictionary
In an alien language, surprisingly they also use english lowercase letters, but possibly in a different order. The order of the alphabet is some permutation of lowercase letters. Given a sequence of words written in the alien language, and the order of the alphabet, return true if and only if the given words are sorted lexicographicaly in this alien language. Example 1 Input: words = ["hello","leetcode"], order = "hlabcdefgijkmnopqrstuvwxyz" Output: true Explanation: As 'h' comes before 'l' in this language, then the sequence is sorted.


{{/* This is the template that will be used for the "sarga" list page. */}} {{ define "main" }}
This alignment between audio and text is the fantastic work of Avinash Varna (see here), but the ugliness of this website is (so far) entirely my own.
{{ $prettyNames := (dict "Kanda_1_BK" "Kāṇḍa 1: Bāla-kāṇḍa" "Kanda_2_AYK" "Kāṇḍa 2: Ayodhyā-kāṇḍa" "Kanda_3_ARK" "Kāṇḍa 3: Araṇya-kāṇḍa" "Kanda_4_KSK" "Kāṇḍa 4: Kiṣkindhā-kāṇḍa" "Kanda_5_SK" "Kāṇḍa 5: Sundara-kāṇḍa" "Kanda_6_YK" "Kāṇḍa 6: Yuddha-kāṇḍa") }}


Report: Falcons RB Freeman, TE Hooper to have MRIs
Atlanta Falcons running back Devonta Freeman and tight end Austin Hooper are having MRI exams Monday to determine the extent of their injuries, NFL Network’s Ian Rapoport reported.
Freeman initially was diagnosed with a foot sprain following the Falcons’ 26-9 upset in New Orleans on Sunday. Hooper left the game with a knee injury.
Freeman rushed 10 times for 38 yards and caught three passes for 10 yards and did not play in the second half against the Saints. Hooper caught four passes for 17 yards, including an 8-yard touchdown in the second quarter.
Freeman, 27, has rushed for 371 yards and no touchdowns in nine starts this season, adding 38 catches for 282 yards and three scores.
Hooper, 25, has a team-high 56 receptions for 608 yards in nine games. He also leads the Falcons with six touchdown grabs.
Backup Brian Hill would be in line to start Sunday at Carolina if Freeman can’t go. Hill, 24, rushed for 61 yards on 20 carries and caught a 10-yard touchdown pass against New Orleans.
Veteran Luke Stocker, 31, is the No. 2 tight end on Atlanta’s roster. Primarily a blocker, he has six catches for 34 yards this season.
—Field Level Media


Presentations and relevant information relative to the Second Meeting on the Implementation of the Plan of Action on Subnational Governments, Cities and Other Local Authorities on Biodiversity, Bonn, Germany, 5-6 September 2011
Presentations
-
The Singapore Index On Cities’ Biodiversity , Dr. Lena Chan, National Biodiversity Centre, National Parks Board Singapore
-
CBD Plan of Action on Subnational Governments, Cities and other Local Authorities-Status and perspectives for implementation, Kobie Brand, ICLEI – CBC; Oliver Hillel, Secretariat of the CBD
-
Project Partnerships of Bonn Maria Hohn-Berghorn, City of Bonn, Germany
-
Biodiversity in Cities – A Biodiversity Exhibition Project Among Leader Cities Dr. José Bernal Stoopen, Secretaría del Medio Ambiente, Gobierno de la Ciudad de México
-
Welcome to Participants Krishna Babu, Greater Hyderabad Municipal Corporation, India
-
TEEB Manual for Cities: Ecosystem Services in Urban Management Marlene Laros, ICLEI-Cities Biodiversity Centre, South Africa
-
BiodiverCities Programme Kobie Brad, ICLEI
-
Biodivercities Guilherme Mattar, Sao Paolo, Brazil
-
Contribution to the Panel Discussion “Dialogue with other International Organisations” Fabrice Renaud, UNU, Germany
-
The Singapore Index On Cities’ Biodiversity Dr. Lena Chan, National Biodiversity Centre, National Parks Board Singapore
-
Cities And Biodiversity Outlook I, A Global Assessment Of The Links Between Urbanization, Biodiversity And Ecosystem Services, Thomas Elmqvist, Stockholm resilience Centre, Stockholm University
-
Decentralised Cooperation of Paris- Algiers- Phnom Penh Fabienne Giboudeaux, City of Paris, France
-
Working towards a win-win-win scenario in Durban: Green economy - climate change adaptation - biodiversity protection Dr Debra Roberts, EThekwini Municipality, Durban, South Africa
-
UN-HABITAT, project examples and perspectives Andrew Rudd, UN-HABITAT, Nairobi, Kenya
-
Lifeweb Project La Paz Ariane Steinsmeier, The Nature Conservancy Steinsmeier.pdf
-
Biodiversity and Agriculture Dr Edelgard Von Houwald, German federal Ministry of Food, Agriculture and Consumer Protection, Germany
Relevant documents/announcements
Presentations and documents from the First Meeting on the Implementation of the Plan of Action on Subnational Governments, Cities and Other Local Authorities on Biodiversity 2011-2020, January 2011, Montpellier, France
The meeting report is available on the meeting's documents webpage. You can also view the meeting's Project factsheet provided in the meeting as well as pictures of objectives, theme clouds and ideas market.
Presentations
Presentations made during The Second Expert Workshop on the Development of the City Biodiversity Index (Singapore, July 2010)
Presentations made during The Second Curitiba Meeting on Cities and Biodiversity (Curitiba, Brazil, January 2010)
-
Mr. Eric Blencowe, UK CBD Focal Point, Head, International Biodiversity Policy Unit: The “Biodiversity Duty” (Natural Environment and Rural Communities Act 2006)
-
Ms. Moramay Navarro, UNESCO: “Fostering a Green Society through the URBIS Initiative”
-
Mr. Augustin Berghöfer, Helmholtz Centre for Environmental Research UFZ, Leipzig, TEEB Scientific Coordination Team : “TEEB – The Economics of Ecosystems and Biodiversity”
-
Ms. Bonnie James, CBD National Focal Point for Canada : “Working Together to Sustain Urban Biodiversity and Enrich the Quality of Life in Cities”
-
Mr. Andre Mader, ICLEI and Mr. Chikara Hombo, CBD Secretariat : “Guidebooks for biodiversity management: twin publications by ICLEI and the CBD Secretariat”
-
Mr. Michael Delafosse and Mr Phillipe Croze, City of Montpellier, France: “Montpellier Cultivates Biodiversity”
-
Mr. João Manuel Linck Feijó, Presidente da Associação Telhado Verde Brasil, Membro da World Green Infrastructure Network: “Índice de Área Ecológica Efetiva”
-
Ms. Karin Burhen, UN-Habitat: “Sustainable Urban Development -Adequate shelter for all”
-
Ms. Chantal Robichaud, CBD Secretariat: “Integrating Biodiversity Considerations into Urban Infrastructure Development”
-
Mr. Hélio Neves, City of Sao Paolo :“Cities And Biodiversity Local Initiatives-Sao Paolo”
-
Mr. Peter Werner, Institute for Housing and Environment (IWU), Darmstadt, Germany, COmpetence NeTwork URban ECology – CONTUREC :“Urbanites meet Urban Biodiversity - Case Studies from Germany” (presentation not available on line. For further information please contact Mr Werner at<EMAIL_ADDRESS>-
Mr. Jose Bernal, Director General, Dirección General de Zoológicos y Vida Silvestre, Secretaría del Medio Ambiente, Gobierno de la Ciudad de México: “The Experience of Mexico City”
-
Ms. Irene Duarte and Mr. Edson Carvalho : “Alta Floresta, Mato Grosso – Estratégia Para O Desenvolvimento Sustentável Da Amazônia”
-
Ms. Malu Nunes, Executive Director of the Boticario Fundação: “Oasis Project, Nature Conservation toward life protection”
-
Ms. Wendy Yap, National Parks Board, Singapore: “Singapore Index on Cities’Biodiversity”
-
Mr. Alfredo Trindade, City of Curitiba: “Testing of the Singapore Index on Cities’ Biodiversity by the City of Curitiba”
-
Mr. Masashi Kato, Adviser, Environmental Affairs Bureau, City of Nagoya: “Testing of the index by the City of Nagoya”
-
Mr. Toshio Fujii, Secretary-General, Aichi-Nagoya COP10 CBD Promotion Committee presented “COP10 Aichi-Nagoya Plan”
-
Mr. Masashi Kato, Adviser, Environmental Affairs Bureau, City of Nagoya: “Towards the City Biodiversity Summit 2010”
-
Mr. Tadayoshi Inoue and Mr. Yukihiro Morimoto, Co-Chairs, Organizing Committee, URBIO 2010 International: “Urban Biodiversity & Design”
-
Ms. Chantal Robichaud, Programme Assistant, CBD Secretariat: "International Year of Biodiversity”
-
Mr. Miguel Milano, Board Vice Chair, Life Certification: “Present situation and short term plans of Life Certification”
Presentations made during the meeting on "Cities and Biodiversity: Achieving the 2010 Biodiversity Target" (Curitiba, Brazil, March 2007)
-
AICHI, JAPAN: Invitation from Aichi/Nagoya, Japan, to COP10 in 2010
-
BELO HORIZONTE, BRAZIL: Cidades e Biodiversidade
-
BONN, GERMANY: Local Action, Global Interaction: The New Bonn, Focus on Sustainability
-
CAPE TOWN, SOUTH AFRICA: City of Cape Town and Reintroducing the extinct Cape Flats Erica (Erica verticillata): Bungy jumping on the brink of extinction...
-
COMPETENCE NETWORK URBAN ECOLOGY (CONTUREC), GERMANY: Distinctive Characteristics of Urban Biodiversity
-
COUNTDOWN 2010, WORLD CONSERVATION UNION: Countdown 2010: The Role of Local Authorities
-
CURITIBA, BRAZIL: Programa Biodiversidade Urbana - Biocity
-
DURBAN, SOUTH AFRICA: Ethekwini Environmental Services Management Plan (EESMP) - from Planning to Implementation: Protecting biodiversity in eThekwini Municipality
-
GOIANIA, BRAZIL: Biodiversidade: Gerenciamento da Biodiversidade Urbana e Promoçao da Conscientizaçao da Biodiversidade em Communidades Urbanas
-
JOHANNESBURG, SOUTH AFRICA: Presentation on Johannesburg's Biodiversity Programme
-
LOCAL ACTION FOR BIODIVERSITY: Local Action for Biodiversity... enhancing urban nature through a global network of local governments
-
MONTREAL, CANADA: Managing Urban Biodiversity and Promoting Awareness of Biodiversity to Urban Communities andThe Montreal's Nature Museums: dedicated to the protection of biodiversity
-
NAGOYA, JAPAN: Cities and Biodiversity: Achieving the 2010 Target, Managing Urban Biodiversity
-
NAIROBI, KENYA: Managing urban biodiversity in Kenya - Nairobi experience
-
PORTO ALEGRE, BRAZIL: Iniciativas de Porto Alegre para Conservaçao da Diversidade Biologica
-
SAO PAULO, BRAZIL: Preserving Biodiversity in Sao Paulo
-
UNITED NATIONS ENVIRONMENT PROGRAMME (UNEP): Cities, Ecosystems and Biodiversity


Cookie Sales
Home
New Shop Location
Minimum number of customers per hour?
Maximum number of customers per hour?
Average number of cookies sales per customer?


{%- include head.html -%}
{%- include header.html -%}
{% include nav.html %}
{{ content }}
{%- include footer.html -%}


(function() { var tmpl; tmpl = toffee.templates["/"] = { bundlePath: "/" }; tmpl.render = tmpl.pub = function(__locals) { var supply, __repress, _i, _len, _ln, _ref, _to, _ts; __locals = __locals || {}; __repress = (_ref = __locals.__toffee) != null ? _ref.repress : void 0; _to = function(x) { return __locals.__toffee.out.push(x); }; _ln = function(x) { return __locals.__toffee.lineno = x; }; _ts = function(x) { return __locals.__toffee.state = x; }; toffee.__augmentLocals(__locals, "/"); with (__locals) {; __toffee.out = []; _ts(1); _ts(2); for (_i = 0, _len = supplies.length; _i < _len; _i++) { supply = supplies[_i]; _ts(1); _ts(1); _ln(2); _to("


--- layout: post title: Summertime, the living is easy category: - Analog - BlackAndWhite - Street Photos tags: - 35mm - analog - antoniocapelo - fed3b - fotografia - photography - porto - rangefinder - shutter hell up - street - vila do conde status: publish type: post published: true --- Yes, it is..
skater girl, riding alone at night
killing spree!
"Geezus, please stop playing halo...I'll pay you.." xD
Don't mess with ma dog.
"Is that the way you say it? That's a Bingo?" (Col. Hans Landa)
Urban Music magazine cover
Caqui
"The Fall of Marcelo", in theaters July 2011
More band-like photos
Late night snack
Is it a cat? Or is it a dog?
Next post I'll show the first walk with my new baby:


Before Change
graph.create_xref(out=fp)
data = fp.getvalue()
r = ET.fromstring(data)
def test_itergraphreport(self):
// XXX: This test is far from optimal, it just ensures
// that all code is exercised to catch small bugs and
After Change
tree = etree.parse(StringIO(data), parser)
assert tree is not None
// Verify no `errors <https://lxml.de/parsing.html//error-log>`_ occurred.
assert len(parser.error_log) == 0
def test_itergraphreport(self):
// XXX: This test is far from optimal, it just ensures
// that all code is exercised to catch small bugs and


{% load nonce %}
{{SITE_NAME}} is able to look at list of your friends to see which are already using {{SITE_NAME}}. You will be redirected to another site so that you can authorize {{SITE_NAME}} to access a list of your contacts.
We don't store any of this information.


You successfully created your own template. Start editing it by hovering the "Manage" button and opening the "Edit Template" dialog.


libfprint DEMO
Users
(current)
Identify
No users yet!
Users
New User
Name
Email
Enroll
Enroll/Verify


Members of the team
SEARCHING
TOOL
Query
Select a pre-defined query...
what similarity laws must be obeyed when constructing aeroelastic models of heated high speed aircraft
what are the structural and aeroelastic problems associated with flight of high speed aircraft
what problems of heat conduction in composite slabs have been solved so far
can a criterion be developed to show empirically the validity of flow solutions for chemically reacting gas mixtures based on the simplifying assumption of instantaneous local chemical equilibrium
what theoretical and experimental guides do we have as to turbulent couette flow behaviour
is it possible to relate the available pressure distributions for an ogive forebody at zero angle of attack to the lower surface pressures of an equivalent ogive forebody at angle of attack
Retrieved documents
‹
›


Upcoming Tests
No upcoming test?
Find out what's happening in your area in the near future.
Find tests
Your Articles Most Viewed
Time-Saving Tools designed with the research process in mind.
Curriculum assessment and development
Student recruitment and retention
Invite people to join Taksh
Add an invitation message


| DOSE: |
3 Tbsp |
oral |
Nutmeg |
(ground / crushed) |
Nutmeg as a drug first came to my attention after seeing the movie 'Malcolm X', wherein Malcolm , while in prison, is given nutmeg to help him kick his habit. I happened to be discussing this with my boss, and she told me that she had heard that one tablespoon of nutmeg will keep you high all day. Well, the very next day, she brought in a jar of nutmeg, and the experiments began. She only took about one or two teaspoons, I scooped about two heaping tablespoons into my coffee, which made the coffee taste terrible. I had to wash the coffee down with water. I scooped some more nutmeg into the coffee. Afterward, I spooned out the nutmeg residue at the bottom of the cup and ate that, too. And then I waited...
After a while, I started feeling a warmth over my body, and everything became kinda funny to me. The small group that I worked with had a meeting, and just about everything that was spoken about seemed funny to me. I began to laugh at almost everything. I felt like I had a nice buzz going on. Back at my desk, I had my little tinny radio playing, and a Four Seasons song came on. I happened to be holding a pair of scissors in my hand. I sat there, holding the scissors up at eye level, staring at them as I listened to this Four Seasons song.
It sounded as if I were right there in the studio with Frankie Valli and the boys, and I could hear somebody hitting wrong notes in the background! Needless to say, my audio perceptions were greatly enhanced. After a while, I realized that I was sitting there staring at a pair of scissors. I didn't know how long I was sitting there doing this, but I decided to put the scissors down before someone noticed.
My boss came over and asked me how I felt. I went into some long, drawn out dialogue about something, and when I finished, I couldn't remember what I had just talked about! That's when I realized that maybe it was time for me to go home. My boss agreed. It had been about 3 and a half hours since I took the nutmeg, and the 'nice buzz' was starting to get intense.
As I was getting my things together, a couple of friends came over to my desk to show me some T-Shirts that they had made. I couldn't, for the life of me, make out the designs on the shirts. It was just splashes of color to me. The two of them stood there smiling as they told me about the shirts. My boss came out and cut them off, telling them that I had to leave on company business. When she did that, their faces seemed to ripple, like two puddles of water. It was like their smiling faces rippled into frowning faces. I was like...'Wow!'.
It was around this time that everything seemed to be in the 'Now'. What I mean is, there was no past, no future, just Now. Next thing I knew, I was waiting for the elevator. Didn't remember walking down the hall to the elevators. Next, I was leaving the building. Didn't remember coming down in the elevator. Now, I started to get scared, because I had a long commute home. I worked in downtown Brooklyn, NY, and I lived out in Long Island. I had to take a subway and two railroad trains to get home. I made it to the railroad station.
 I hopped on the first train leaving, and I had to constantly tell myself to get off in Jamaica. I felt that I might end up riding the train back and forth for however long this thing lasted. I sat towards the middle of the car. A couple of people sat at the end of the car, and were talking. It sounded like they were sitting right next to me! My eyes wouldn't stay still. I tried closing them, but when I did, I got this falling sensation, like I was falling right through the seat. I tried to read a book, but I kept reading the top line over and over again! I couldn't make my eyes go down to the next line! I ended up just looking out of the window, but instead of watching the scenery go by, my eyes focused in on every bit of ballast and debris that went by! If a dime were sitting out there on the tracks, I would've spotted it!
I made it as far as Babylon, and I called my wife to come and pick me up. By now, everything seemed unreal, as if I were sitting somewhere daydreaming about all of this. My wife showed up, and I explained to her what happened. While I was explaining, it seemed to me that she was sort of giggling about it, so I kinda laughed as I spoke. When I was finished, she yelled at me, which took me by surprise because I thought she had been giggling earlier. And her face looked angry in an exaggerated way. I remember her calling me all kinds of 'stupid'. All I could do was just put my head on her shoulder as she drove, partly because the movements of the car were making me nauseous. It had been about 6 hours since I first took the nutmeg, and things were really starting to slip.
When we got home, I went straight to bed. Everything seemed so unreal. I wasn't sure if I were really home, or still riding the train and thinking about all of this. I tried to sleep, but every time I closed my eyes I would see patterns, like stripes and plaids and things. It was too distracting. I tried to look at T.V., but I couldn't seem to make out the images. I knew it was 'The Flintstones' that was on, but I couldn't make them out. All I saw was distorted colors. Amazingly, I was able to hear my neighbors eating dinner and talking. Outside of my bedroom window was a walkway, a fence, a driveway, and my neighbor's house. My window was partially open, and their side door was open. I could clearly hear their utensils hitting their plates as they ate and talked. I couldn't understand what they were saying because they spoke spanish.
At some point in the evening, I 'felt' as if the skin were melting off of the bottom half of my face. I truly believed that the bottom half of my skull was showing. When my wife walked into the room, I covered the bottom half of my face with the sheets. When she asked me why I was doing that, I told her that the skin melted off of the bottom half of my face, and I didn't want her to see me like this. She just stood there with a very concerned look on her face, and then she left the room. At some point, I got up and ate some pizza. I don't remember getting up, I just remember being in the kitchen eating the pizza. Then, I was back in bed. Don't remember getting in the bed. Later on, I remember being in the bathroom with my head in the toilet, throwing up. Don't remember getting up to go to the bathroom. Just remember being there. It had been about 11 hours since I took the nutmeg.
An amazing thing that happened while I was on the nutmeg was the memories that came flooding back into my mind. I mean old memories, from when I was a toddler. Later on, I told my mother about some of these memories, and she verified them as having really happened.
The next day, I still felt that intense buzz, although not as strong as the previous day, but strong enough to keep me home from work. Everything still had that unreal feel to it, but I just accepted it as reality. As my wife and I headed out to a store, I was fascinated by the intense colors of the trees and the sky! It was as if I had never seen these things before. I just stood there, marveling at how blue the sky looked. And when I listened to my music, it was as if I were listening for the first time. I could hear things in the music that I never noticed before. Everything seemed to have a 'deepness' to it, including me. My conversations were very philosophical and spiritual. This was the enjoyable part of my nutmeg experience. I felt really laid back, like a hippy from the 60's.
I feel that I would've enjoyed the whole experience more if I didn't have to commute while under the influence. That situation kind of put a damper on the whole thing, due to my fear of never being able to get home. But, all in all, I found it to be a fascinating experience, and I'd like to try it again, under more comfortable circumstances. Even the come-down wasn't that bad. For days afterward, my piss and my sweat smelled just like nutmeg.
For years afterward, my wife banned nutmeg from our house, and, after the ban was lifted, I found that just the smell of nutmeg made me gag. But, one day, I'm gonna give it another shot.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Calculation of pressure loss in a straight pipe for laminar or turbulent flow regime of single-phase fluid flow only considering surface roughness.
This function shall be used within the restricted limits according to the referenced literature.
dp = lambda_FRI * (L/d_hyd) * (rho/2) * velocity^2
with
| lambda_FRI | as Darcy friction factor [-], |
| L | as length of straight pipe [m], |
| d_hyd | as hydraulic diameter of straight pipe [m], |
| rho | as density of fluid [kg/m3], |
| velocity | as mean velocity [m/s]. |
The Darcy friction factor lambda_FRI for straight pipes is calculated depending on the fluid flow regime (with corresponding Reynolds number Re) and the absolute surface roughness K .
The Laminar regime is calculated for Re ≤ 2000 by the Hagen-Poiseuille law according to [Idelchik 2006, p. 77, eq. 2-3]
lambda_FRI = 64/Re
The Darcy friction factor lambda_FRI in the laminar regime is independent of the surface roughness k as long as the relative roughness k is smaller than 0.007. A greater relative roughness k than 0.007 is leading to an earlier leaving of the Hagen-Poiseuille law at some value of Reynolds number Re_lam_leave . The leaving of the laminar regime in dependence of the relative roughness k is calculated according to [Samoilenko in Idelchik 2006, p. 81, sect. 2-1-21] as:
Re_lam_leave = 754*exp(if k ≤ 0.007 then 0.93 else 0.0065/k)
The Transition regime is calculated for 2000 < Re ≤ 4000 by a cubic interpolation between the equations of the laminar and turbulent flow regime. Different cubic interpolation equations for the calculation of either pressure loss dp or mass flow rate m_flow results in a deviation of the Darcy friction factor lambda_FRI through the transition regime. This deviation can be neglected due to the uncertainty in determination of the fluid flow in the transition regime.
Turbulent regime can be calculated for a smooth surface (Blasius law) or a rough surface (Colebrook-White law):
Smooth surface (roughness = Modelica.Fluid.Dissipation.Utilities.Types.Roughness.Neglected) w.r.t. Blasius law in the turbulent regime according to [Idelchik 2006, p. 77, sec. 15]:
lambda_FRI = 0.3164*Re^(-0.25)
with
| lambda_FRI | as Darcy friction factor [-]. |
| Re | as Reynolds number [-]. |
Note that the Darcy friction factor lambda_FRI for smooth straight pipes in the turbulent regime is independent of the surface roughness K .
Rough surface (roughness = Modelica.Fluid.Dissipation.Utilities.Types.Roughness.Considered) w.r.t. Colebrook-White law in the turbulent regime according to [Miller 1984, p. 191, eq. 8.4]:
lambda_FRI = 0.25/{lg[k/(3.7*d_hyd) + 5.74/(Re)^0.9]}^2
with
| d_hyd | as hydraulic diameter [-], |
| k= K/d_hyd | as relative roughness [-], |
| K | as roughness (average height of surface asperities [m], |
| lambda_FRI | as Darcy friction factor [-], |
| Re | as Reynolds number [-]. |
The Darcy friction factor lambda_FRI in dependence of Reynolds number for different values of relative roughness k is shown in the figure below.
The pressure loss dp for the turbulent regime in dependence of the mass flow rate of water is shown in the figure below.
And the mass flow rate m_flow for the turbulent regime in dependence of the pressure loss of water is shown in the figure below.


Make the Web Fun Again
Introducing Hugo, a new idea around making website creation simple again. Hugo flexibly works with many formats and is ideal for blogs, docs, portfolios and much more. Hugo’s speed fosters creativity and makes building a website fun again.
Run Anywhere
Hugo is quite possibly the easiest to install software you’ve ever used, simply download and run. Hugo doesn’t depend on administrative privileges, databases, runtimes, interpreters or external libraries. Sites built with Hugo can be deployed on S3, GitHub Pages, Dropbox or any web host.
Fast & Powerful
Hugo is written for speed and performance. Great care has been taken to ensure that Hugo build time is as short as possible. We’re talking milliseconds to build your entire site for most setups.
Flexible
Hugo is designed to work how you do. Organize your content however you want with any URL structure. Declare your own content types. Define your own meta data in YAML, TOML or JSON. Use indexes to group your content however you want. Best of all this is all done with virtually no configuration, Hugo just works.


Aman garg, Bishakh Bhattacharya, VS Chinthu and Devendra gupta, Wireless pressure sensor node for inflatable structures
[Patent, 2018]
Aman Garg, Bishakh Bhattacharya, Anil Agarwal and Sujeet Gautum, A novel carbon dioxide sensing based guidance device for
Endotracheal Intubation [Patent, 2018]
Aman Garg, Bishakh Bhattacharya, Manish Dixit and Sanjay Gambhir, Shape memory alloy actuator device for flow
control[Patent, 2018]
Publications
Aman Garg and Bishakh Bhattacharya, Design of a flexible endotracheal tube holder device and study of its effect on cutaneous
blood flow in the skin using laser Doppler velocimetry, SPIE Smart Structures + Nondestructive Evaluation 2019
Aman garg, Bishakh Bhattacharya, Anil Agarwal and Sujeet gautum , Design and development of a Carbon dioxide sensor based
guidance device for endotracheal intubation, IEEE Journal of biomedical engineering [Submitted]
Aman garg, Bishakh Bhattacharya,VS Chinthu and Devendra Gupta, Design of Inexpensive wireless pressure sensor nodes for
inflatable structures using MEMS unit, IEEE Sensors Journal [Submitted]


--- layout: archive title: Zulip Chat Archive permalink: /stream/113488-general/topic/How.20old.20is.20.60mathlib.60.3F.html ---
Hi, I wonder how old is mathlib (as a project to formalize math in Lean)? I see that the oldest commit is from July 2017 but the second one imports a lot of content from lean/library/data
and library_dev
.
It depends on what you mean. mathlib
was originally library_dev
, which I think contained some material translated from lean 2. I don't think any lean library projects have truly started from scratch since the beginning
The library_dev project is still around at https://github.com/avigad/library_dev
Looks like the first few commits on the library_dev repo (Sep 2016) were for super
, the sat solver that never made it into mathlib for some reason.
This commit by Jeremy looks like the first commit that contains parts that are still in mathlib today
Thank you for the explanation. So, the project is very young. That's amazing how fast it came from "simple lemmas about propositional logic" to the current status.
One of the reasons it grows so fast is because some people make several PR's per week :wink:
One of the reasons that I back the project so publically is that I've seen it grow so quickly. It still amazes me that there are definitions like schemes and manifolds and Noetherian rings, standard BSc and MSc objects, which have appeared in Lean but are in essentially none of the other systems, and when I started just over two years ago it didn't even have complex numbers.
Yury, did you read the mathlib paper? It briefly discusses the history of mathlib and lots of other very interesting things.
The story is more complicated. Mathlib combined elements of library_dev
and Lean's core library. Most of those were in turn ported from Lean 2: https://github.com/leanprover/lean2/tree/master/library, which dates to about 2014. And parts of that library trace all the way back to the original Lean, Lean 0.1. When Mario took over mathlib, he rewrote a lot. But lots of stuff survives from the earlier versions: basic algebraic structures (from semigroups to ordered fields), sets, lists, finsets, nat, int, etc.
Last updated: Apr 24 2020 at 19:02 UTC


Wine application created to learn more about wine. There are quizzes to test and gain wine knowlegdge. Pairings for food and wines can be searched and added to database. A user can also save wines that they like into their own wine library.


Client Encryption API documentation
This is an encryption library created by ReCheck devs team.
We are glad to receive any feedback you want to give us.
You can find the docs website here.
Table of Contents
Overview
This is a reference implementation of a protocol for end-to-end encryption with the Recheck services platform. It implements data storage, fetching and validation with a set of keypairs that support ethereum and aeterntiy digital signatures.
Requirements
-
npm version 8.15 or above
-
You will need to download the library from the node repository.
-
npm i recheck-clientjs-library
Getting started
Exported functions :
debug: setDebugMode,
Setting the debug either true or false.
init: init
Specify API token, host and blockchain network
login: login,
Returns a token that the user need in order to communicate with the server.
loginWithChallengeParams: loginWithChallengeParams,
Returns a token that the user need in order to communicate with the server. Has a parameter challenge. When the user is using our service, upon login into the system there is going to be a QR code that you have to scan. That will create a link between the server and the GUI and you will be prompted to the GUI file manager.
newKeyPair: newKeyPair
Creates a key pairs and recovery phrase
store: store
Encrypt, upload and register a file or any data
open: open
share: share
validate: validate
prepare: prepare
decrypt: decrypt
poll: poll
select: select
selection: getSelected
prepareSelection: prepareSelection
execSelection: execSelection
Application layer
The exported functions in better detail.
Low level layer
The base functions in better detail.


FileWriterCache
Cache for file writers.
This class caches file writers, one per directory.
clear
@staticmethod clear()
Clear cached summary writers. Currently only used for unit tests.
get
@staticmethod get(logdir)
Returns the FileWriter for the specified directory.
logdir
: str, name of the directory.A FileWriter
.


2 Samuel 14:16
For the king will hear, to deliver his handmaid out of the hand of the man that would destroy me and my son together out of the inheritance of God.


Moorhead Savage
Malcolm C Foy
Rotherham Youth Enterprise
Burgess Commercial
Barnsley & Rotherham Chamber


EASI Components
code on github
npm package
<a-easi
show-text
/>
<a-easi-select />
<a-easi-ernie />
A very useful
Guide on EASI


| CS 391 - Selected Topics: Data Mining
Syllabus |
Part I: Practical Machine Learning Tools and Techniques
1. What’s it all about?
1.1 Data mining and machine learning
1.2 Simple examples: the weather problem and others
1.3 Fielded applications
1.4 Machine learning and statistics
1.5 Generalization as search
1.6 Data mining and ethics
1.7 Further reading
2. Input: Concepts, instances, attributes
2.1 What’s a concept?
2.2 What’s in an example?
2.3 What’s in an attribute?
2.4 Preparing the input
2.5 Further reading
3. Output: Knowledge representation
3.1 Decision tables
3.2 Decision trees
3.3 Classification rules
3.4 Association rules
3.5 Rules with exceptions
3.6 Rules involving relations
3.7 Trees for numeric prediction
3.8 Instance-based representation
3.9 Clusters
3.10 Further reading
4. Algorithms: The basic methods
4.1 Inferring rudimentary rules
4.2 Statistical modeling
4.3 Divide-and-conquer: constructing decision trees
4.4 Covering algorithms: constructing rules
4.5 Mining association rules
4.6 Linear models
4.7 Instance-based learning
4.8 Clustering
4.9 Further reading
5. Credibility: Evaluating what’s been learned
5.1 Training and testing
5.2 Predicting performance
5.3 Cross-validation
5.4 Other estimates
5.5 Comparing data mining schemes
5.6 Predicting probabilities
5.7 Counting the cost
5.8 Evaluating numeric prediction
5.9 The minimum description length principle
5.10 Applying MDL to clustering
5.11 Further reading
6. Implementations: Real machine learning schemes
6.1 Decision trees
6.2 Classification rules
6.3 Extending linear models
6.4 Instance-based learning
6.5 Numeric prediction
6.6 Clustering
6.7 Bayesian networks
We will also cover selected portions of Part II involving the WEKA software workbench.