What you should know about the SEO process. How to initiate, control and monitor it.
Find Out More
Technology to be used is an IT Architect decision. The identification of the correct technology is the
consequence of the knowledge of the IT Standards and Business needs.
Examples of technology decisions:
CMS vs HMLT coding
Dinamyc vs Static
PHP vs ASPX vs JS, etc
Heroku, CrownPeak, Plone, Bastion, etc
The best is to get an updated sitemap.xml with an automatic tool that replaces the existing file in order to
include also the latest pages of the site. The tool can be launched with a regular frequency (scheduled task)
or every time there is a new material to be included (manual task).
There could be many sitemap.xml files for one site (of course with different names), if it is needed a separation.
All sitemap.xml files have to be located in the site root.
This file contains the rules that Search Engines have to follow on the web pages. It is possible to exclude here a set of pages that are not relevant per the SEO perspective avoiding the crawling/indexing of those pages. This file has to be located in the site root. There should be only one robots.txt file for the entire site. Make sure there is indicated the path to the sitemap.xml file (or files if there are more)
More about this topic? or Continue?Site Map is more for Search Engines than humans. It is recommended to create a schematic sitemap that displays the real schema of the web site following the real hierarchy of the structure.
More about this topic? or Continue?Keep in mind that subdomains are considered as a totally separated domain, there won’t be any connection in terms of SEO perspective.
More about this topic? or Continue?This is an important task. Don't forget to make sure that the sitemap.xml is submitted to Google via the Google Search Console tool.
More about this topic? or Continue?
The less clicks to reach a page the best will be for customer experience and crawlers to get your pages.
1 click: The best
3 clicks: quite ok
5 clicks: useless
Make sure that all existing redirects are set as 301 codes.
Allow 302 only if it is a real temporarily solution.
Contact the System Custodian or your Dedicated BI, you'll get helped on what's next!


Negredolucy says:
Have you been locked out of your email or cannot trust your spouse about getting the price for the new purchase and the receipt for the order is in there email and you need access to email or probably need to access his/her of facebook for a cheating spouse or maybe you have bad grades in school and you don’t want to ruin your future. This is the definition of a Hacker. You need a hacker to get you through backdoor and make life easy. What do you want? “Do you want to access your locked out email, cheating spouse phone, facebook, Tap phone conversation, WhatsApp conversation” We render a brilliant service on the market. We believe in building reputation and getting a satisfied customer Contact us on WHATSAPP +1<PHONE_NUMBER> Email Authenticatehackers@gmail.com


| 004:013 Khan | : |
These are the limits (set by) Allah (or ordainments as regards laws of inheritance), and whosoever obeys Allah and His Messenger (Muhammad SAW) will be admitted to Gardens under which rivers flow (in Paradise), to abide therein, and that will be the great success. |
| 004:013 Maulana | : |
These are Allah's limits. And whoever obeys Allah and His Messenger, He will admit him to Gardens wherein flow rivers, to abide in them. And this is the great achievement. |
| 004:013 Pickthal | : |
These are the limits (imposed by) Allah. Whoso obeyeth Allah and His messenger, He will make him enter Gardens underneath which rivers flow, where such will dwell for ever. That will be the great success. |
| 004:013 Rashad | : |
These are GOD's laws. Those who obey GOD and His messenger, He will admit them into gardens with flowing streams, wherein they abide forever. This is the greatest triumph. |
| 004:013 Sarwar | : |
These are the laws of God.  This is the greatest triumph. |
| 004:013 Shakir | : |
These are Allah's limits, and whoever obeys Allah and His Messenger, He will cause him to enter gardens beneath which rivers flow, to abide in them; and this is the great achievement. |
| 004:013 Sherali | : |
These are the limits set by ALLAH; and whoso obeys ALLAH and HIS Messenger, HE will make him enter Gardens through which streams flow; Therein shall they abide; and that is a great triumph. |
| 004:013 Yusufali | : |
Those are limits set by Allah: those who obey Allah and His Messenger will be admitted to Gardens with rivers flowing beneath, to abide therein (for ever) and that will be the supreme achievement. |
Concepts/Themes Covered: الإيمان > الغيب > الجنة > أصحاب الجنة Faith> The Unseen World> The Paradise> The Companions of the Garden الإيمان > الغيب > الجنة > صفات الجنة Faith> The Unseen World> The Paradise> Characteristics of Paradise الإيمان > الغيب > الخلود > الخلود في النعيم Faith> The Unseen World> The Eternity> The Immortality in Happiness تنظيم العلاقات المالية > الميراث Organizing Financial Relationships>Inheritance تنظيم العلاقات المالية > الوصية > التحذير من الإفراط بها Organizing Financial Relationships>The Will>The Warning of going to the Extremes when Bequeathing
This tool uses eight English parallel translations for the Holy Quran imported from Mr. Clay Smith. You can also visit Qurany Concepts for browsing the Quran themes or topics. If you want to search the Holy Quran for keywords, please visit Qurany Keywords.


