HL7 v24

En qué nivel del modelo ISO/OSI se ubica HL7 v2.x. Elija una opción. Transporte. Aplicación. Red. Enlace. Sesión.

De las siguientes opciones, elija la mejor que defina a HL7 v 2.x. Una base de datos. Un ruteador para mensajes de intercambio de información clínica. Una especificación de arquitectura para sistemas de salud. Una aplicación de mensajería. Un protocolo para intercambio de información clínica.

El estándar asume un entorno de comunicaciones... Soportado por ANSI. Basado en TCP/IP. De código libre. Que asegure la transmisión sin errores.

¿Cuál de estos No es considerado actualmente un evento disparador de mensajes para HL7 v 2.x?. Se generó un informe radiológico. Se rompió la impresora en el sector 18. Paciente admitido en guardia médica. Se otorgó un turno a un paciente ambulatorio.

¿En qué parte del mensaje se identifica el tipo y el evento disparador? Debe elegir una sola opción. Es imposible dentro del mensaje. Debe hacerse por fuera del. Solamente en el sector de encabezado de episodios. En el segmento MSH. En el segmento PID.

Elija una opción que responda mejor a la consigna: ¿Cuántos segmentos DG1 pueden ir en el mensaje según este fragmento de definición de mensaje abstracto?. Entre 0 y N. 2. Entre 1 y N. Entre 1 y 5.

¿Cuál de estas afirmaciones es falsa?. Los segmentos no pueden ser opcionales. Los segmentos pueden ser repetitivos. Los segmentos se identifican por un código único de tres caracteres únicos. Los segmentos son agrupaciones de campos.

El único delimitador NO modificable es: El separador de subcomponente. El separador de campo. El separador de segmento. El separador de componente.

De las siguientes opciones elija una sola que complete la oración: La secuencia de los campos dentro de un segmento... No puede modificarse y está definida en la tabla de definición de cada segmento. Depende del separador de campos. Se especifica en el segmento MSH. Es opcional. Los campos podrían estar en otro orden y sería exactamente lo mismo.

Elija una sola opción ,de las listadas a continuación, que indique : Cómo es la longitud de cada campo o atributo en la tabla de definición de segmentos . Es la mínima posible. Si se envían datos de longitud menor puede haber inconvenientes con los parseadores de mensajes. Es la máxima posible. No hay inconveniente si se envían datos de menor longitud. Es fija. Deben enviarse mensajes con campos que midan exactamente esa cantidad de bytes. Se especifica en el segmento MSH.

One of the options below is NOT an HL7 trigger event. ¿Which one?. Patient admitted. Lab result of blood glucose is validated. Printer in emergency room ran out of paper. Patient discharged.

The HL7 V2.4 standard assumes for the underlying communications infrastructure I. Character set conversion II. Certain design of the receiving system III. Certain subsequent action of the system receiving data IV. Unlimited message length V. Error free transmission. Only I. Only II. I and II. I, IV and V. V. III, I and II.

With a positive accept acknowledge in enhanced processing mode the receiving system. Saves the message to a log file. Validates the data in the message. Commits the data in the message to the database. Commits the message to safe storage.

In HL7 v 2.4 a segment is defined as. A logical grouping of data fields. A logical grouping of messages. A logical grouping of components.

In HL7 v 2.4 a message is comprised of. A group of sub-components in a defined order. A group of unordered segments. A group of fields in a defined order. A group of components in a defined order. A group of segments in a defined order.

Messages types and trigger events beginning with the letter ’Z’ are. Reserved for future releases. Forbidden. Reserved for locally defined messages.

Relationship between message types and trigger events is. one to one. one to many. many to one.

Segments of a message may be. Restrained or optative. Required or Repetitive. Required or optional. Optional or Repetitive.

An HL7 field is. represented depending on the application configuration. a defined length 8 bit ASCII code. a string of characters.

When the receiving application has to update a record, the difference between null and not present fields is. if a field is not present, it will be changed to null. if a field is not present, it will not be changed. if a field is valued as 'null' it will not be changed.

Field optionality defines. whether a component is required or optional in a field. whether a sub-component is required or conditional in a component. whether a field is required, optional or conditional in a segment. when a field should be sent depending on other fields values.

