Complete Details Response - tabular view

No Current Link To VocabularyCoded With Extensions
REPC_RM100000UK30
CompleteLRList

All Legitimate Relationship records that meet the criteria specified in the Details Request message.

Used by:
[1..1] classCode (CS {CNE:LIST} ){ Fixed="LIST " }

Indicates that this is a List.

  • Fixed Value: "LIST"

The classCode is carried as an attribute of the LRList 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 LRList element.

[1..1] recordTarget
The information held in the LR record is about specified patient. The patient does not have any direct input into the record itself
[1..1] typeCode (CS {CNE:RCT} ){ Fixed="RCT " }

Indicates that the role is the patient of the request.

  • Fixed value: "RCT"

The typeCode is carried as an attribute of the recordTarget element.

[1..1] patient (Patient)

Details about the patient.

[0..*] component
[1..1] typeCode (CS {CNE:COMP} ){ Fixed="COMP " }

Indicates that this is a component.

  • Fixed value: "COMP"

The typeCode is carried as an attribute of the component element.

[1..1] completeDetails (CompleteDetails)

Link to LR complete details

Patient

Details of Patient who is the record target.

Used by: CompleteLRList
[1..1] classCode (CS {CNE:PAT} ){ Fixed="PAT " }

Indicates that the role is that of a patient.

  • Fixed value "PAT" Patient
[1..1] id (II)

The NHS number that identifies the patient.

NHS numbers are composed of ten numerics.

  • The root element identifies the  NHS patient numbering scheme represented by OID 2.16.840.1.113883.2.1.4.1
  • the extension contains the actual identifier.
CompleteDetails
A heading linking all details pertaining to a LR record from the list.
Used by: CompleteLRList
[1..1] classCode (CS {CNE:PCPR} ){ Fixed="PCPR " }

Indicates that this is Patient Care Provision.

  • Fixed Value: "PCPR"

The classCode is carried as an attribute of the CompleteDetails 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 CompleteDetails element.

[1..1] id (II)

Unique Identifier denoting the LR Record.

A Identifier code is carried in the following way:

  • The root attribute shall contain an OID with the value 2.16.840.1.113883.2.1.3.2.4.18.3  
  • the Extension attribute shall contain the LR record id.
[0..1] code (CV {CNE:LRCurrentStatus} )

A Code identifying the current status of the legitimate relationship 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 the LRCurrentStatus vocabulary.
  • An OID identifying the coding system from which the code is derived.

Example: 02 - inactive

[1..1] effectiveTime (IVL<TS>)

Date and Time from which the LR record is active and an optional date and time at which the Legitimate Relationship achieved its current status.

  • Format: CCYYMMDDHHMMSS to CCYYMMDDHHMMSS

A Low value (Active DT) must exist. A high value (Historic DT) may not exist.

A high sub-element cannot exist without a low sub-element., but a low sub-element may exist without a high.

The high value is present unless the Legitimate Relationship is 'active'.

NOTE: Expired relationships are not returned at all.

Example: 20041231235959 - 20050125235959

[1..1] reasonCode (CV {CNE:LRType} )

Reason for the Legitimate Relationship to exist.

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 the LRType vocabulary.
  • An OID identifying the coding system from which the code is derived.

Example: 08 - Self Claimed Relationship

[1..1] subject
A heading linking details of the parties involved in the LR record.
[1..1] typeCode (CS {CNE:SBJ} ){ Fixed="SBJ " }

Indicates that the role is either the Health Care Professional, WorkGroup or other person of the record.

  • Fixed value: "SBJ"

The typeCode is carried as an attribute of the subject element.

[1..1] role (LRinvolved)

Link to details of persons/workgroup involved in the LR.

[1..1] author
A heading linking the details of the author for a particular LR record.
[1..1] typeCode (CS {CNE:AUT} ){ Fixed="AUT " }

Indicates that the role is the author of the Create LR Request.

  • Fixed value: "AUT"

The typeCode is carried as an attribute of the author element.

[1..1] role (AuthorChoice)

Link to the Choice of author.

[0..1] component
A heading linking to additional details for this LR record.
[1..1] typeCode (CS {CNE:COMP} ){ Fixed="COMP " }

Indicates that this is a component.

  • Fixed value: "COMP"

The typeCode is carried as an attribute of the component element.

[1..1] sCDetails (SCDetails)
Details of any Status Changes to the LR Record.
[0..1] pertinentInformation
[1..1] typeCode (CS {CNE:PERT} ){ Fixed="PERT " }

Indicates pertinent information.

  • Fixed value: "PERT"

The typeCode is carried as an attribute of the pertinentinformation element.

[1..1] pertinentReasonTxt (ReasonTxt)

Additional details for LR record reason to exist.

LRinvolved

Link to person/workgroup that are involved in the LR.

Used by: CompleteDetails
[1..1] either : OtherPerson

Link to Other Person (non SDS) details.

This is only a placeholder for future use.

             ... or ... : UKCT_MT120501UK02