Evaluate Day Pro is enabled via an auto renewing subscription. For the Yearly Subscription applies the following:
- The duration of the every period of the subscription is 1 year.
- The price of the subscription is shown in the Evaluate Day`s Purchase Pane updated to the time of the purchase.
- Payment will e charrged to iTunes Account at confirmation of purchase of the end of the Free Trial Period, if any.
- The lenght of the free Trial Period, if any, is shown in the Evaluate Day`s Purchase Pane updated to the time of the purchase.
- Subscription automatically renewsunless auto-renew is turned off at least 24-hours efore the end of the current period.
- Account will be charged for renewal within 24-hours prior to the end of current period, with the same amount as the first period.
- Subscriptions may ne managed by the user and auto-renewal may be turned off by going to the user`s Account Settings after purchase.


MLSA Event [18/09/2021]
1. Introduction to MLSA and other student programs [Before Lunch]
2. Hands-on and deep dive session on Git, GitHub and CI/CD [After Lunch]
Event Feedback Form
Join Telegram Channel
Event Resources
Join DSEU HackClub
Join AngelHack Core Team
Contact Me
HackClub Brochure
Our amazing team!
Anshuman Fauzdar
[Host]
Akshay Goyal
[Event Manager]
Sunny Vedwal
[Technical Lead]
Vinay Dhiman
[Public Relations]
Vinayak Verma
[Technical Reviewer]
Prateek Jindal
[Finance Manager]
Ish Kapoor
[Event Handling]
Ish Kapoor
[Event Handling]
Exciting Benefits!
Stickers
Cheat Sheet
Venue
Certificate
Powered by
MLSA
,
HackClub
and
DSEU
[For direct query use contact-me button on the right]


Disclaimer: Don't click on the caprese salad picture unless you want to download and watch it in action
Click here to look up Toby on the InterwebsToby Flenderson is the human resources representative for the Scranton branch of paper distributor Dunder Mifflin/Sabre.
Mild-mannered to the point of being physically incapable to voice his opinions or assert himself, Toby can be somewhat mournful about his life choices (he fell into the field of Human Resources after leaving his training at seminary in order to pursue the woman he'd later marry and painfully divorce).


--- layout: page title: About header-img: "img/about-bg.png" ---
A 24 year old girl who took a big leap into a new direction and hopes that all the hard work will create a great outcome.


Enumeration members
Ashenvale
Ashenvale: = "A"
Black Citadel
Black Citadel: = "K"
Cityscape
Cityscape: = "Y"
Dalaran Ruins
Dalaran Ruins: = "J"
Lordaeron Fall
Lordaeron Fall: = "F"
Lordaeron Summer
Lordaeron Summer: = "L"
Lordaeron Winter
Lordaeron Winter: = "W"
Northrend
Northrend: = "N"
Sunken Ruins
Sunken Ruins: = "Z"
Underground
Underground: = "G"
Village Fall
Village Fall: = "Q"
Tileset is the main-type one of the tilesets.


RXG-1-give sub-ID counter is zero (0). The quantity will always be 1.
This quantity/timing field may differ from the ORC quantity/timing field, which
contains the requested quantity/timing of the original order.
Note: The contents of fields 3-8 should be identical to the comparable
fields in the RXE (RXE-2 thru 5).
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 is the identifier of the medical substance/treatment
ordered to be given to the patient; it is equivalent to OBR-4-Universal
service ID in function. See the RXE segment for a complete definition of
the RXE-2-Give code. If the substance given is a vaccine, CVX codes may
be used to code this field (see HL7 table 0292 - Vaccines administered).
Definition:
This field contains the ordered amount as encoded by the pharmacy/treatment
supplier. In a variable dose order, this is the minimum ordered amount. In a
nonvarying dose order, this is the exact amount of the order.
Note: This field is not a duplication of the first component of the
quantity/timing field, since in non-pharmacy/treatment orders, that component
can be used to specify multiples of an ordered amount.
Another way to
say this is that, for pharmacy/treatment orders, the quantity component of the
quantity/timing field refers to what is to be given out at each service
interval; and thus, in terms of the RX order, that first component always
defaults to 1. Hence, in the actual execution of the order, the value of 1 in
the first component of the quantity/timing field always refers to one
administration of the amount specified in this field (the requested Give Amount
field).
Definition: In a variable dose order, this is the maximum ordered amount. In a nonvarying dose order, this field is not used.
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 units for the give amount.
Note: These units can be a "compound quantity;" i.e., the units may
contain the word "per." For example, micrograms per KG (micg/kg) is an
acceptable value, which means that the units are micrograms per KG (of body
weight).
A table of standard units that contains compound units is needed. Until such a
table is agreed on, a user-defined table is needed for each site.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: The dosage form indicates the manner in which the
medication/treatment is aggregated for dispensing, e.g., tablets, capsules,
suppositories. In some cases, this information is implied by the give code
in RXG-4-give code. Use this field when the give code does not specify
the dosage form.
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 notes to the person administering the
medication/treatment (may include the ordering provider's original notes, as
well as any notes from the formulary or the pharmacy or treatment supplier).
If coded, a user-defined table must be used. If free text, place a null in the
first component and the text in the second, e.g., |^this is a free text
administration note|.
Definition:
Refer to HL7 Table 0167 - Substitution status for valid values.
Note: The next two fields are equivalent to the corresponding fields of
the RXE segment. They are included (optionally) in the RXG so that it may
"stand alone" as a "give" instruction segment.
 The default (null)
value is the current census location for the patient. Site-specific table.
The first eight components have the same form as the first eight components of
PV1-3-assigned patient location. The final eight components replace the
ninth component of PV1-3-assigned patient location and represent the
full address specification.
Definition:
Refer to HL7 table 0136 - Yes/no indicator for valid values.
The values have the following meaning for this field:
Y Yes - Indicates that a warning is present. The application receiving the
dispense order needs to warn the person dispensing/administering the drug or
treatment to pay attention to the text in
RXG-13-pharmacy/treatment supplier's special administration
instructions.
N No - Indicates no warning is present. This is the equivalent default (null)
value.
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 pharmacy/treatment supplier-generated special
instructions to the provider administering the order.
Definition:
This field contains the time unit to use to calculate the rate at which the
pharmaceutical/treatment is to be administered.
Format:
S<integer> |
= |
<integer> seconds |
M<integer> |
= |
<integer> minutes |
H<integer> |
= |
<integer> hours |
D<integer> |
= |
<integer> days |
W<integer> |
= |
<integer> weeks |
L<integer> |
= |
<integer> months |
T<integer> |
= |
at the interval and amount stated until a total of <integer> "DOSAGE" is accumulated. Units would be assumed to be the same as in the QUANTITY field. |
INDEF |
= |
do indefinitely - also the default |
This
is the same as the format specified for the DURATION component of the
quantity/timing field, excluding the "X" specification.
Required when relevant (e.g., certain IVs). For example, if the "give
amount/units" were 300 ml and the "give per" time unit were H1 (equivalent to
one hour), the rate is 300ml/hr.
Definition: This field contains the amount (number) of substance/treatment to be administered.
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 units for RXG-15-give rate amount.
May be composite. The ratio of the RXG-15-give rate amount and
RXG-16-give rate units fields define the actual rate of administration.
Thus, if RXG-15-give rate amount = 100 and RXG-16-give rate units
= ml/hr, the requested rate of administration is 100 ml/hr.
Definition: Use when RXG-4-Give code does not specify the strength. This is the numeric part of the strength, used in combination with RXG-18-Give strength units.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: Use when RXG-4-Give code does not specify the strength.
This is the unit of the strength, used in combination with RXG-17-Give
strength.
Note: These units can be a "compound quantity"; i.e., the units may
express a quantity per unit of time. For example, micrograms per hour (ug/h)
is an acceptable value. These compound units are contained in the ISO+ table.
See Chapter 7 for full definition of ISO+ units.
Definition:
This field contains the lot number of the medical substance administered.
Note: The lot number is the number printed on the label attached to the
container holding the substance and on the packaging which houses the
container. If the substance is a vaccine, for example, and a diluent is
required, a lot number may appear on the vial containing the diluent; however,
any such identifier associated with a diluent is not the identifier of
interest. The substance lot number should be reported, not that of the diluent.
Definition:
This field contains the expiration date of the medical substance
administered.
Note: Vaccine expiration date does not always have a "day" component;
therefore, such a date may be transmitted as YYYYMM.
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 manufacturer of the medical substance
administered.
Note: For vaccines, code system MVX may be used to code this field (see
Section 4.17.1, "Vaccine administration data"). This field may be used if the
manufacturer of the substance is not identified by the code used
in RXA-5-administered code.
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 identifier of the condition or problem for
which the drug/treatment was prescribed. May repeat if multiple indications
are relevant.
The
ORC must have the filler order number and the order control code RE. As a
site-specific variant, the RXO and associated RXCs and/or the RXE (and
associated RXCs) may be present if the receiving application needs any of their
data. The RXA carries the administration data.
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM # |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
4 |
NM |
R |
00342 |
Give Sub-ID Counter |
||
2 |
4 |
NM |
R |
00344 |
Administration Sub-ID Counter |
||
3 |
26 |
TS |
R |
00345 |
Date/Time Start of Administration |
||
4 |
26 |
TS |
R |
00346 |
Date/Time End of Administration |
||
5 |
250 |
CE |
R |
0292 |
00347 |
Administered Code |
|
6 |
20 |
NM |
R |
00348 |
Administered Amount |
||
7 |
250 |
CE |
C |
00349 |
Administered Units |
||
8 |
250 |
CE |
O |
00350 |
Administered Dosage Form |
||
9 |
250 |
CE |
O |
Y |
00351 |
Administration Notes |
|
10 |
250 |
XCN |
O |
Y |
00352 |
Administering Provider |
|
11 |
200 |
CM |
C |
00353 |
Administered-at Location |
||
12 |
20 |
ST |
C |
00354 |
Administered Per (Time Unit) |
||
13 |
20 |
NM |
O |
01134 |
Administered Strength |
||
14 |
250 |
CE |
O |
01135 |
Administered Strength Units |
||
15 |
20 |
ST |
O |
Y |
01129 |
Substance Lot Number |
|
16 |
26 |
TS |
O |
Y |
01130 |
Substance Expiration Date |
|
17 |
250 |
CE |
O |
Y |
0227 |
01131 |
Substance Manufacturer Name |
18 |
250 |
CE |
O |
Y |
01136 |
Substance/Treatment Refusal Reason |
|
19 |
250 |
CE |
O |
Y |
01123 |
Indication |
|
20 |
2 |
ID |
O |
0322 |
01223 |
Completion Status |
|
21 |
2 |
ID |
O |
0323 |
01224 |
Action Code-RXA |
|
22 |
26 |
TS |
O |
01225 |
System Entry Date/Time |
Definition: Use this field if matching this RXA segment to its corresponding RXG segment. If the two applications are not matching RXG and RXA segments, this field's value is zero (0).
Definition:
This field starts with 1 the first time that medication/treatment is
administered for this order. Increments by one with each additional
administration the medication/treatment.
Note: More than one RXA segment can be "matched" to a single RXG
segment, as is the case when recording a change of the rate of administration
of an IV solution.
Definition: If the order is for a continuous administration (such as an IV), and the rate is changed at a certain time after the start, an RAS message can be issued to record the change. For such an RAS message, this field records the time the rate was changed to the new value recorded in the RXA-12-administered per (time unit) of the same message.
Definition: If null, the date/time of RXA-3-date/time start of administration is assumed.
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 identifier of the medical
substance/treatment administered. It is equivalent to OBR-4-universal
service ID in function. If the substance administered is a vaccine, CVX
codes may be used to code this field (see HL7 Table 0292 - Vaccines
administered).
Definition: This field contains the amount administered.
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 is conditional because it is required if the
administered amount code does not imply units. This field must be in simple
units that reflect the actual quantity of the substance administered. It does
not include compound units.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: The dosage form indicates the manner in which the
medication/treatment is aggregated for dispensing, e.g., tablets, capsules,
suppositories. In some cases, this information is implied by the dispense/give
code in RXA-5-Administered code. Use this field when the administered
code does not specify the dosage form.
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 notes from the provider administering the
medication/treatment. If coded, requires a user-defined table. If free text
(describing a custom IV, mixture, or salve, for example) place a null in the
first component and the text in the second, e.g., |^this is a free text
administration note|.
Components:
In Version 2.3 and later, use instead of the CN data type. <ID number
(ST)> ^ <family name (FN)> ^ <given name (ST)> ^ <second or
further given names or initials thereof (ST)> ^ <suffix (e.g., JR or III)
(ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (IS)> ^
<source table (IS)> ^ <assigning authority (HD)> ^ <name type
code (ID)> ^ <identifier check digit (ST)> ^ <code identifying the
check digit scheme employed (ID)> ^ <identifier type code (IS)> ^
<assigning facility (HD)> ^ <name representation code (ID)> ^
<name context (CE)> ^ <name validity range (DR)> ^ < name
assembly order (ID)>
Subcomponents of assigning authority: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)
Subcomponents of assigning facility: <namespace ID (IS)> &
<universal ID (ST)> & <universal ID type (ID)
Definition: This field contains the provider ID of the person administering
the pharmaceutical/treatment.
 The default
(null) value is the current census location for the patient. Site-specific
table. The first eight components have the same form as the first eight
components of PV1-3-assigned patient location. The final eight
components replace the ninth component of PV1-3-assigned patient location
and represent the full address specification.
Definition: This field contains the rate at which this medication/treatment was administered as calculated by using RXA-6-administered amount and RXA-7-administered units. This field is conditional because it is required when a treatment is administered continuously at a prescribed rate, e.g., certain IV solutions.
Definition: Use when RXA-5-Administered code does not specify the strength. This is the numeric part of the strength, used in combination with RXA-14-Administered strength units.
Components:
<identifier (ST)> ^ <text (ST)> ^ <name of coding system
(IS)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^
<name of alternate coding system (IS)>
Definition: Use when RXA-5-Administered code does not specify the
strength. This is the unit of the strength, used in combination with
RXA-13-Administered strength.
Note: These units can be a "compound quantity;" i.e., the units may
express a quantity per unit of time. For example, micrograms per hour (ug/h)
is an acceptable value. These compound units are contained in the ISO+ table.
See Chapter 7 for full definition of ISO+ units.
Definition:
This field contains the lot number of the medical substance administered.
Note: The lot number is the number printed on the label attached to the
container holding the substance and on the packaging which houses the
container. If the substance is a vaccine, for example, and a diluent is
required, a lot number may appear on the vial containing the diluent; however,
any such identifier associated with a diluent is not the identifier of
interest. The substance lot number should be reported, not that of the diluent.
Definition:
This field contains the expiration date of the medical substance
administered.
Note: Vaccine expiration date does not always have a "day" component;
therefore, such a date may be transmitted as YYYYMM.
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 manufacturer of the medical substance
administered.
Note: For vaccines, code system MVX may be used to code this field).
See Section 4.17.1. This field may be used if the manufacturer of the substance
is not identified by the code used in RXA-5- administered code.
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 reason the patient refused the medical
substance/treatment. Any entry in the field indicates that the patient did not
take the substance.
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 identifier of the condition or problem for
which the drug/treatment was prescribed. May repeat if multiple indications
are relevant.
Value |
Description |
CP |
Complete |
RE |
Refused |
NA |
Not Administered |
PA |
Partially Administered |
Definition:
Status of record. The information in this field enables the use of the RXA in
the vaccine messages (see Section 4.18, "Vaccine Segments"), where a method of
correcting vaccination information transmitted with incorrect patient
identifying information is needed. Refer to HL7 Table 0323 - Action
code for valid values.
Value |
Description |
A |
Add |
D |
Delete |
U |
Update |
Definition: Date/time the administration information was entered into the source system. This field is used to detect instances where treatment administration information is inadvertently entered multiple times by providing a unique identification field. Under usual circumstances, this field would be provided automatically by the computer system rather than being entered by a person.
The purpose of this section is to show how certain specific situations would be handled using the pharmacy/treatment protocol. The ellipses represent uncompleted details. The symbol // precedes comments for clarification.
The
order give 500 mg Ampicillin P.O. Q6H for 10 days for a total of 40
tablets is sent to the RX application from the OE application. This order
can be coded with various levels of precision by an ordering application:
a) E-mail only version (uses only free text, RXO-6-provider's
pharmacy/treatment instructions or RXO-7-provider's administration
instructions only); fully encoded version must be re-entered or verified
manually by the pharmacy or treatment application.
b) With RXO-2-requested give amount-minimum, RXO-4-requested give
units, and ORC-7-quantity/timing coded, and RXO-1-requested give
code as free text.
c) With RXO-1-requested give code, RXO-2-requested give
amount-minimum, RXO-4-requested give units, and
ORC-7-quantity/timing coded, but where RXO-1-requested give code
does not include units.
d) With RXO-1-requested give code, RXO-2-requested give
amount-minimum, RXO-4-requested give units, and ORC-7-quantity/timing
coded, and where RXO-1-requested give code does include
units.
In this case, the units are optional. The rule for this case (on orders,
dispense results, give results, and administration results) is as follows: if
units are coded, they override or supersede the units value implied by the give
code.
a) The E-mail only version of the order: no coded fields exist in the RXO.
MSH|^&~\|Pharm|GenHosp|CIS|GenHosp|1998052911150700||OMP^O09|...<cr>
PID|...<cr>
ORC|NW|1000^OE||||E|...<cr>
RXO||||||500 mg Polycillin Q6H for 10 days, dispense 40
Tablets|...<cr>
b) A partially coded version of the order. This version has the
RXO-2-requested give amount-minimum, RXO-4-requested give units,
and ORC-7-quantity/timing coded, but the RXO-1-requested give
code as free text.
MSH|^&~\|Pharm|GenHosp|CIS|GenHosp|1998052911150700||OMP^O09|...<cr>
PID|...<cr>
ORC|NW|1000^OE||||E|^Q6H^D10^^^R|...<cr>
RXO|^Polycillin 500 mg TAB^|500||MG|||||Y||40|...<cr>
RXR|PO|...<cr>
c) A more completely coded version of the order, with the RXO-1-requested
give code, RXO-2-requested give amount-minimum, RXO-4-requested
give units, and ORC-7-quantity/timing coded, but where
RXO-1-requested give code does not imply units.
MSH|^&~\|Pharm|GenHosp|CIS|GenHosp|1998052911150700||OMP^O09|...<cr>
PID|...<cr>
ORC|NW|1000^OE||||E|^Q6H^D10^^^R|...<cr>
RXO|RX1001^Polycillin^L|500||MG|||||Y||40|...<cr>
RXR|PO|...<cr>
d) A completely encoded version, with the RXO-1-requested give code,
RXO-2-requested give amount-minimum, RXO-4-requested give units,
and ORC-7-quantity/timing coded, and where RXO-1-requested give
code does imply units.
MSH|^&~\|Pharm|GenHosp|CIS|GenHosp|1998052911150700||OMP^O09|...<cr>
PID|...<cr>
ORC|NW|1000^OE||||E|^Q6H^D10^^^R|...<cr>
RXO|RX1001^Polycillin 500 mg TAB^L|500||MG|||||G||40|...<cr>
RXR|PO|...<cr>
e) Pharmacy or treatment supplier's encoded version (RDE message) sent to
nursing application (a generic substitution).
MSH|^&~\|Pharm|GenHosp|CIS|GenHosp|1998052911150700||RDE^O11|...<cr>
PID|...<cr>
ORC|RE|1000^OE|9999999^RX|||E|^Q6H^D10^^^R|...<cr>
RXE|^^^199012100600^^R|0047-0402-30^Ampicillin 250 MG
TAB^NDC|2||TAB|||||G|80||||123456|rx#1001|...<cr>
RXR|PO|...<cr>
f) Pharmacy or treatment supplier's dispense results (RDS message).
MSH|...<cr>
PID|...<cr>
ORC|RE|1000^OE|9999999^RX|||E|^Q6H^D10^^^R|...<cr>
RXD|1|0047-0402-30^Ampicillin 250 MG TAB^NDC|199012100400|8|TAB||RX#1001|||
123456|G|8|...<cr>
g) Pharmacy or treatment supplier's give results (RGV message).
MSH|^&~\|Pharm|GenHosp|CIS|GenHosp|1998052911150700||RGV^O15|...<cr>
PID|...<cr>
ORC|RE|1000^OE|9999999^RX|||E|^Q6H^D10^^^R|...<cr>
RXG|1|1|^^199012100600^^R|0047-0402-30^Ampicillin 250 MG
TAB^NDC|500||MG|||G|...<cr>
RXR|PO|...<cr>
h) Nursing application Medications Administration results to pharmacy,
treatment, or Order Entry application.
MSH|^&~\|Pharm|GenHosp|CIS|GenHosp|1998052911150700||RAS^O17|...<cr>
PID|...<cr>
ORC|RE|1000^OE|9999999^RX|||E|^Q6H^D10^^^R|...<cr>
RXA|1|1|199012100615||0047-0402-30^Ampicillin 250 MG
TAB^NDC|2|TAB|...<cr>
RXR|PO|...<cr>
a)
RXO-1 Requested Give code example
RXO|58160040000110^Fluoxetine HCL 10mg Capsule^GPI^00777310402^Prozac 10 mg
caps^NDC|...<cr>
b) RXO-18 and RXO-19 Requested Strength and Strength Unit examples
The need for strength and strength unit fields in addition to the amount and
amount units fields included in various RX_ segments requires explanation.
Physicians can write a prescription for a drug such as Ampicillin in two ways.
One way would be: "Ampicillin 250 mg capsules, 2 capsules four times a day."
In this case the give amount would be 2, the give units would be capsules, the
strength would be 250 and the strength units would milligrams.
ORC|||||||1^QID|...<cr>
RXO|01200020200105^Ampicillin 250 mg capsule^GPI^00047040230^Ampicillin 250 mg
caps^NDC|2||caps^capsule^FDB||||||||||||||250|mg|...<cr>
However, the provider could also write the prescription as "Ampicillin 500 mg
four times a day." In this case the give amount would be 500 and the give
units would be milligrams. The strength would not be reported in the RXO
segment because it is not specified; the drug could be given in two 250 mg caps
or one 500 mg cap. But the pharmacist would dispense a specific capsule size
and would record the strength in the RXE segment as 250 or 500, depending upon
which pill size was dispensed.
ORC|||||||1^QID|...<cr>
RXO|012000202001^Ampicillin capsule^GPI |500||mg^milligram^ISO||...<cr>
a)
RXD-4 and RXD-5 Dispense amount and Actual dispense units
The RXD-4 and RXD-5 together might say
100 tabs:
RXD||||100|TAB^tablet^FDB|...<cr>
Or, 100 each
RXD||||100|EA^each^FDB|...<cr>
Or, perhaps a volume, 3 liters
RXD||||3|L^liter^ISO|...<cr>
b) Actual dispense amount, Actual dispense units, Actual strength, Actual
strength units
For example, the RXD-4 , RXD-5, RXD-16 and RXD-17 together might say
100 tabs of 240 mg strength:
RXD||||100|tab^tablet^FDB|||||||||||240|mg|...<cr>
Or, 100 each of 60 units per cc
RXD||||100|EA||||||||||||60|iu/ml^^ISO+|...<cr>
Or, perhaps a volume, 3 liters with 60 grams per liter
RXD||||3|L^liter^ISO|||||||||||60|g/L^^ISO+|...<cr>
c) Valuing the Dispense Package Size Unit
If the package given to the patient is 2, 4 ounce bottles with a strength of
100/5ml, but the cough suppressant is stocked in 1 gallon bottles, then the
field contains 1 gallon.
RXD||||8|ounce^^ISO|||||||||||20|mg/ml|||||1|gal^gallon^ISO|...<cr>
If one were to dispense Mevacor 100 tablets with a strength of 20 mg/tablet,
and the package from the manufacturer is a 60 tablet package, then the fields
reflect 60 tablets (the size of the package stocked by the pharmacy).
RXD||||100|tab^^FDB|||||||||||20|mg|||||60|tab|...<cr>
Example:
Adam Everyman appears in the Pharmacy with a prescription for Veramil 120 mgm
B.I.D. The prescription is filled and the $5 co-pay is collected. The
following RDS message is generated:
MSH|^&~\|PIMS|GenHosp|IE||1998052911150700||RDS^O13^RDS_O13||...<cr>
PID|||555444222111^^^MPI&GenHosp&L^MR||Everyman^Adam||19600614|M||C|99
Oakland #
106^^Pasadena^CA^91131||^^^^^626^5641111|^^^^^626^5647654|||||343132266|||N|...<cr>
ORC|RE||89968665||||||1998052910300700|||77^Hippocrates^Harold^H^III^DR^MD||^^^^^510^
2673600|...<cr>
RXE|1^BID^^19980529|^Verapamil|120||mg^milligram^FDB.MDDB||...<cr>
RXD|1|00378112001^Verapamil Hydrochloride 120 mg TAB^NDC
|199805291115-0700|100|||1331665|3|...<cr>
RXR|PO|...<cr>
FT1|1|||199805291115-0700||CO^Co-Pay^HL70017 |00378112001^Verapamil
Hydrochloride 120 mg TAB^NDC |||1|5&USD^TP|...<cr>
FT1|2|||199805291115-0700||PY^Payment^HL70017 |00378112001^Verapamil
Hydrochloride 120 mg TAB^NDC |||1|5&USD|...<cr>
HL7
Delimiters: <cr> = segment terminator; | = field separator; ^ =
component separator; & = subcomponent separator; ~ = repetition
indicator; \ = escape character
Encoding Note: For readability, these examples do not show encoding of the
subcomponents of the Give Codes (CE data type) in the RXC and RXO segments. In
practice, the subcomponents should be encoded as described in the HL7
specification.
a) Example #1
D5/0.45NaCl 1000mL with 20mEq KCl in every 3rd bottle. Start the KCl in the
3rd bottle of this order. Run in at a rate of 100mL/hr.
(Other message data: placer order #123, placer application ID=SMS,
interval=continuous, start date/time=11/28/94 0900, no stop date/time,
priority=Routine, order sequencing=Cyclical)
This order may be expressed using a parent/child relationship. The parent
order consists of an ORC (and a RXO, incompletely elaborated in this example)
that contains order level information. The repeating bottle cycle of
D5/0.45NaCl 1000mL followed by D5/0.45NaCl 1000mL followed by D5/0.45NaCl +
20mEq KCL 1000mL is represented by three child segments. The placer system may
be treating this as a single order with two bottles, A (D5/0.45NaCl 1000mL @
100mL/hr) and B (D5/0.45NaCl + 20mEq KCL 1000mL @ 100mL/hr), repeating in the
cycle of A-A-B.
The parent:
ORC|NW|123^SMS|||||1^C^^199411280900^^R^^^^C|...<cr>
RXO|Cyclic IV|...<cr>
The first child:
ORC|CH|123A1^SMS|||||1^C^^^^^^^^C&123B&SMS&&&*ES+0M|123|...<cr>
RXO Segment, Requested Give Amount-Minimum: ...|100||ML|...
Requested Give Per (Time Unit): ...|H1|...<cr>
RXR|IV|...<cr>
RXC|B|D5/.45NACL|1000|ML|...<cr>
The second child:
ORC|CH|123A2^SMS|||||1^C^^^^^^^^C&123A1&SMS&&&ES+0M|123|...<cr>
RXO Segment, Requested Give Amount-Minimum: ...|100||ML|...
Requested Give Per (Time Unit): ...|H1|...<cr>
RXR|IV|...<cr>
RXC|B|D5/.45NACL|1000|ML|...<cr>
The third child:
ORC|CH|123B^SMS|||||1^C^^^^^^^^C&123A2&SMS&&&#ES+0M|123|...<cr>
RXO Segment, Requested Give Amount-Minimum: ...|100||ML|...
Requested Give Per (Time Unit): ...|H1|...<cr>
RXR|IV|...<cr>
RXC|B|D5/.45NACL|1000|ML|...<cr>
RXC|A|KCL|20|MEQ|...<cr>
Discussion points:
Placer Order Number - Three alternatives must be discussed for placer order
number.
1. Each child could have its own placer order number.
2. Each child could have the order number of the parent plus some appended
identifier (for examples, 123A or 123.A or 123.1 etc.) that labels each child
or each unique combination of ingredients.
3. In addition to the appended identifier discussed in `B' above, a further
suffix could be attached to uniquely identify each repetition of a particular
member of the sequence. The example (a cycle of bottles `A' and `B' in the
sequence A-A-B) identified the order numbers of the children as 123A1, 123A2,
and 123B, thereby enabling the quantity/timing to be completely unambiguous.
This could be expressed many other ways, such as 123A.1 or 123.A.1 or 123.A#1
etc. HL7 does not specify a format for the expression of order number
suffixes, nor does it specify a delimiter to use for such a purpose.
Sequence Condition Value - In this example, the first child contains an
asterisk (*) as the first character of the Sequence Condition Value and the
third (last) child contains a pound sign (#).
The asterisk and pound sign are important for designating the first and last
bottles especially when children are sent in separate messages, although this
example is not constructed that way.
Note that computing the duration of the bottle is dependent upon the presence
of all of the following fields:
* RXO-2-requested give amount-minimum
* RXO-4-requested give units
* RXC-3-component amount
* RXC-4-component units
For cyclic IV orders, these fields are all required in order to determine how
long each occurrence of a child will last.
While HL7 allows either sending the parent and children in one message or
sending the parent and children in separate messages, it appears simpler and
therefore recommended to have the parent and all children included in a single
message. The example is constructed that way.
b) Example #2
D5W + 40mEq KCl 1000mL alternating with D5/LR + 20mEq KCl 1000mL at 125mL/hr
(Other message data: placer order #124, placer application ID=SMS,
interval=continuous, start date/time=11/28/94 0900, no stop date/time,
priority=Routine, order sequencing=Cyclical)
This example is a variation on the first example where two different base
solutions are used. In this example, the placer system deals with this as one
order with two alternating bottles, A (D5W + 40mEq KCl 1000mL @ 125mL/hr) and B
(D5/LR + 20mEq KCl 1000mL @ 125mL/hr) in the cycle A-B. The principles
discussed in Example #1 apply equally to this example.
The parent:
ORC|NW|124^SMS|||||1^C^^199411280900^^R^^^^C|...<cr>
RXO|Cyclic IV|...<cr>
The first child:
ORC|CH|124A^SMS|||||1^C^^^^^^^^C&124B&SMS&&&*ES+0M|124|...<cr>
RXO Segment, Requested Give Amount-Minimum: ...|125||ML|...
Requested Give Per (Time Unit): ...|H1|...<cr>
RXR|IV|...<cr>
RXC|B|D5W|1000|ML|...<cr>
RXC|A|KCL|40|MEQ|...<cr>
The second child:
ORC|CH|124B^SMS|||||1^C^^^^^^^^C&124A&SMS&&&#ES+0M|124|...<cr>
RXO Segment, Requested Give Amount-Minimum: ...|125||ML|...
Requested Give Per (Time Unit): ...|H1|...<cr>
RXR|IV|...<cr>
RXC|B|D5/LR|1000|ML|...<cr>
RXC|A|KCL|20|MEQ|...<cr>
c) Example #3
D5/0.45NaCl 1000mL with 20mEq KCl in every 3rd bottle. Start the KCl in the
3rd bottle of this order. Add 10mL of multi-vitamins to the one bag daily.
Run in at a rate of 100mL/hr.
(Other message data: placer order #134, placer application ID=SMS,
interval=continuous, start date/time=11/28/94 0900, no stop date/time,
priority=Routine, order sequencing=Cyclical. Note that the encoding of the
multi-vitamins statement in the above order, adding multi-vitamins to one IV
bag each day, may vary by institution to put it into the first or last bottle
of the day.)
This order may be expressed using a parent/child relationship. The parent
order consists of an ORC (and a RXO, although I did not completely elaborate
one in this example) that contains order level information. The repeating
bottle cycle of D5/0.45NaCl 1000mL followed by D5/0.45NaCl 1000mL followed by
D5/0.45NaCl + 20mEq KCL 1000mL is represented by three child segments. This
order is complicated by the request to add one component into any one of the
three repeating bottles, depending upon which of the bottles will occur first
on any particular day. Further complicating this order is a rate of infusion
(10 hours for a 1000mL bottle) which results in a fractional number of daily
administrations. Most legacy systems have a great deal of trouble
accommodating orders like this within their existing database structures;
however there a few vendors who now are able to handle the situation. The
placer system may be treating this as a single order with two bottles, A
(D5/0.45NaCl 1000mL @ 100mL/hr) and B (D5/0.45NaCl + 20mEq KCL 1000mL @
100mL/hr), repeating in the cycle of A-A-B with a cyclical component
(multi-vitamins).
The parent:
ORC|NW|134^SMS|||||1^C^^199411280900^^R^^^^C|...<cr>
RXO|Cyclic IV|...<cr>
The first child:
ORC|CH|134A1^SMS|||||1^C^^^^^^^^C&134B&SMS&&&*ES+0M|134|...<cr>
RXO Segment, Requested Give Amount-Minimum: ...|100||ML|...
Requested Give Per (Time Unit): ...|H1|...<cr>
RXR|IV|...<cr>
RXC|B|D5/.45NACL|1000|ML|...<cr>
The second child:
ORC|CH|134A2^SMS|||||1^C^^^^^^^^C&134A1&SMS&&&ES+0M|134|...<cr>
RXO Segment, Requested Give Amount-Minimum: ...|100||ML|...
Requested Give Per (Time Unit): ...|H1|...<cr>
RXR|IV|...<cr>
RXC|B|D5/.45NACL|1000|ML|...<cr>
The third child:
ORC|CH|134B^SMS|||||1^C^^^^^^^^C&134A2&SMS&&&#ES+0M|134|...<cr>
RXO Segment, Requested Give Amount-Minimum: ...|100||ML|...
Requested Give Per (Time Unit): ...|H1|...<cr>
RXR|IV|...<cr>
RXC|B|D5/.45NACL|1000|ML|...<cr>
RXC|A|KCL|20|MEQ|...<cr>
The fourth child:
ORC|CH|134X^SMS|||||1^Q1D^^^^^^^^|134|...<cr>
RXO|MULTIVITAMINS|10||ML|INJECTABLE|...<cr>
Discussion points:
This method for accommodating the Multi-vitamins Daily scenario does not
pretend to be the best or only way to express the message, but simply
demonstrates adapting the current specification to a highly complex order
without adding new components.
The Multi-vitamins component may be sent as a fourth child.
In this example, its ORC-7-quantity/timing includes an interval of "Q1D"
(every 1 days).
Its order number consists of the placer's parent order number plus an appended
identifier (`X' in the above example) that labels this child as a special case.
This convention would need to be agreed upon by sending and receiving
applications.
d) Example #4
D5W + 40mEq KCl 1000mL alternating with D5/LR + 20mEq KCl 1000mL alternating
with D5/0.45NaCl 1000mL. Infuse the D5W and D5/0.45 at 125mL/hr, and the D5/LR
at 100mL/hr.
(Other message data: placer order #177, placer application ID=SMS,
interval=continuous, start date/time=11/28/94 0900, no stop date/time,
priority=Routine, order sequencing=Cyclical)
This example is another variation of Example 1 where the rate for each bottle
is different, and this can be expressed within the RX segments of the children
using current components. In this example, the placer system deals with this
as one order with three alternating bottles, A (D5W + 40mEq KCl 1000mL @
125mL/hr) , B (D5/LR + 20mEq KCl 1000mL @ 100mL/hr) , and C (D5/0.45NaCl 1000mL
@ 125mL/hr) in the cycle A-B-C. The principles discussed in Example #1 apply
equally to this example.
The parent:
ORC|NW|177^SMS|||||1^C^^199411280900^^R^^^^C|...<cr>
RXO|Cyclic IV|...<cr>
The first child:
ORC|CH|177A^SMS|||||1^C^^^^^^^^C&177C&SMS&&&*ES+0M|177|...<cr>
RXO Segment, Requested Give Amount-Minimum: ...|125||ML|...
Requested Give Per (Time Unit): ...|H1|...<cr>
RXR|IV|...<cr>
RXC|B|D5W|1000|ML|...<cr>
RXC|A|KCL|40|MEQ|...<cr>
The second child:
ORC|CH|177B^SMS|||||1^C^^^^^^^^C&177A&SMS&&&ES+0M|177|...<cr>
RXO Segment, Requested Give Amount-Minimum: ...|100||ML|...
Requested Give Per (Time Unit): ...|H1|...<cr>
RXR|IV|...<cr>
RXC|B|D5/LR|1000|ML|...<cr>
RXC|A|KCL|20|MEQ|...<cr>
The third child:
ORC|CH|177C^SMS|||||1^C^^^^^^^^C&177B&SMS&&&#ES+0M|177|...<cr>
RXO Segment, Requested Give Amount-Minimum: ...|125||ML|...
Requested Give Per (Time Unit): ...|H1|...<cr>
RXR|IV|...<cr>
RXC|B|D5/0.45NACL|1000|ML|...<cr>
With
appropriate definitions in the QRD and/or QRF segments, the RDE, RDS, RGV, and
RAS messages can serve as models for result-oriented pharmacy/treatment queries
returning the current profile of pharmacy or treatment orders (RDE type), the
current dispense history (RDS type), the current dose history (RGV type), or
the current administration record (RAS type)..."
The order entry application requests pharmacy/treatment order information for
patient 12345, from 8/12/92 through 8/13/92.
MSH|^&~\|||||199208201200||QRY^Onn^QRY_Q01|...<cr>
QRD|19920814181254|R|D|9200785|||45^RD|12345|RER|...<cr>
QRF|PHM|19920812000000|19920813235959|...<cr>
DSC|...<cr>
MSH|^&~\|||||199208201201||RER^RER^RER_RER|...<cr>
MSA|AA|1001|...<cr>
QRD|...<cr>
QRF|...<cr>
ORC|RE|3346^OE|R23^RX|...<cr>
RXE|^BID^D5^199208120800^199208162000|10986^AMPICILLIN|250||MG|...<cr>
RXR|PO|...<cr>
ORC|RE|3987^OE|R76^RX|...<cr>
RXE|^TID^D7^199208120600^199208182200|12796^ASPIRIN|325||MG|...<cr>
RXR|PO|...<cr>
DSC|...<cr>
The lab application requests pharmacy/treatment administration information for
patient 12345, from 8/12/92 through 8/13/92.
MSH|^&~\|||||199208201200||QRY^Onn^QRY_Q01|...<cr>
QRD|19920814165645|R|D|9200231|||30^RD|12345|RAR|...<cr>
QRF|PHM|19920812000000|19920813235959|...<cr>
DSC|...<cr>
MSH|^&~\|||||199208201201||RAR^RAR^RAR_RAR|...<cr>
MSA|AA|1002|...<cr>
QRD|...<cr>
QRF|...<cr>
ORC|RE||R23^RX|...<cr>
RXE|^BID^D5^199208120800^199208162000|10986^AMPICILLIN|250||MG|...<cr>
RXR|PO|...<cr>
RXA|1|1|199208120800|199208120800|10986^AMPICILLIN|250|...<cr>
RXA|2|2|199208122000|199208122000|10986^AMPICILLIN|250|...<cr>
RXA|3|3|199208130800|199208130800|10986^AMPICILLIN|250|...<cr>
RXA|4|4|199208132000|199208132000|10986^AMPICILLIN|250|...<cr>
ORC|RE||R76^RX|...<cr>
RXE|^TID^D7^199208120600^199208182200|12796^ASPIRIN|325||MG|...<cr>
RXR|PO|...<cr>RXA|1|1|199208120600|199208120600|12796^ASPIRIN|325|...<cr>
RXA|2|2|199208121400|199208121400|12796^ASPIRIN|325|...<cr>
RXA|3|3|199208122200|199208122200|12796^ASPIRIN|325|...<cr>
RXA|4|4|199208130600|199208130600|12796^ASPIRIN|325|...<cr>
RXA|5|5|199208131400|199208131400|12796^ASPIRIN|325|...<cr>
RXA|6|6|199208132200|199208132200|12796^ASPIRIN|325|...<cr>
DSC|...<cr>
The nursing system requests pharmacy/treatment dose information for patient
12345, from 8/12/92 through 8/13/92.
MSH|^&~\|||||199208201200||QRY^Onn^QRY_Q01|...<cr>
QRD|19920814172309|R|D|9200543|||100^RD|12345|RGR|...<cr>
QRF|PHM|19920812000000|19920813235959|...<cr>
DSC|...<cr>
MSH|^&~\|||||199208201201||RGR^RGR^RGR_RGR|...<cr>
MSA|AA|1003|...<cr>
QRD|...<cr>
QRF|...<cr>
ORC|RE||R23^RX|...<cr>
RXE|^BID^D5^199208120800^199208162000|10986^AMPICILLIN|250||MG|...<cr>
RXR|PO|...<cr>
RXG|1||^^^199208120701|10986^AMPICILLIN|250|...<cr>
RXG|2||^^^199208121923|10986^AMPICILLIN|250|...<cr>
RXG|3||^^^199208130702|10986^AMPICILLIN|250|...<cr>
RXA|4||^^^199208131912|10986^AMPICILLIN|250|...<cr>
ORC|RE||R76^RX|...<cr>
RXE|^TID^D7^199208120600^199208182200|12796^ASPIRIN|325||MG|...<cr>
RXR|PO|...<cr>
RXG|1||^^^199208120459|12796^ASPIRIN|325|...<cr>
RXG|2||^^^199208121328|12796^ASPIRIN|325|...<cr>
RXG|3||^^^199208122101|12796^ASPIRIN|325|...<cr>
RXG|4||^^^199208130503|12796^ASPIRIN|325|...<cr>
RXG|5||^^^199208131311|12796^ASPIRIN|325|...<cr>
RXG|6||^^^199208132145|12796^ASPIRIN|325|...<cr>
DSC|...<cr>
The following are possible routes at a generic site.
1. ORM/RXO |
||||
1. ORM/RXO |
2. RDE/RXE |
|||
Ordering System |
2. RDE/RXE |
Pharmacy/ Treatment Supplier |
3. RDS/RXD |
Nursing |
4. RGV/RXG |
||||
5. RAS/RXA |
||||
5. RAS/RXA |
The Ordering application generates a pharmacy/treatment order (ORM with RXO and possibly additional RXC segments) and sends it to the pharmacy or treatment application, Nursing application, and/or other applications as appropriate at the site.
The pharmacy/treatment application may send the RDE, the Pharmacy/Treatment Encoded Order message, a fully encoded order to the Nursing application, Ordering application, and/or other system applications as appropriate at the site.
The pharmacy/treatment application may send the RDS, the Pharmacy/Treatment Dispense message, to the Nursing application or other applications as appropriate at the site, each time a medication is dispensed for this order. This message may occur multiple times for each order.
The pharmacy application may send the RGV, the Pharmacy/Treatment Give message, to the Nursing application or other applications as appropriate at the site, for each scheduled date/time of administration of a medication for a given order. This message may occur multiple times for each order.
The
Nursing application (and other applications) can generate the RAS, the
pharmacy/treatment Administration Results message, whenever a medication is
given to the patient. This message may occur multiple times for each order.
Note: Sites having a long term clinical data repository may wish to
route data to the data repository from copies of all or any of the five messages.
The
message header segment will carry one of four event types at MSH-9-message
type:
Event |
Description |
V01 |
Query for Vaccination Record |
V02 |
Response to Vaccination Query (V01) Returning Multiple PID Matches |
V03 |
Response to Query (V01) Returning Vaccination Record |
V04 |
Unsolicited Update to Vaccination Record |
Immunization
registries that maintain vaccination records need to be able to transmit
patient-specific records of vaccines administered to other registries to
provide access to the record at the time healthcare is given and to allow
tracking of progress in reaching age-appropriate immunization coverage. The
transmissions will occur as the result of four activities: (1) a query from
one system for a patient's vaccination record that is held in another system,
(2) a response to a query containing multiple patient matches to the query, (3)
a response to a query containing the vaccination record, and (4) an unsolicited
update to an immunization registry
These messages permit the transmission of immunization records from care
providers to immunization registries, queries of these registries for
immunization records, and the return of these immunization records to care
providers. Messages containing immunization records carry patient identifying
information in the PID segment. They may also carry parent or guardian
information in the NK1 segments to help identify a child. The RXA segment is
used to report the details of the immunization event: the type of vaccine
(e.g., DPT, polio, MMR), the date administered, the sequence (1st, 2nd, etc.),
the amount (e.g., 0.5 ml), and location and provider of the immunization. In
addition, the RXA provides a place to record the lot number, manufacturer and
date of expiration of the immunization. The RXA can also be used to report the
fact that a specified immunization was refused. This section includes two
tables (0292 and 0227) maintained by the U.S. Centers for Disease Control and
Prevention (CDC). These tables are recommended in the U.S. for identifying the
immunization in field RXA-5-administered code and the vaccine
manufacturer in field RXA-17-substance manufacturer name.
The
VXQ, VXX, and VXR messages defined below incorporate the QRF segment defined at
2.24.5, "QRF - original style query filter segment." QRF-5-other query
subject filter is a locally defined filter for use between two systems
which mutually agree on a definition. For transferring vaccination
administration data, QRF-5-other QRY subject filter should be structured
as shown in Figure 4-20 to transmit up to ten separate search "keys." These
search keys are only used to identify one patient's immunization record. The
message provides for a wide variety of "identifying" keys including mother's
and/or father's name and other identifiers; in some cases such information will
be needed to identify a specific patient in the immunization database.
The format of each of the possible "search keys" is given below, and listed in
a more structured form in Figure 4-20. These keys are transmitted as
strings separated by repeat delimiters. The position of the components within
QRF-5-other QRY subject filter is significant. The requester sends
values for all the components that are known.
Components: <patient social security number> ~ <patient birth
date> ~ <patient birth state> ~ <patient birth registration
number> ~ <patient medicaid number> ~ <mother's name
last^first^middle> ~ <mother's maiden name> ~ <mother's Social
Security number> ~ <father's name last^first^middle> ~ <father's
Social Security number>
Pos |
Component |
Data Type |
Description/Examples |
1 |
Patient Social Security Number~ |
ST |
In U.S., use SSN, without hyphens between 3rd and 4th digits and 5th and 6th digits, e.g., 123456789. In other countries, universal patient ID such as National Health Service number may be used. |
2 |
Patient Birth Date~ |
DT |
July 4, 1976 = 19760704 |
3 |
Patient Birth State~ |
ID |
In U.S., use 2-letter postal code, e.g., IN, NY, CA. In other countries, locally applicable postal table may be used. |
4 |
Patient Birth Registration Number~ |
ST |
State birth certificate number |
5 |
Patient Medicaid Number~ |
ST |
When relevant |
6 |
Mother's Name Last^First^Middle~ |
PN |
<family
name> ^ <given name> ^ <middle name or initial> ^ <suffix>
|
7 |
Mother's Maiden Name~ |
ST |
Family name of mother before marriage. E.g., Jones |
8 |
Mother's Social Security Number~ |
ST |
In U.S., use SSN, without hyphens between 3rd and 4th digits and 5th and 6th digits, e.g., 123456789. In other countries, universal patient ID such as National Health Service number may be used. |
9 |
Father's Name Last^First^Middle~ |
PN |
<family
name> ^ <given name> ^ <middle name or initial> ^
<suffix> |
10 |
Father's Social Security Number |
ST |
In U.S., use SSN, without hyphens between 3rd and 4th digits and 5th and 6th digits, e.g., 123456789. In other countries, universal patient ID such as National Health Service number may be used. |
For
instance, if the requestor knew only the patient's Social Security number and
birthdate, this QRF-5-other QRY subject filter would be sent:
|908723461~19941005|
If, in addition, the patient's birth state and mother's current and maiden name
were known, this QRF-5-other QRY subject filter would be sent:
|908723461~19941005~IN~~~HUTCHINS^KATHY^ANN~HARKNESS|
Definition:
When an immunization registry does not already have the complete patient
vaccination record, it will send a query (with a V01 event) for the definitive
(last updated) record. Within the definitions for QRD and QRF, certain
components are defined according to position in the field, as detailed in
Section 4.17.2, "Queries for immunization records (QRF Segments)." The
three-letter code in the leftmost column indicates the segment that is
included; the column on the right specifies the chapter in which that segment
is fully defined.
The query will follow this format:
VXQ^V01 |
Vaccination Query |
Chapter |
MSH |
Message Header Segment |
2 |
QRD |
Query Definition Segment |
2 |
[QRF] |
Query Filter Segment |
2 |
Definition:
In response to a query for the definitive patient vaccination record, the
registry holding the record will return it to the registry originating the
query.
If the query results in multiple "matches," i.e., more than one patient record
matches the identifiers in the query so that there is no unique identification,
the response to the query (with a V02 event) will follow this format. Within
the definitions for QRD and QRF, certain components are defined according to
position in the field, as detailed in Section 4.17.2, "Queries for immunization
records (QRF Segments)." The three-letter code in the leftmost column
indicates the segment that is included; the column on the right specifies the
chapter in which that segment is fully defined.
VXX^V02 |
Returning Multiple PID Matches |
Chapter |
MSH |
Message Header |
2 |
MSA |
Message Acknowledgment |
2 |
QRD |
Query Definition |
2 |
[QRF] |
Query Filter |
2 |
{PID |
Patient Identification |
3 |
[{NK1}] |
Next of Kin/Associated Parties |
3 |
} |
Definition:
When the patient has been uniquely identified (there is only one "match" to
the query), the response to the query (with a V03 event) will follow this
format. Within the definitions for QRD and QRF, certain components are defined
according to position in the field, as detailed in Section 4.17.2, "Queries for
immunization records (QRF Segments)." The three-letter code in the leftmost
column indicates the segment that is included; the column on the right
specifies the chapter in which that segment is fully defined.
VXR^V03 |
Vaccination Response |
Chapter |
MSH |
Message Header |
2 |
MSA |
Message Acknowledgment |
2 |
QRD |
Query Definition |
2 |
[QRF] |
Query Filter |
2 |
PID |
Patient Identification |
3 |
[PD1] |
Additional Demographics |
3 |
[{NK1}] |
Next of Kin/Associated Parties |
3 |
[PV1 |
Patient Visit |
3 |
[PV2]] |
Patient Visit - Additional Info |
3 |
[{GT1}] |
Guarantor |
6 |
[{IN1 |
Insurance |
6 |
[IN2] |
Insurance Additional Info |
6 |
[IN3] |
Insurance Add'l Info - Cert. |
6 |
}] |
||
[{ |
||
[ORC] |
Common Order |
4 |
RXA |
Pharmacy Administration |
4 |
[RXR] |
Pharmacy Route |
4 |
[{OBX |
Observation/Result |
7 |
[{NTE}] |
Notes (Regarding Immunization) |
2 |
}] |
||
}] |
Definition:
When a provider wishes to update the patient's vaccination record being held
in a registry, he will transmit an unsolicited update of the record (a V04
trigger event).
An unsolicited update will follow this format. The three-letter code in the
leftmost column indicates the segment that is included; the column on the right
specifies the chapter in which that segment is fully defined.
VXU^V04 |
Unsolicited Vaccination Update |
Chapter |
MSH |
Message Header Segment |
2 |
PID |
Patient Identification Segment |
3 |
[PD1] |
Additional Demographics |
3 |
[{NK1}] |
Next of Kin/Associated Parties |
3 |
[PV1 |
Patient Visit |
3 |
[PV2]] |
Patient Visit - Additional Info |
3 |
[{GT1}] |
Guarantor |
6 |
[{IN1 |
Insurance |
6 |
[IN2] |
Insurance Additional Info |
6 |
[IN3] |
Insurance Add'l Info - Cert. |
6 |
}] |
||
[{ |
||
[ORC] |
Common Order Segment |
4 |
RXA |
Pharmacy Administration Segment |
4 |
[RXR] |
Pharmacy Route |
4 |
{[ OBX |
Observation/Result |
7 |
[{NTE}] |
Notes (Regarding Immunization) |
2 |
]} |
||
}] |
With
the exception of RXA-5-Administered code and RXA-17-Substance
manufacturer name, the structure for the RXA segment below is identical to
that documented in section 4.14.7. When using the RXA segment for vaccine
messages, H
L7
Table 0292- V
accines
Administered, should be used for RXA-5- Administered code, as noted in
Section <IP_ADDRESS>. HL7 Table 0227- Manufacturers of Vaccines,
should be used for RXA-17- Substance manufacturer name, as noted in
Section <IP_ADDRESS>
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM # |
ELEMENT NAME |
|---|---|---|---|---|---|---|---|
1 |
4 |
NM |
R |
00342 |
Give Sub-ID Counter |
||
2 |
4 |
NM |
R |
00344 |
Administration Sub-ID Counter |
||
3 |
26 |
TS |
R |
00345 |
Date/Time Start of Administration |
||
4 |
26 |
TS |
R |
00346 |
Date/Time End of Administration |
||
5 |
250 |
CE |
R |
0292 |
00347 |
Administered Code |
|
6 |
20 |
NM |
R |
00348 |
Administered Amount |
||
7 |
250 |
CE |
C |
00349 |
Administered Units |
||
8 |
250 |
CE |
O |
00350 |
Administered Dosage Form |
||
9 |
250 |
CE |
O |
Y |
00351 |
Administration Notes |
|
10 |
250 |
XCN |
O |
Y |
00352 |
Administering Provider |
|
11 |
200 |
CM |
C |
00353 |
Administered-at Location |
||
12 |
20 |
ST |
C |
00354 |
Administered Per (Time Unit) |
||
13 |
20 |
NM |
O |
01134 |
Administered Strength |
||
14 |
250 |
CE |
O |
01135 |
Administered Strength Units |
||
15 |
20 |
ST |
O |
Y |
01129 |
Substance Lot Number |
|
16 |
26 |
TS |
O |
Y |
01130 |
Substance Expiration Date |
|
17 |
250 |
CE |
O |
Y |
0227 |
01131 |
Substance Manufacturer Name |
18 |
250 |
CE |
O |
Y |
01136 |
Substance/Treatment Refusal Reason |
|
19 |
250 |
CE |
O |
Y |
01123 |
Indication |
|
20 |
2 |
ID |
O |
0322 |
01223 |
Completion Status |
|
21 |
2 |
ID |
O |
0323 |
01224 |
Action Code - RXA |
|
22 |
26 |
TS |
O |
01225 |
System Entry Date/Time |
Use
in RXA-5- administered code to identify the particular vaccine
administered. The codes listed are used by immunization by immunization
registries in the U.S. Entries will be added as needed to accommodate
international requirements.
Code |
Short Description |
Full Vaccine Name |
|---|---|---|
54 |
adenovirus, type 4 |
adenovirus vaccine, type 4, live, oral |
55 |
adenovirus, type 7 |
adenovirus vaccine, type 7, live, oral |
82 |
adenovirus, NOS1 |
adenovirus vaccine, NOS |
24 |
anthrax |
anthrax vaccine |
19 |
BCG |
Bacillus Calmette-Guerin vaccine |
27 |
botulinum antitoxin |
botulinum antitoxin |
26 |
cholera |
cholera vaccine |
29 |
CMVIG |
cytomegalovirus immune globulin, intravenous |
56 |
dengue fever |
dengue fever vaccine |
12 |
diphtheria antitoxin |
diphtheria antitoxin |
28 |
DT (pediatric) |
diphtheria and tetanus toxoids, adsorbed for pediatric use |
20 |
DTaP |
diphtheria, tetanus toxoids and acellular pertussis vaccine |
50 |
DTaP-Hib |
DTaP-Haemophilus influenzae type b conjugate vaccine |
01 |
DTP |
diphtheria, tetanus toxoids and pertussis vaccine |
22 |
DTP-Hib |
DTP-Haemophilus influenzae type b conjugate vaccine |
57 |
hantavirus |
hantavirus vaccine |
52 |
Hep A, adult |
hepatitis A vaccine, adult dosage |
83 |
Hep A, ped/adol, 2 dose |
hepatitis A vaccine, pediatric/adolescent dosage, 2 dose schedule |
84 |
Hep A, ped/adol, 3 dose |
hepatitis A vaccine, pediatric/adolescent dosage, 3 dose schedule |
31 |
Hep A, pediatric, NOS |
hepatitis A vaccine, pediatric dosage, NOS |
85 |
Hep A, NOS |
hepatitis A vaccine, NOS |
30 |
HBIG |
hepatitis B immune globulin |
08 |
Hep B, adolescent or pediatric |
hepatitis B vaccine, pediatric or pediatric/adolescent dosage |
42 |
Hep B, adolescent/high risk infant2 |
hepatitis B vaccine, adolescent/high risk infant dosage |
43 |
Hep B, adult4 |
hepatitis B vaccine, adult dosage |
44 |
Hep B, dialysis |
hepatitis B vaccine, dialysis patient dosage |
45 |
Hep B, NOS |
hepatitis B vaccine, NOS |
58 |
Hep C |
hepatitis C vaccine |
59 |
Hep E |
hepatitis E vaccine |
60 |
herpes simplex 2 |
herpes simplex virus, type 2 vaccine |
46 |
Hib (PRP-D) |
Haemophilus influenzae type b vaccine, PRP-D conjugate |
47 |
Hib (HbOC) |
Haemophilus influenzae type b vaccine, HbOC conjugate |
48 |
Hib (PRP-T) |
Haemophilus influenzae type b vaccine, PRP-T conjugate |
49 |
Hib (PRP-OMP) |
Haemophilus influenzae type b vaccine, PRP-OMP conjugate |
17 |
Hib, NOS |
Haemophilus influenzae type b vaccine, conjugate NOS |
51 |
Hib-Hep B |
Haemophilus influenzae type b conjugate and Hepatitis B vaccine |
61 |
HIV |
human immunodeficiency virus vaccine |
62 |
HPV |
human papilloma virus vaccine |
86 |
IG |
immune globulin, intramuscular |
87 |
IGIV |
immune globulin, intravenous |
14 |
IG, NOS |
immune globulin, NOS |
15 |
influenza, split (incl. purified surface antigen) |
influenza virus vaccine, split virus (incl. purified surface antigen) |
16 |
influenza, whole |
influenza virus vaccine, whole virus |
88 |
influenza, NOS |
influenza virus vaccine, NOS |
10 |
IPV |
poliovirus vaccine, inactivated |
02 |
OPV |
poliovirus vaccine, live, oral |
89 |
polio, NOS |
poliovirus vaccine, NOS |
39 |
Japanese encephalitis |
Japanese encephalitis vaccine |
63 |
Junin virus |
Junin virus vaccine |
64 |
leishmaniasis |
leishmaniasis vaccine |
65 |
leprosy |
leprosy vaccine |
66 |
Lyme disease |
Lyme disease vaccine |
03 |
MMR |
measles, mumps and rubella virus vaccine |
04 |
M/R |
measles and rubella virus vaccine |
94 |
MMRV |
measles, mumps, rubella, and varicella virus vaccine |
67 |
malaria |
malaria vaccine |
05 |
measles |
measles virus vaccine |
68 |
melanoma |
melanoma vaccine |
32 |
meningococcal |
meningococcal polysaccharide vaccine |
07 |
mumps |
mumps virus vaccine |
69 |
parainfluenza-3 |
parainfluenza-3 virus vaccine |
11 |
pertussis |
pertussis vaccine |
23 |
plague |
plague vaccine |
33 |
pneumococcal |
pneumococcal polysaccharide vaccine |
100 |
pneumococcal conjugate |
pneumococcal conjugate vaccine, polyvalent |
70 |
Q fever |
Q fever vaccine |
18 |
rabies, intramuscular injection |
rabies vaccine, for intramuscular injection |
40 |
rabies, intradermal injection |
rabies vaccine, for intradermal injection |
90 |
rabies, NOS |
rabies vaccine, NOS |
72 |
rheumatic fever |
rheumatic fever vaccine |
73 |
Rift Valley fever |
Rift Valley fever vaccine |
34 |
RIG |
rabies immune globulin |
74 |
rotavirus |
rotavirus vaccine, tetravalent, live, oral |
71 |
RSV-IGIV |
respiratory syncytial virus immune globulin, intravenous |
93 |
RSV-Mab |
respiratory syncytial virus monoclonal antibody (palivizumab), intramuscular |
06 |
rubella |
rubella virus vaccine |
38 |
rubella/mumps |
rubella and mumps virus vaccine |
75 |
smallpox |
smallpox vaccine |
76 |
Staphylococcus bacterio lysate |
Staphylococcus bacteriophage lysate |
09 |
Td (adult) |
tetanus and diphtheria toxoids, adsorbed for adult use |
35 |
tetanus toxoid |
tetanus toxoid |
77 |
tick-borne encephalitis |
tick-borne encephalitis vaccine |
13 |
TIG |
tetanus immune globulin |
95 |
TST-OT tine test |
tuberculin skin test; old tuberculin, multipuncture device |
96 |
TST-PPD intradermal |
tuberculin skin test; purified protein derivative solution, intradermal |
97 |
TST-PPD tine test |
tuberculin skin test; purified protein derivative, multipuncture device |
98 |
TST, NOS |
tuberculin skin test; NOS |
78 |
tularemia vaccine |
tularemia vaccine |
25 |
typhoid, oral |
typhoid vaccine, live, oral |
41 |
typhoid, parenteral |
typhoid vaccine, parenteral, other than acetone-killed, dried |
53 |
typhoid, parenteral, AKD (U.S. military) |
typhoid vaccine, parenteral, acetone-killed, dried (U.S. military) |
101 |
typhoid, ViCPs |
Typhoid Vi capsular polysaccharide vaccine |
91 |
typhoid, NOS |
typhoid vaccine, NOS |
79 |
vaccinia immune globulin |
vaccinia immune globulin |
21 |
varicella |
varicella virus vaccine |
81 |
VEE, inactivated |
Venezuelan equine encephalitis, inactivated |
80 |
VEE, live |
Venezuelan equine encephalitis, live, attenuated |
92 |
VEE, NOS |
Venezuelan equine encephalitis vaccine, NOS |
36 |
VZIG |
varicella zoster immune globulin |
37 |
yellow fever |
yellow fever vaccine |
999 |
unknown |
unknown vaccine or immune globulin |
99 |
RESERVED - do not use3 |
RESERVED - do not use |
Usage
Notes:
NOS=not otherwise specified; avoid using NOS codes except to record historical
records that lack the indicated specificity
As of August 27, 1998, Merck ceased distribution of their adolescent/high risk
infant hepatitis B vaccine dosage. Code 42 should only be used to record
historical records. For current administration of hepatitis B vaccine,
pediatric/adolescent dosage, use code 08.
Code 99 will not be used in this table to avoid confusion with code 999.
As of September 1999, a 2-dose hepatitis B schedule for adolescents (11-15 year
olds) was FDA approved for Merck's Recombivax HB® adult formulation. Use
code 43 for both the 2-dose and the 3-dose schedules.
The codes in HL7 Table 0292 represent the first revision (January 14,
1998) of the initial content of the external code set CVX. Since vaccines may
have to be added to this table more quickly than new versions of HL7 are
released, this code system will be maintained by the Centers for Disease
Control and Prevention. (Contact the Chief, Systems Development Branch,
National Immunization Program, Centers for Disease Control and Prevention, 1600
Clifton Road, MS E-62, Atlanta, GA 30333; 1-800-799-7062,
http://www.cdc.gov/nip/registry.) When using this code system to identify
vaccines, the coding system component of the CE field should be valued as
"CVX", not as "
HL70292."
Use
in RXA-17-substance manufacturer name to identify the manufacturer or
distributor of the particular vaccine administered. The codes listed are used
by immunization registries in the U.S. Entries will be added as needed to
accommodate international requirements.
Code |
Vaccine Manufacturer/Distributor |
|---|---|
AB |
Abbott Laboratories (includes Ross Products Division) |
AD |
Adams Laboratories |
ALP |
Alpha Therapeutic Corporation |
AR |
Armour [Inactive-use CEN] |
AVI |
Aviron |
BA |
Baxter Healthcare Corporation |
BAY |
Bayer Corporation(includes Miles, Inc. and Cutter Laboratories) |
BP |
Berna Products [Inactive-use BPC] |
BPC |
Berna Products Corporation (includes Swiss Serum and Vaccine Institute Berne) |
CEN |
Centeon L.L.C. (includes Armour Pharmaceutical Company) |
CHI |
Chiron Corporation |
CON |
Connaught [Inactive-use PMC] |
EVN |
Evans Medical Limited (an affiliate of Medeva Pharmaceuticals, Inc.) |
GRE |
Greer Laboratories, Inc. |
IAG |
Immuno International AG |
IM |
Merieux [Inactive-use PMC] |
IUS |
Immuno-U.S., Inc. |
JPN |
The Research Foundation for Microbial Diseases of Osaka University (BIKEN) |
KGC |
Korea Green Cross Corporation |
LED |
Lederle [Inactive-use WAL] |
MA |
Massachusetts Public Health Biologic Laboratories |
MED |
MedImmune, Inc. |
MIL |
Miles [Inactive-use BAY] |
MIP |
Bioport Corporation (formerly Michigan Biologic Products Institute) |
MSD |
Merck & Co., Inc. |
NAB |
NABI (formerly North American Biologicals, Inc.) |
NYB |
New York Blood Center |
NAV |
North American Vaccine, Inc. |
NOV |
Novartis Pharmaceutical Corporation (includes Ciba-Geigy Limited and Sandoz Limited) |
OTC |
Organon Teknika Corporation |
ORT |
Ortho Diagnostic Systems, Inc. |
PD |
Parkedale Pharmaceuticals (formerly Parke-Davis) |
PMC |
Aventis Pasteur Inc. (formerly Pasteur Merieux Connaught; includes Connaught Laboratories and Pasteur Merieux) |
PRX |
Praxis Biologics [Inactive-use WAL] |
SCL |
Sclavo, Inc. |
SI |
Swiss Serum and Vaccine Inst. [Inactive-use BPC] |
SKB |
SmithKline Beecham |
USA |
United States Army Medical Research and Materiel Command |
WA |
Wyeth-Ayerst [Inactive-use WAL] |
WAL |
Wyeth-Ayerst (includes Wyeth-Lederle Vaccines and Pediatrics, Wyeth Laboratories, Lederle Laboratories, and Praxis Biologics) |
OTH |
Other manufacturer |
UNK |
Unknown manufacturer |
The codes in HL7 Table 0227 represent the first revision (January 14, 1998) of the initial content of the external code set MVX. Since vaccine manufacturers may have to be added to this table more quickly than new versions of HL7 are released, this code system will be maintained by the Centers for Disease Control and Prevention. (Contact the CDC, as noted in Section <IP_ADDRESS> "RXA field definitions"). When using this code system to identify vaccines, the coding system component of the CE field should be valued as "MVX", not as "HL70227."
MSH|^~\&||GAVACREC||AZVACREC|199505221605||VXQ^V01|
...<cr>
QRD|199505221605|R|I|950522GA40|||1000^RD|^JONES^JOHN^RICHARD|VXI|SIIS|...<cr>
QRF|AZVACREC||||256946789~19900607~CA~CA99999999~88888888~JONES^MARY^SUE~SMITH~898666725~JONES^MATHEW^LEE~822546618|...<cr>
In this query, Georgia Vaccine Records is sending a request to Arizona Vaccine
Records for an immunization record. The request is being sent on May 22, 1995,
at 4:05 p.m. Identifiers other than patient name are defined in the query by
giving positional meaning to the repeat delimiters in the QRF-5-other query
subject filter field, as specified in 4.17.2, "Queries for immunization
records (QRF Segments)." The responding system is expected to return all query
items in their response. The QRD segment, at QRD-8-who subject filter,
identifies the patient name. QRD-9-what subject filter reflects the new
VXI category of Vaccination Information. QRD-10-what department data
code shows SIIS.
In our example, we are sending a query for the record of John Richard Jones.
The patient's Social Security number is 256-94-6789; the patient birth date is
June 7, 1990; the patient birth state is CA; the patient birth registration
number is CA99999999; and the patient Medicaid number is 88888888.  Her Social
Security number is 898-66-6725. The patient's father is Mathew Lee Jones, and
the father's Social Security number is 822-54-6618.
MSH|^~\&||AZVACREC||GAVACREC|199505221606||VXX^V02|...<cr>
MSA|...<cr>
QRD|199505221605|R|I|950522GA40|||1000^RD|^JONES^RICHARD|VXI|SIIS|...<cr>
QRF|AZVACREC||||~~~~~JONES^MARY|...<cr>
PID|1||123456789^^^AZ||^JONES^RICHARD^ROBERT||19910607|M^MALE^HL70001|...<cr>
NK1|1|JONES^MARY^SUE|MTH^MOTHER^HL70063||||||||||||||||||||||||||||||265909900^^^^SS|...<cr>
PID|2||987654321^^^AZ||^JONES^JOHN^RICHARD||19900607|M^MALE^HL70001|...<cr>
NK1|1|JONES^MARY|MTH^MOTHER^HL70063||||||||||||||||||||||||||||||898666725^^^^SS|...<cr>
NK1|2|JONES^MATHEW^LEE|FTH^FATHER^HL70063||||||||||||||||||||||||||||||822546618^^^^SS|...<cr>
PID|3||231453675^^^AZ||^JONES^RICHARD^CURTIS||19901225|M^MALE^HL70001|...<cr>
NK1|1|JONES^MARY^ANN|MTH^MOTHER^HL70063||||||||||||||||||||||||||||||288763102^^^^SS|...<cr>
PID|4||908786564^^^AZ||^JONES^RICHARD^ALAN||19870205|M^MALE^HL70001|...<cr>
NK1|1|JONES^MARY^SUE|MTH^MOTHER^HL70063||||||||||||||||||||||||||||||190966725^^^^SS|...<cr>
NK1|2|JONES^CHRISTOPHER|FTH^FATHER^HL70063||||||||||||||||||||||||||||||786118768^^^^SS|...<cr>
The example shows the response when multiple PIDs match a query. In the QRD,
the sender is querying Arizona Vaccine Records for information on Richard
Jones; the only further identifying information supplied in the QRF is that the
mother's name is Mary Jones. For each record which matches this information, a
PID is returned along with its associated NK1. The system initiating the query
may then re-send a more precise query.
MSH|^~\&||AZVACREC||GAVACREC|199505221606||VXR^V03|...<cr>
MSA|...<cr>
QRD|...<cr>
QRF|...<cr>
PID|...<cr>
NK1|1|JONES^MARY^SUE|MTH^MOTHER^HL70063||||||||||||||||||||||||||||||898666725^^^^SS|...<cr>
NK1|2|JONES^MATHEW^LEE|FTH^FATHER^HL70063||||||||||||||||||||||||||||||822546618^^^^SS|...<cr>
ORC|RE||V43^AZVAC|...<cr>
RXA|0|4|19910607|19910607|01^DTP^CVX|.5|MG^^ISO+|||1234567891^GOLDSTEIN^HAROLD^A^^DR|
^^^CHILD HEALTHCARE CLINIC^^^^^101 MAIN
STREET^^METROPOLIS^AZ||||W46932777|19910813|
SKB^SmithKline Beecham^MVX|...<cr>ORC|RE||V44^AZVAC|...<cr>
RXA|0|1|19910607|19910607|03^MMR^CVX|.5|MG^^ISO+|||1234567891^GOLDSTEIN^HAROLD^A^^DR|
^^^CHILD HEALTHCARE CLINIC^^^^^101 MAIN
STREET^^METROPOLIS^AZ||||W23487909876456|
19910725|MSD^Merck \T\ Co., Inc.^MVX|...<cr>
ORC|RE||V87^AZVAC|...<cr>
RXA|0|5|19950520|19950520|01^DTP^CVX|.5|MG^^ISO+|||1234567891^GOLDSTEIN^HAROLD^A^^DR|
^^^CHILD HEALTHCARE CLINIC^^^^^101 MAIN
STREET^^METROPOLIS^AZ||||W22532806|19950705|
SKB^SmithKline Beecham^MVX|...<cr>
ORC|RE||V88^AZVAC|...<cr>
RXA|0|2|19950520|19950520|03^MMR^CVX|.5|MG^^ISO+|||1234567891^GOLDSTEIN^HAROLD^A^^DR|
^^^CHILD HEALTHCARE CLINIC^^^^^101 MAIN
STREET^^METROPOLIS^AZ||||W2341234567|19950630|
MSD^Merck \T\ Co., Inc.^MVX|...<cr>
The example reflects a vaccination record return as might be expected by a
public health agency reporting from one immunization registry to another. It
shows repeating RXA segments reporting the first and second doses of MMR and
the fourth and fifth doses of DTP, including the manufacturer, lot number, and
expiration date. If the vaccination had been refused by the patient or
guardian, RXA-18-substance refusal reason would record the vaccine
refusal reason, utilizing a user-defined table.
MSH|^~\&||AZVACREC||GAVACREC|199505221606||VXU^V04|...<cr>
PID|...<cr>
NK1|...<cr>
NK1|...<cr>
PV1|...<cr>
PV2|...<cr>
IN1|...<cr>
IN2|||||||JONES^ALICE^P|909686637A|...<cr>
ORC|...<cr>
RXA|0|1|19950901115500|19950901115500|03^MMR^CVX|.5|MG^^ISO+|||
1234567891^GOLDSTEIN^HAROLD^A^^DR| ^^^ CHILD HEALTHCARE CLINIC^^^^^101 MAIN
STREET^ ^METROPOLIS^AZ||||W23487909876456|19951125|MSD^Merck \T\ Co.,
Inc.^MVX|...<cr>
RXR|IM^INTRAMUSCULAR^HL70162|LG^LEFT GLUTEUS MEDIUS^HL70163|...<cr>
OBX|1|NM|1000.3^TEMP.RECTAL^AS4||102.9|DEGF^^ANSI+|||||F|||19950901153000|...<cr>
NTE|||PATIENT DEVELOPED HIGH FEVER APPROX 3 HRS AFTER VACCINE INJECTION.
PROBABLE ADVERSE REACTION|...<cr>
This message shows an unsolicited update of a vaccination record. The message
type is VXU--Unsolicited Vaccination Record Update, with event code V04
(unsolicited vaccination record update). This example is given to show
possible uses for some of the optional segments in the message.
MSH|^~\&||AZVACREC||GAVACREC|19950522130550^S||DSR^Q01|...<cr>
MSA|AA|950522GA40|...<cr>
QAK||NF|...<cr>
QRD|...<cr>
The example shows the response to a query which was successfully processed, but
no qualifying data were found.
Referenced
in 4
.4.1.1
-
Order
Control
Codes
Value1 |
Event/Message Type |
Description |
Originator2 |
Field Note3 |
|---|---|---|---|---|
NW |
ORM^O01 |
New order/service |
P |
l |
OML^O21 |
||||
OMD^O03 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
OMP^O09 |
||||
OK |
ORR^O02 |
Order/service accepted & OK |
F |
l |
ORG^O20 |
||||
ORD^O04 |
||||
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
RRE^O12 |
||||
RRD^O14 |
||||
RRG^O16 |
||||
RRA^O18 |
||||
UA |
ORR^O02 |
Unable to accept order/service |
F |
n |
ORG^O20 |
||||
ORD^O04 |
||||
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
RRE^O12 |
||||
RRD^O14 |
||||
UA |
RRG^O16 |
Unable to accept order/service |
F |
n |
RRA^O18 |
||||
PR |
ORM^O01 |
Previous Results with new order/service |
P |
v |
OML^O21 |
||||
CA |
ORM^O01 |
Cancel order/service request |
P |
a |
OML^O21 |
||||
OMD^O03 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
OMP^O09 |
||||
OC |
ORM^O01 |
Order/service canceled |
F |
|
OML^O21 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
RDE^O11 |
||||
RDS^O13 |
||||
RGV^O15 |
||||
RAS^O01 |
||||
CR |
ORR^O02 |
Canceled as requested |
F |
|
ORG^O20 |
||||
ORD^O04 |
||||
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
UC |
ORR^O02 |
Unable to cancel |
F |
b |
ORG^O20 |
||||
UC |
ORD^O04 |
Unable to cancel |
F |
b |
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
DC |
ORM^O01 |
Discontinue order/service request |
P |
c |
OML^O21 |
||||
OMD^O03 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
OMP^O09 |
||||
OD |
ORM^O01 |
Order/service discontinued |
F |
|
OML^O21 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
RDE^O11 |
||||
RDS^O13 |
||||
RGV^O15 |
||||
RAS^O01 |
||||
DR |
ORR^O02 |
Discontinued as requested |
F |
|
ORG^O20 |
||||
ORD^O04 |
||||
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
UD |
ORR^O02 |
Unable to discontinue |
F |
|
ORG^O20 |
||||
UD |
ORD^O04 |
Unable to discontinue |
F |
|
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
HD |
ORM^O01 |
Hold order request |
P |
|
OML^O21 |
||||
OMD^O03 |
||||
OMP^O09 |
||||
OH |
ORM^O01 |
Order/service held |
F |
|
OML^O21 |
||||
OMS^O05 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
OMN^O07 |
||||
RDE^O11 |
||||
RDS^O13 |
||||
RGV^O15 |
||||
RAS^O01 |
||||
UH |
ORR^O02 |
Unable to put on hold |
F |
|
ORG^O20 |
||||
ORD^O04 |
||||
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
HR |
ORR^O02 |
On hold as requested |
F |
|
ORG^O20 |
||||
HR |
ORD^O04 |
On hold as requested |
F |
|
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
RL |
ORM^O01 |
Release previous hold |
P |
|
OML^O21 |
||||
OMD^O03 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
OMP^O09 |
||||
OE |
ORM^O01 |
Order/service released |
F |
|
OML^O21 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
RDE^O11 |
||||
RDS^O13 |
||||
RGV^O15 |
||||
RAS^O01 |
||||
OR |
ORR^O02 |
Released as requested |
F |
|
ORG^O20 |
||||
ORD^O04 |
||||
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
UR |
ORR^O02 |
Unable to release |
F |
|
ORG^O20 |
||||
UR |
ORD^O04 |
Unable to release |
F |
|
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
RP |
ORM^O01 |
Order/service replace request |
P |
"e,d" |
OML^O21 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
OMP^O09 |
||||
RU |
ORM^O01 |
Replaced unsolicited |
F |
"f,d" |
OML^O21 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
RDE^O11 |
||||
RO |
ORM^O01 |
Replacement order |
"P,F" |
"g,d" |
OML^O21 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
OMP^O09 |
||||
RDE^O11 |
||||
RQ |
ORR^O02 |
Replaced as requested |
F |
"d,e" |
ORG^O20 |
||||
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
UM |
ORR^O02 |
Unable to replace |
F |
|
UM |
ORG^O20 |
Unable to replace |
F |
|
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
PA |
ORM^O01 |
Parent order/service |
F |
I |
OML^O21 |
||||
OMS^O05 |
||||
OMS^O05 |
||||
OMP^O09 |
||||
RDE^O11 |
||||
RGV^O15 |
||||
RAS^O01 |
||||
ORU^R01 |
||||
CH |
ORM^O01 |
Child order/service |
"F,P" |
I |
OML^O21 |
||||
OMS^O05 |
||||
OMS^O05 |
||||
RDE^O11 |
||||
RGV^O15 |
||||
RAS^O01 |
||||
ORU^R01 |
||||
XO |
ORM^O01 |
Change order/service request |
P |
|
OML^O21 |
||||
OMD^O03 |
||||
OMS^O05 |
||||
OMS^O05 |
||||
XO |
OMP^O09 |
Change order/service request |
P |
|
XX |
ORM^O01 |
"Order/service changed, unsol." |
F |
|
OML^O21 |
||||
OMS^O05 |
||||
OMS^O05 |
||||
RDE^O11 |
||||
RDS^O13 |
||||
RDS^O13 |
||||
RGV^O15 |
||||
RAS^O01 |
||||
RAS^O01 |
||||
UX |
ORR^O02 |
Unable to change |
F |
|
ORG^O20 |
||||
ORD^O04 |
||||
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
XR |
ORR^O02 |
Changed as requested |
F |
|
ORG^O20 |
||||
ORD^O04 |
||||
ORS^O06 |
||||
ORN^O08 |
||||
ORP^O10 |
||||
DE |
ORM^O01 |
Data errors |
"P,F" |
|
ORR^O02 |
||||
ORG^O20 |
||||
DE |
ORS^O06 |
Data errors |
"P,F" |
|
ORN^O08 |
||||
ORP^O10 |
||||
RRE^O12 |
||||
RRD^O14 |
||||
RRG^O16 |
||||
RRA^O18 |
||||
RE |
ORM^O01 |
Observations/Performed Service to follow |
"P,F" |
j |
OML^O21 |
||||
RDE^O11 |
||||
RDS^O13 |
||||
RGV^O15 |
||||
RAS^O01 |
||||
ORU^R01 |
||||
RR |
ORR^O02 |
Request received |
"P,F" |
k |
SR |
ORR^O02 |
Response to send order/service status request |
F |
|
OSR^Q06 |
||||
SS |
ORM^O01 |
Send order/service status request |
P |
|
OML^O21 |
||||
SC |
ORM^O01 |
Status changed |
"F,P" |
|
OML^O21 |
||||
SN |
ORM^O01 |
Send order/service number |
F |
l |
OML^O21 |
||||
OMS^O05 |
||||
OMS^O05 |
||||
RDE^O11 |
||||
NA |
ORR^O02 |
Number assigned |
P |
l |
ORG^O20 |
||||
ORS^O06 |
||||
ORN^O08 |
||||
RRE^O12 |
||||
CN |
ORU^R01 |
Combined result |
F |
m |
RF |
ORM^O01 |
Refill order/service request |
"F, " |
o |
OMP^O09 |
||||
RDE^O11 |
||||
AF |
ORR^O02 |
Order/service refill request approval |
P |
p |
RRE^O12 |
||||
DF |
ORR^O02 |
Order/service refill request denied |
P |
q |
ORP^O10 |
||||
RRE^O12 |
||||
FU |
ORM^O01 |
"Order/service refilled, unsolicited" |
F |
r |
RDE^O11 |
||||
OF |
ORR^O02 |
Order/service refilled as requested |
F |
s |
ORP^O10 |
||||
UF |
ORR^O02 |
Unable to refill |
F |
t |
ORP^O10 |
||||
LI |
ORM^O01 |
Link order/service to patient care problem or goal |
u |
|
OML^O21 |
||||
OMS^O05 |
||||
OMS^O05 |
||||
LI |
OMP^O09 |
Link order/service to patient care problem or goal |
u |
|
RDE^O11 |
||||
RDS^O13 |
||||
RAS^O01 |
||||
UN |
ORM^O01 |
Unlink order/service from patient care problem or goal |
u |
|
OML^O21 |
||||
OMS^O05 |
||||
OMN^O07 |
||||
OMP^O09 |
||||
RDE^O11 |
||||
RDS^O13 |
||||
RAS^O01 |
Notes:
1 The order control value field
2 "F": Values originate from the filler and are not restricted to be sent only
to the placer. "P": Values originate from the placer or other application with
placer privileges (as agreed in interface negotiation).
3 See table notes below for explanation of codes.
Referenced
in <IP_ADDRESS> OBR-15 Specimen source
Value |
Description |
|---|---|
ABS |
Abscess |
AMN |
Amniotic fluid |
ASP |
Aspirate |
BPH |
Basophils |
BIFL |
Bile fluid |
BLDA |
Blood arterial |
BBL |
Blood bag |
BLDC |
Blood capillary |
BPU |
Blood product unit |
BLDV |
Blood venous |
BON |
Bone |
BRTH |
Breath (use EXHLD) |
BRO |
Bronchial |
BRN |
Burn |
CALC |
Calculus (=Stone) |
CDM |
Cardiac muscle |
CNL |
Cannula |
CTP |
Catheter tip |
CSF |
Cerebral spinal fluid |
CVM |
Cervical mucus |
CVX |
Cervix |
COL |
Colostrum |
CBLD |
Cord blood |
CNJT |
Conjunctiva |
CUR |
Curettage |
CYST |
Cyst |
DIAF |
Dialysis fluid |
DOSE |
Dose med or substance |
DRN |
Drain |
DUFL |
Duodenal fluid |
EAR |
Ear |
EARW |
Ear wax (cerumen) |
ELT |
Electrode |
ENDC |
Endocardium |
ENDM |
Endometrium |
EOS |
Eosinophils |
RBC |
Erythrocytes |
EYE |
Eye |
EXHLD |
Exhaled gas (=breath) |
FIB |
Fibroblasts |
FLT |
Filter |
FIST |
Fistula |
FLU |
Body fluid, unsp |
GAS |
Gas |
GAST |
Gastric fluid/contents |
GEN |
Genital |
GENC |
Genital cervix |
GENL |
Genital lochia |
GENV |
Genital vaginal |
HAR |
Hair |
IHG |
Inhaled Gas |
IT |
Intubation tube |
ISLT |
Isolate |
LAM |
Lamella |
WBC |
Leukocytes |
LN |
Line |
LNA |
Line arterial |
LNV |
Line venous |
LIQ |
Liquid NOS |
LYM |
Lymphocytes |
MAC |
Macrophages |
MAR |
Marrow |
MEC |
Meconium |
MBLD |
Menstrual blood |
MLK |
Milk |
MILK |
Breast milk |
NAIL |
Nail |
NOS |
Nose (nasal passage) |
ORH |
Other |
PAFL |
Pancreatic fluid |
PAT |
Patient |
PRT |
Peritoneal fluid /ascites |
PLC |
Placenta |
PLAS |
Plasma |
PLB |
Plasma bag |
PLR |
Pleural fluid (thoracentesis fld) |
PMN |
Polymorphonuclear neutrophils |
PPP |
Platelet poor plasma |
PRP |
Platelet rich plasma |
PUS |
Pus |
RT |
Route of medicine |
SAL |
Saliva |
SEM |
Seminal fluid |
SER |
Serum |
SKN |
Skin |
SKM |
Skeletal muscle |
SPRM |
Spermatozoa |
SPT |
Sputum |
SPTC |
Sputum - coughed |
SPTT |
Sputum - tracheal aspirate |
STON |
Stone (use CALC) |
STL |
Stool = Fecal |
SWT |
Sweat |
SNV |
Synovial fluid (Joint fluid) |
TEAR |
Tears |
THRT |
Throat |
THRB |
Thrombocyte (platelet) |
TISS |
Tissue |
TISG |
Tissue gall bladder |
TLGI |
Tissue large intestine |
TLNG |
Tissue lung |
TISPL |
Tissue placenta |
TSMI |
Tissue small intestine |
TISU |
Tissue ulcer |
TUB |
Tube NOS |
ULC |
Ulcer |
UMB |
Umbilical blood |
UMED |
Unknown medicine |
URTH |
Urethra |
UR |
Urine |
URC |
Urine clean catch |
URT |
Urine catheter |
URNS |
Urine sediment |
USUB |
Unknown substance |
VOM |
Vomitus |
BLD |
Whole blood |
BDY |
Whole body |
WAT |
Water |
WICK |
Wick |
WND |
Wound |
WNDA |
Wound abscess |
WNDE |
Wound exudate |
WNDD |
Wound drainage |
XXX |
To be specified in another part of the message |
None.


Save weeks of development time by creating a project with all the plumbing for a beautiful, fast, and maintainable web application
RESTility provides a clean, reusable, typesafe architecture for calling REST services with GWT
Tokenized identity provides shared tokens and SAML authentication to secure your enterprise
Don't take our word for it. Create your own Spiffy UI application and have it running in under a minute.
Spiffy UI is all open source under the Apache 2.0 license.
Tens of thousands of people run Spiffy UI every day.
Flexible CSS layouts and a small download size make it easy to support your favorite mobile device.


Stores choices to the questions from the demographics survey and user intent questions.
| Name | Description |
|---|---|
| question_id | Integer id for the questions |
| choice_id | The choice id helps to identify how a learner responded to a demographic question. The choice id itself is not a unique identifier, but the question id/choice id combo is unique and relates to a specific choice description (choice_desc) that provides the text of a learner's answer selection. |
| choice_desc | Indicated by a unique question id/choice id combo, this provides the text of a learner's answer selection to a demographic question. |
CREATE TABLE demographics_choices ( question_id int4 ,choice_id int4 ,choice_desc varchar ,PRIMARY KEY (question_id, choice_id) );


{% extends 'layout.html' %} {% block content %} {{ block.super }}
Are you sure you want to delete {{ attendant.full_name }}?


Tim's Weather Station
Search a city for the forecast
City Search
Search
Clear Search History
5 Day Forecast:


--- layout: post title: Fred Brooks quoth date: 2006-06-27 00:00:00 category: software-development ---
Fred Brooks quoth: "Much of present-day software-acquisition procedure rests upon the assumption that one can specify a satisfactory system in advance, get bids for its construction, have it built, and install it. I think this assumption is fundamentally wrong, and that many software-acquisition problems spring from that fallacy."


Hello there, I am a User Experience Designer at Konrad Group in New York City. Recent grad of the University of Connecticut’s Digital Media & Design program.


---
layout: default
---
Phi Lab
Research topics
Learning of complex representations | How do we learn complex networks that surround us? We use tools from
network science, applied topology and deep learning to understand the process of learning of complex (spatial and non-spatial)
representations of the world.
Reorganization of brain networks | What rules govern constant changes in brain network configuration?
We use network neuroscience and neuroimaging techniques to study the dynamics of functional brain networks
during cognitive tasks and learning.
Dynamics of brain-body interaction | How our body interacts with the brain network? We want to understand
interactions between brain and body during cognition.
Creative flow and art perception | What are neuronal mechanisms of creative process in humans? Why art
plays so important role in human lives? We seek to understand how brain-body interaction shapes the creative flow
and art perception.
<EMAIL_ADDRESS>Centre for Modern Interdisciplinary Technologies
Nicolaus Copernicus University, Wileńska 4, 87-100 Toruń, Poland


Attached to nothing
module A: { ... };
let f: t;
Attached to value
let e: unit => t;
Attached to external
module type S = { ... };
class c: { ... }
class type cs{ ... }
type x += | X;
Attached to extension
module S := A
Attached to module subst
type s := t;
Attached to type subst


| 038:015 Khan | : |
And these only wait for a single Saihah [shout (i.e. the blowing of the Trumpet by the angel Israfil Sarafil)] there will be no pause or ending thereto [till everything will perish except Allah (the only God full of Majesty, Bounty and Honour)]. |
| 038:015 Maulana | : |
And these wait but for one cry, wherein there is no delay. |
| 038:015 Pickthal | : |
These wait for but one Shout, there will be no second thereto. |
| 038:015 Rashad | : |
These people can expect a single blow, from which they never recover. |
| 038:015 Sarwar | : |
They had only to wait for the single inevitable blast. |
| 038:015 Shakir | : |
Nor do these await aught but a single cry, there being no delay in it. |
| 038:015 Sherali | : |
And these now wait only for a single blast, and there shall be no delaying it. |
| 038:015 Yusufali | : |
These (today) only wait for a single mighty Blast, which (when it comes) will brook no delay. |
Concepts/Themes Covered: أركان الإسلام > التوحيد > توحيد الله تعالي > إنذار من لا يعترف بتوحيد الله تعالي بالانتقام Pillars of Islam> Islamic> Oneness of Allah>A Warning to all who do not Acknowledge his Glory Oneness that He'll take Retribution from them
This tool uses eight English parallel translations for the Holy Quran imported from Mr. Clay Smith. You can also visit Qurany Concepts for browsing the Quran themes or topics. If you want to search the Holy Quran for keywords, please visit Qurany Keywords.


Targeted Segment
Apple's Customer Segment
Corresponding Segment
Age
Customize
Features
Attributes |
|
|
Age: 18 - 25 years old |
|
|
Section: Technology in The Wall Street Journal |
|
|
Income: $100K - $150K |
|
Outcomes
Results
-
65 & older represent a majority of customer interaction
We discovered that a demographic of individuals ages 65 & older were a large customer...
-
More CEO’s exposure to ads than CTO’s
After analysis, we found that CEO’s spend an immense amount of time scanning the articles with your advertisements...
-
More females click on ads than males
The success of this campaign is based on the insights we have on female readers, thus it would be beneficial to brand the ads in a way that better appeal to this demographic...


Inventory
Backpacks
Vests
Belt
Capacity:
20
Used Space:
0
Select an item to add
Item
Weight
Add to Backpack


Select Bucket:
To save a single log to logman bucket, make POST request to url:
{{protocol}}//{{host}}/api/write?key={{ (sbucket)? sbucket.write_token : 'bucket_write_key' }}
With data in JSON format:
{ log_type: 1, //type of log: 1-error, 2-success, 3-warning,4-info message: 'Err...', //log message //Optional parameters data: { //aditional data innerException: {message:'...'} }, datetime: '1-1-2013 10:00', //time when error occurred on server data_type: '.net exception', //not used for now, but indicates 'data' field format sources: [{ //Name and IP of machine that generated an error, name: 'my server', //if logman Proxy is used, it will append his hostname and ip ip_address: '<IP_ADDRESS>' }] }