Confirm Response for Legitimate Relationship Tabular View

This response indicates the existence (or otherwise) of a LR between a patient and a User or other person and the status of the LR found.

Used by:

[1..1] classCode (CS {CNE:OBS} ){ Fixed="OBS " }

Indicates that this is an Observation.

Fixed Value: "OBS"

The classCode is carried as an attribute of the ConfirmHistory element.

[1..1] moodCode (CS {CNE:EVN} ){ Fixed="EVN " }

Indicates that this is an Event.

Fixed Value: "EVN"

The moodCode is carried as an attribute of the ConfirmHistory element.

[0..1] code (CV {CNE:LRCurrentStatus} )

A code indicating the status of the LR found..

The Coded with Code System datatype flavour is used to carry this information as follows:

The code attribute will contain a value from the list of codes in LRCurrentStatus vocabulary.
An OID identifying the coding system from which the code is derived.

If multiple legitimate relationships exist, only one will be returned: the order of priority will be 'active', 'inactive' then 'frozen'.

[0..1] effectiveTime (TS)

The date and time at which the latest Legitimate Relationship valid for the User Role Profile or other user specified in the request was established in its current state.

This date and time is not present if the status of the LR found is 'active'.

Format: YYYYMMDDHHMMSS

[1..1] value (BL)

A value stating the existence or absence of a Legitimate Relationship record.

The BL (Boolean) data type is designed to carry a 'True/False' status. Where it is essential that a value is carried, the field is set to Mandatory. Mandatory requires a value and may not carry 'Null Flavours' The BN datatype is a reserves HL7 internal datatype and must not be used.

The XML used to represent an attribute that is a Mandatory BL data type is identical to that used to represent a BN.

The false value does not denote a failed message. It means that there are no current LRs for this patient.


REPC_RM080000UK30

ConfirmHistory		This response indicates the existence (or otherwise) of a LR between a patient and a User or other person and the status of the LR found.

	Used by:

[1..1] classCode (CS {CNE:OBS} ){ Fixed="OBS " }		Indicates that this is an Observation. Fixed Value: "OBS" The classCode is carried as an attribute of the ConfirmHistory element.

[1..1] moodCode (CS {CNE:EVN} ){ Fixed="EVN " }		Indicates that this is an Event. Fixed Value: "EVN" The moodCode is carried as an attribute of the ConfirmHistory element.

[0..1] code (CV {CNE:LRCurrentStatus} )		A code indicating the status of the LR found.. The Coded with Code System datatype flavour is used to carry this information as follows: The code attribute will contain a value from the list of codes in LRCurrentStatus vocabulary. An OID identifying the coding system from which the code is derived. If multiple legitimate relationships exist, only one will be returned: the order of priority will be 'active', 'inactive' then 'frozen'.

[0..1] effectiveTime (TS)		The date and time at which the latest Legitimate Relationship valid for the User Role Profile or other user specified in the request was established in its current state. This date and time is not present if the status of the LR found is 'active'. Format: YYYYMMDDHHMMSS

[1..1] value (BL)		A value stating the existence or absence of a Legitimate Relationship record. The BL (Boolean) data type is designed to carry a 'True/False' status. Where it is essential that a value is carried, the field is set to Mandatory. Mandatory requires a value and may not carry 'Null Flavours' The BN datatype is a reserves HL7 internal datatype and must not be used. The XML used to represent an attribute that is a Mandatory BL data type is identical to that used to represent a BN. The false value does not denote a failed message. It means that there are no current LRs for this patient.

Confirm Response for Legitimate Relationship - tabular view