The HL7 V 2.4 segment terminator I. Is hex 0D (CR) II. Should be specified in the MSH segment III. Cannot be changed by implementers IV. Should be defined in each site negotiation. II and IV. I and III. I and IV. II and I.

In the message below, the component separator is: MSH|?~\&|... ~. &. \. ?. |.

Escape character can be used in. Datatypes ST , TX, FT. Datatypes NM, FT, and ST. only NM datatype. only TX,ST datatypes. only FT datatype. Datatypes ED and TX only.

Assigning authorities are I. defined by a local country HL7 affiliate. II. globally defined by HL7. III. unique across a given HL7 implementation. IV. the unique identifiers of a systems or organizations that creates data. III and IV. I and III. I and IV. II and I.

The CWE data type should be used. For coded fields that are repetitive. Where is permissible to send text for items not yet part of an approved value set. For coded fields that are required. For charges within exclusions.

Data type ED can be used to send. Reference pointers between applications. Current status of patient record editing between applications. Base64 encoded data between applications. Patient names and addresses between applications.

The entity identifier datatype (EI). Defines a given entity within a series of GUIDs. Is appropiate for machine or software generated identifiers. Defines an XML structure with a series of entity identifiers.

One of these is not a valid HL7 Universal Id Type value. XSD. x400. GUID. x500. UUID. DNS. HL7.

Datatype ID is for. coded values for user defined tables. storing message ids for queueing. coded values for HL7 defined tables. storing patient identifications across multiple sites.

This string ‘99.50^USD’ is a valid field value for. ST datatype. MO datatype. TX datatype.

One of this is not a valid NM datatype field value. -45.23. 45.23. 4.234514243321. 45/2.

Which of the following segments contains the field “SendingApplication”?. MSH. ERR. DSC. NTE.

What is the specified maximum length for the CX datatype?. 290. 1024. none. 6K. 64K.

The segment FTS contains which of the following fields. File batch count. File sending facility. File receiving application. File control id. File name/id.

If the default encoding character are used, and a text field is being encoded which contains the string “LEVEL 2 PATIENT | AGE=42 Years | SEX=Male | SMOKE&DRINK = YES|”, which of the following statements is true: I. There is no need to escape the text. It must be sent as is. II. The text must be serialized and encoded using the Base64 algorithm. III. The encoded text will include the string ‘\S\’ and the string ‘\A\’ IV. There is no way of sending this string using HL7 V2.4 V. The encoded text will include the string ‘\F\’ and the string ‘\T\’. Only I. II. and V. II. and III. Only V. Only IV.

Given the following HL7 field of data type NA (Numeric Array) |8^7^^5~4^3^2^1| which one of the following statements is TRUE?. The sixth component of the first repetition is not present. The third component of the first repetition is not present. This is not a valid value for a NA data type field. The second repetition has a not present component.

Which of the following statements about the HL7 LEN column in segment attribute tables is NOT TRUE?. I. Is the maximum number of characters that one occurrence of the data field may occupy II. Is normative, and it cannot be changed on a site negotiation III. Shall be a number larger than 250 bytes IV. If the number 65536 appears, is a convention for ‘very large number’. Only I. II. and IV. II. and III. Only III.

Given the following abstract message definition: MSH Message Header PID Patient [ZPE Patient Extra Demographics] { ZEP Patient Epilepsy Episode Data {[ZEM Patient Epilepsy Episode Medication Data]} } Which of the following ordered segments in a message would be ILLEGAL?. MSH PID ZPE ZEP ZEM ZEM ZEM. MSH PID ZEP ZEP. MSH PID ZPE ZEP ZEP ZEM. MSH PID ZPE ZPE ZEP.

Which of the following is not a component of the RP (reference pointer) data type. Pointer. Application ID. Type of data. Subtype. None of the above. All of the above are components of the RP data type.

Data type XCN is well suited for. Representing addresses. Representing organizations. Representing Id.s and names for persons within an organization. Representing lab results. None of the above.

What acknowledgement code should a system return as an accept acknowledgement if the message cannot be accepted because of an error in the message type field and enhanced processing mode is used?. CX. CD. CE. CR. AR.

