Please use a compatible browser :Google Chrome or Mozilla Firefox
Page expired. Any change will be lost. Try to refresh the page.
Gazelle update scheduled, unsaved changes will be lost :
Your session will timeout :
Redeployed...
Logged out...
The server is restarting. Any change will be lost.
 

Actor : Infusion Order Programmer

Actor Details Last changed 10/25/08 6:00:00 AM by Unknown

117
IOP
Infusion Order Programmer
The Infusion Order Programmer (IOP) actor sends the information comprising an order to the Infusion Order Consumer (IOC). The mechanism by which the IOP obtains the order information is outside the scope of this profile.
Id
Keyword
Name
Description
Status
Action
229 PIV Point-of-Care Infusion Verification The Point-of-Care Infusion Verification profile supports the electronic transfer of infusion parameters from a Barcode Point of Care (BPOC) system, also known as a Bar Code Medication Administration (BCMA) system, to an infusion pump. This capability will reduce errors by eliminating keystroke errors and by increasing the use of automatic dosage checking facilitated by onboard drug libraries. In addition to the reduction of medication administration errors, this integration may also increase caregiver productivity and provide more contextual information regarding infusion data. Final Text
84 PIV2009 DEPRECATED: 2009 Point-of-Care Infusion Verification This profile entry represents the structure of actors and options in the PIV profile as published in 2009 and tested at NA2010. The documentation was updated in 2010, and the new profile entry, PIV, represents the updated structure. Deprecated
Integration profile
Integration Profile Option
TF Reference
Specification
PIV - Point-of-Care Infusion VerificationNONE - None
PIV2009 - DEPRECATED: 2009 Point-of-Care Infusion VerificationNONE - None
Id
Integration profile
Transaction
Optionality
Specification
1638PIV - Point-of-Care Infusion VerificationPCD-3 - Communicate Infusion OrderRequired
1029PIV2009 - DEPRECATED: 2009 Point-of-Care Infusion VerificationPCD-3 - Communicate Infusion OrderRequired
1033PIV2009 - DEPRECATED: 2009 Point-of-Care Infusion VerificationITI-1 - Maintain TimeRequired
Id
Keyword
Name
Description
TF Reference
Status
Specification
Action
43 ITI-1 Maintain Time NTP transactions used to maintain time synchronization. Final Text
170 PCD-3 Communicate Infusion Order This transaction contains the information from the Infusion Order Placer, such as caregiver, patient, and pump identification, medication, volume, and rate, for the infusion being programmed. Final Text
Assertion Id
Description
PCD-Vol2-001 OBX-3 shall be expressed as an HL7 Coded Element With Exceptions (CWE) data type
PCD-Vol2-002 OBX-4 shall be expressed as the containment level of a particular item expressed in OBX-3
PCD-Vol2-003 Ordinal numbers in OBX-4 are not normative for a given parameter and may vary between implementations. They shall be unique within a given containment, however, numbers may change between messages.
PCD-Vol2-004 Source for nomenclature codes is IEEE 11073-10101 current version. Additional codes not yet standardized are contained in the RTMMS
PCD-Vol2-005 Periodic versus aperiodic data shall be distinguished by the IEEE 11073 Metric Access code in OBX-17
PCD-Vol2-006 The value in MSH-2 Encoding Characters shall be ^~\&
PCD-Vol2-007 MSH-3 Sending Application shall uniquely identify the software application implementing the actor sending the message
PCD-Vol2-008 If MSH-4 Sending Facility is populated, the first component shall identify the organizational entity responsible for sending the message, the second component if present shall identify the Universal ID of the organizational entity responsible for the sender of the message, the third component if present shall identify the Universal ID Type
PCD-Vol2-009 If MSH-5 Receiving Application is populated, the first component shall identify the organizational entity responsible for receiving the message, the second component if present shall identify the Universal ID of the organizational entity responsible for the sender of the message, the third component if present shall identify the Universal ID Type.
PCD-Vol2-010 If MSH-6 Receiving Facility is populated, the first component shall identify the organizational entity responsible for the receiving facility, the second component if present shall identify the Universal ID of the organizational entity responsible for the sender of the message, the third component if present shall identify the Universal ID Type
PCD-Vol2-011 In MSH-7 Date/Time of Message time zone shall be included in the field content
PCD-Vol2-012 In field MSH-11 Processing ID, the first component shall be present and be a value based upon HL7 Table 0103. The second component if present shall be a value based upon HL7 Table 0207.
PCD-Vol2-013 Field MSH-12 Version ID shall contain 2.6
PCD-Vol2-014 If MSH-17 County Code is present it shall contain a three Character alphabetic value from ISO 3166
PCD-Vol2-015 For MSH-18 Character Set, if the character set is ASCII then the field can be empty, or shall contain the value ASCII. If the character set is other than ASCII the field shall contain a value from HL7 Table 0211
PCD-Vol2-016 For MSH-19 Principal Language of Message if the field is empty then en^English^ISO639 is assumed. If present the value shall be from ISO 639.
PCD-Vol2-017 If PID-13 Phone Number - Home is present the field is constrained to a maximum of two repetitions to allow for a phone number and an e-mail address.
PCD-Vol2-018 If PID-15 Primary Language is populated the value shall be from ISO 639.
PCD-Vol2-020 In field OBR-2 Placer Order Number the first component shall be populated with the Entity Identifier (EI-1). If the third and fourth components are populated with the Universal ID (EI-3) and the Universal ID type (EI-4) then the second component namespace ID (EI-2) is not required to be present else it shall be required to be present.
PCD-Vol2-021 For field OBR-3 Filler Order Number the Universal ID (EI-3) and Universal ID Type (EI-4) components shall be populated.