PSIS Summary Query Response - tabular view

No Current Link To VocabularyCoded With ExtensionsCoded No Extensions

queryResponseSummary  

queryResponseSummary

A header for the PSIS Query Response.

queryResponseSummary is the root element of the response for a "get summary" request.

 It will contain zero-to-many event items.


Used by:

[1..1] recordTarget

A Participation that idicates the Service User that the Query Response relates to.


[1..1] patient (Patient)

Link to the Patient who is the Record Target


[1..1] id (II)

The Patient's NHS number.  The Identifier External datatype flavour is used to carry this information as follows:-

  • The root attribute will contain the NHS number OID
  • The extension attribute will contain the NHS number itself.


[1..*] eventItem

A container for the clinical statement to be returned..

Multiple statements can be returned as a part of a single get "summary" request.



[1..1] eventItemID
eventItemID is the unique ID of the clinical statement.

 It's of type II-IG (Identifier Global) so it has a root attribute that is the ID, and no other attributes.

[1..1] persistenceDate
The date at which the event was entered into PSIS, in yyyyMMddhhmmss format. This does not necessarily correspond to the date on which the event occurred.

This is an HL7 timestamp field, which can have a number of different formats, but PSIS will only use the form that has a value attribute containing a date in the format yyyyMMddhhmmss.


[1..1] eventItemStatus

The current status of the event item, inherited from the status of the event.  

See the further comments below.
   



[1..1] eventItemType
The type of event item - such as "OBS" for Observation, or "SUP" for Supply. This doesn't necessarily correspond to the element name of the event item (like "Observation").
       
The code is extracted from the classCode of the clinical statement.

It's of type CS (Coded Simple), so it has a code attribute, that contains the type, and no other attributes.
 


[1..1] CREType
The CRE type of the clinical statement.

(see /Vocabulary/CREType.htm in the MiM for the list of valid CRE types)

This is of type CV (Coded Value - Coded with Code System) so it will have a codeSystem attribute that will always contain
 "2.16.840.1.113883.2.1.3.2.4.17.56" and a code attribute that holds the CRE type.
   


[1..1] eventID
eventID is the unique ID of the event.

It's of type II-IG (Identifier Global) so it has a root attribute that is the ID, and no other attributes.


[1..1] hl7Data
This is clinical statement.  It is in the exact same XML format as sent as a part of the originating message.