Full details of the workgroup. In this instance the Identifier in the OrganizationSDS entity is required. This denotes the workgroup Identifier.

  • The root element identifies the SDS Workgroup scheme represented by OID 1.2.826.0.1285.0.2.0.109
  • the extension contains the actual identifier. 

    • The Optional AGENT Class Identifier and Code may be ignored in this instance.

                 ... or ... : UKCT_MT120301UK02

    Full details for person and role profile are available on SDS.

    Both the Class of Agnt and PSN are required.

    The AGNT Class consists of an SDS identifier that uniquely identifies the Role of the Person.   This is carried in the following way:

    • The root attribute shall contain an OID with the value 1.2.826.0.1285.0.2.0.67
    • the extension attribute shall contain the SDS Role Profile ID

    The PSN Class an SDS identifier that uniquely identifies the Person.   This is carried in the following way:

    • The root attribute shall contain an OID with the value 1.2.826.0.1285.0.2.0.65
    • the extension attribute shall contain the SDS User ID
    AuthorChoice

    Details of the Choice of Author.

    Used by: CompleteDetails
    [1..1] either : UKCT_MT120701UK02

    Full details of the accredited application generated the request for the creation  and status change of the LR respectively. Details are available from SDS. The details shall be carried in the following way:-

    The root attribute shall contain an OID with the value 1.2.826.0.1285.0.2.0.107

  • the extension attribute shall contain the SDS Device ID

    • Present when the message is issued automatically by the application as a result of a business process.

    The definition of System-id for this purpose is "An individual application running upon a server. Where there are multiple (n) applications running upon a single server, then there shall be considered to be n systems.

    The Optional AgentDeviceSDS Class Identifier and Code may be ignored in this instance.

                 ... or ... : UKCT_MT120301UK02

    Full details for person and role profile are available on SDS.

    Both the Class of Agnt and PSN are required.

    The AGNT Class consists of an SDS identifier that uniquely identifies the Role of the Person.   This is carried in the following way:

    • The root attribute shall contain an OID with the value 1.2.826.0.1285.0.2.0.67
    • the extension attribute shall contain the SDS Role Profile ID

    The PSN Class an SDS identifier that uniquely identifies the Person.   This is carried in the following way:

    • The root attribute shall contain an OID with the value 1.2.826.0.1285.0.2.0.65
    • the extension attribute shall contain the SDS User ID
    SCDetails

    Details of Status Change Record for this LR.

    Used by: CompleteDetails
    [1..1] classCode (CS {CNE:ACT} ){ Fixed="ACT " }

    Indicates that this is an act.

    • Fixed value: "ACT"

    The classCode is carried as an attribute of the SCDetails 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 SCDetails element.

    [1..1] reasonCode (CV {CNE:SCReasonCode} )

    Code identifying the reason for the change in status of the legitimate relationship.

    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 the SCReasonCode  vocabulary.
    • An OID identifying the coding system from which the code is derived.

    Example: 07 - Closure of Case

    [1..1] author
    A heading linking details of the status change author for the LR record.
    [1..1] typeCode (CS {CNE:AUT} ){ Fixed="AUT " }

    Indicates that the role is the author of the Status Change Request.

    • Fixed value "AUT"

    The typeCode is carried as an attribute of the author element.

    [1..1] role (SCAuthorChoice)

    Link to Choice of Author

    ReasonTxt

    Additional Reason for LR to exist.

    Used by: CompleteDetails
    [1..1] classCode (CS {CNE:PCPR} ){ Fixed="PCPR " }

    Indicates that this is Patient Care Provision.

    • Fixed Value: "PCPR"

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

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

    Indicates that this is a request for service.

    • Fixed Value: "RQO"

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

    [0..1] text (ST)

    Free-text element to record the reason for the LR to exist.

    Free text may be included for any LRType.

    This field will be present if AccessReasonCode is OTHER.

    LR Reason Text MUST be included if it was entered at the time of the LR creation

    [0..1] reasonCode (CV {CNE:AccessReasonCode} )

    Details of the reason why this record needs to be accessed.

    Where the LRType is either codes '03', '08' or '04' then a standard reason for the access must exist.

    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 the AccessReasonCode  vocabulary.
    • An OID identifying the coding system from which the code is derived.
    OtherPerson

    Details of Other Person involved in the Legitimate Relationship.

    This is only a placeholder for future use.

    Used by: CompleteDetails, LRinvolved
    [1..1] classCode (CS {CNE:AGNT} ){ Fixed="AGNT " }

    Indicates that the role is that of an agent.

    • Fixed value: "AGNT"

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

    [1..1] id (II)

    The NHS number is use to identify this person.

    NHS numbers are composed of ten numerics.

    • The root element identifies the  NHS patient numbering scheme represented by OID 2.16.840.1.113883.2.1.4.1
    • the extension contains the actual identifier.

    Example: '1234567899'

    SCAuthorChoice

    Details of Status Change Author

    Used by: SCDetails
    [1..1] either : UKCT_MT120701UK02

    Full details of the accredited application generated the request for the creation of the LR. Details are available from SDS. The details shall be carried in the following way:-

    The root attribute shall contain an OID with the value 1.2.826.0.1285.0.2.0.107

  • the extension attribute shall contain the SDS Device ID

    • Present when the message is issued automatically by the application as a result of a business process.

    The definition of System-id for this purpose is "An individual application running upon a server. Where there are multiple (n) applications running upon a single server, then there shall be considered to be n systems.

    The Optional AgentDeviceSDS Class Identifier and Code may be ignored in this instance.

                 ... or ... : UKCT_MT120301UK02

    Full details for person and role profile are available on SDS.

    Both the Class of Agnt and PSN are required.

    The AGNT Class consists of an SDS identifier that uniquely identifies the Role of the Person.   This is carried in the following way:

    • The root attribute shall contain an OID with the value 1.2.826.0.1285.0.2.0.67
    • the extension attribute shall contain the SDS Role Profile ID

    The PSN Class an SDS identifier that uniquely identifies the Person.   This is carried in the following way:

    • The root attribute shall contain an OID with the value 1.2.826.0.1285.0.2.0.65
    • the extension attribute shall contain the SDS User ID