Which MSH fields values must be verified in order to define if a message is in original or enhanced processing mode?. MSH-9 and MSH-10. MSH-3 and MSH-4. MSH-15 and MSH-16. MSH-5 and MSH-15. MSH-16 and MSH-4.

Which segments must be added to the first message in order to split a segment between multiple messages due to its length?. FHS and FTS. ADD and Empty DSC. Empty ADD and DSC. ADD and DSC.

Which is the relationship between MSH-14 Continuation Pointer and DSC-1 Continuation Pointer Value?. MSH-14 of the split message must be equal to DSC-1 of its continuation. DSC-1 of the split message must be equal to MSH-14 of its continuation. There is no relationship at all. DSC-1 of the split message must be equal to (MSH-14 of its continuation + 1) in order to achieve proper message sequencing.

When should the receiver system issue an Application Level Accept message if receiving a fragmented message using the continuation protocol in enhanced mode?. For each fragment. There is no need for an Application Level Accept Message in this scenario. Only for the last fragment. It depends on a site negotiation.

What should the receiver system do when receiving a 0 (zero) in the sequence number field?. It’s an error and must responded with an AR acknowledgement code. It’s a confirmation from the sending system that the last message in sequence was sent, so the receiver must not respond to this message. It depends on a site negotiation. Respond with an MSA with a sequence number equal to -1 if the value doesn’t exists.

When a field definition involves the use of subcomponents, which of the following rules are NOT used: I. If more than one subcomponent is included they are separated by the subcomponent separator II. Subcomponents present but null are represented by the "" characters III. Subcomponents not present are represented by the "" characters IV. Subcomponents with null values at the end of a component need not be represented. I. and II. II. and III. I. and IV. III. and IV.

What does a repeat delimiter means within a TX (text) field?. It’s invalid: the TX data type does not allow repetitions. A series of repeating lines to be displayed, as if CR/LF were inserted. Several different values for the field. It depends on a site negotiation.

Which of these values are valid for a TS (Timestamp) field? I. |20040201203000+0100| II. |20040306| III. |200412023000| IV. |200402| V. |20040210201|. II. and III. I. and IV. I. , II. and IV. III. and V. All of them are valid.

What does this value for a RCD (row column definition) data type field means: |@PID.5.2^ST^35|. It’s invalid: this is not a valid value for an RCD data type field. Defines a column containing the value of the ‘given name’ component of PID-5 expressed as a ST data type with a maximum length of 35. Defines a column that contains up to five repetitions of field 2 of PID (Patient Id). The receiving system must query the user for the last name of the patient.

What data type is component ‘Assigning Facility’ of data type PPN (Performing person time stamp). HD (Hierachic Designator). XON (Extended Composite name and Id number for organizations). XPN (Extended Person name). EI (Entity Identifier).

Which components are mandatory when valuing fields of PL (Patient Location) data type?. All of them. Room, Bed and Facility. Room, Floor and Location Status. Person Location Type. None of them, depends on site needs.

Which of these values is not valid for CWE (coded with exceptions) status?. U Unknown. UASK Asked but Unknown. NAV Not available. AVE Available elsewhere. NASK Not asked.

Which of these values is not valid for a field with CNE data type?. |NM|. |^Decimal Range|. |NM^Numeric^HL70125^NUM^Number^99LAB^2.3.1^1.1^Decim al|. |NM^^^NUM^Number^99LAB^^|.

What is an external table?. A set of values defined and published by HL7. A set of values that are locally or site-defined. A set of coded values defined and published by another standards organization. A set of entity identifiers generated by an external application which has to be exchanged by special HL7 messages.

What does an integer mean in the RP/# column of the field definition table?. The minimum quantity of repetitions possible for the field. The exact quantity of repetitions required for the field. It’s there for backward compatibility only. The maximum quantity of repetitions possible for the field.

If a sending system has to send two new diagnosis for a patient that already has a previously transmitted one, and the site is working in snapshot mode for updating repeating segments, what does the application need to send to a receiving system?. The two new diagnosis segments and the old one. Only the two new diagnosis segments. This issue cannot be solved in this version of the standard. The sending system must send first a message to delete the previous diagnosis, and in another message, the three diagnosis.