Send Batch Wrapper - tabular view
No Current Link To VocabularyCoded With ExtensionsCoded No ExtensionsMCCI_IN200001UK02 | ||||||||||
BatchRequest |
The Send Batch wrapper forms the outer wrapper for a batch of message interactions. |
|||||||||
Used by: | ||||||||||
[1..1] id (II) |
A unique identifier for this batch. The Identifier Global datatype flavour is used to carry this information as follows:
This batch identifier is used to match a batch of interactions with one or more batch responses. It shall be echoed in the TargetBatch.id attribute present in the batch application acknowledgement wrapper of one or more batch responses responding to this batch. |
|||||||||
[1..1] creationTime (TS) |
The date and time that the sending system created the batch message. |
|||||||||
[1..1] transmissionQuantity (INT) |
A count of individual message interactions contained within this batch message. |
|||||||||
[1..1] versionCode (CS {CNE:HL7StandardVersionCode } ) |
A code which identifies the version of the NPfIT Message Implementation Manual that describes the HL7 version 3 standard used to format the batch message. The Coded Only datatype flavour is used to carry this information as follows:
|
|||||||||
[1..1] interactionId (II) |
The fixed value interaction identifier that identifies a Send Batch interchange. The Identifier External datatype flavour is used to carry this information as follows:
|
|||||||||
[1..1] communicationFunctionRcv (CommunicationFunctionRcv) |
Identifying information about the system receiving the message. |
|||||||||
[1..1] communicationFunctionSnd (CommunicationFunctionSnd) |
Identifying information about the system sending the message. |
|||||||||
[1..*] manifestItem (ManifestItem) |
A class which will occur once for each message
interaction in the batch.
|
|||||||||
[1..1] batchSequenceNo (BatchSequenceNo) |
A class carrying the sequence number of the batch
message within the sequence of batch messages relating
to a single business process.
|
|||||||||
[1..1] batchControlActEvent (BatchControlActEvent) |
A batch Control Act.
|
|||||||||
CommunicationFunctionRcv |
Details about the receiving system. |
|||||||||
Used by: BatchRequest, | ||||||||||
[1..1] typeCode (CS {CNE:RCV } ) { Fixed="RCV " } |
Indicates that the communication function being served is the receiver.
|
|||||||||
[1..1] device (Device) |
Identifying information about the receiving device. |
|||||||||
CommunicationFunctionSnd |
Details about the sending system. |
|||||||||
Used by: BatchRequest, | ||||||||||
[1..1] typeCode (CS {CNE:SND } ) { Fixed="SND " } |
Indicates that the communication function being served is the sender.
|
|||||||||
[1..1] device (Device) |
Identifying information about the sending device. |
|||||||||
Device |
The Device class represents the sender and
receiver.
|
|||||||||
Used by: CommunicationFunctionRcv,CommunicationFunctionSnd, | ||||||||||
[1..1] classCode (CS {CNE:DEV } ) { Fixed="DEV " } |
Indicates that the entity is a device.
|
|||||||||
[1..1] determinerCode (CS {CNE:INSTANCE } ) { Fixed="INSTANCE " } |
Indicates that the entity is a single instance.
|
|||||||||
[1..*] id (SET<II>) |
A single unique identifier of the accredited system that represents the party who is either sending or receiving the batch message. The accredited system is represented by the SDS Accredited Application Instance Id held in the SDS directory as the Accredited System Identifier. This is carried in the following way:
A set of ids allows more than one address identifying the party to be present. This requirement does not exist at present but may be identified in the future. |
|||||||||
[0..1] agencyFor (Agent) |
An agent role linking device and organisation. |
|||||||||
Agent |
An agent linking device and organisation. |
|||||||||
Used by: Device, | ||||||||||
[1..1] classCode (CS {CNE:AGNT } ) { Fixed="AGNT " } |
Indicates that the role is that of an agent.
|
|||||||||
[0..1] representedOrganization (Organization) |
Identifying information about the organisation.
|
|||||||||
Organization |
The organisation of the sender or receiver of the batch message. N.B. Domain specific guidance will be given describing the population of this construct in a future MIM. |
|||||||||
Used by: Agent, | ||||||||||
[1..1] classCode (CS {CNE:ENT } ) { Fixed="ENT " } |
Indicates that this is an organisation
|
|||||||||
[1..1] determinerCode (CS {CNE:INSTANCE } ) { Fixed="INSTANCE " } |
Indicates that the entity is a single instance.
|
|||||||||
[1..1] id (II) |
An SDS identifier that uniquely identifies the organisation of the intended recipient. This is carried in the following way:
|
|||||||||
[1..1] scopedRole1 [CMET: UKCT_MT120301UK02] |
NPfIT CMET identifying an Organization fulfilling a specific role. Full details of the organization are available from SDS. Details of the scoping organization are either not required or available from SDS. In this context the optional CMET identifies an SDS workgroup id as the recipient of the message. The only attribute that may be populated in this context is UKCT_MT120501UK03.OrganizationSDS.id as follows:
|
|||||||||
[1..1] scopedRole2 [CMET: UKCT_MT120501UK03] |
NPfIT CMET identifying a person fulfilling a specific role. Full details of the person and role profile are available from SDS. In this context the person is the named intended recipient of the message who shall be identified by an SDS Role Profile Id and an SDS User Id. |
|||||||||
ManifestItem |
A class carrying a set of values relating to a specific
message interaction present in the batch message.
Typically this class will be repeated for each message
interaction.
|
|||||||||
Used by: BatchRequest, | ||||||||||
[1..1] payloadId (II) |
The unique identifier for a specific message
interaction contained within the batch.
The Identifier Global datatype flavour is used to carry this information as follows:
|
|||||||||
[1..1] manifestValue (ManifestValue) |
A value relating to the message interaction identified
in payloadId.
|
|||||||||
BatchSequenceNo |
A parameter carrying a batch sequence number attribute. The batch sequence number (BSN) is managed by the sender of a batch message. The BSN is a mechanism for describing the order in which batch messages (either request or response) are sent. This mechanism is used where a business process at the sender generates multiple batch requests or responses. BSNs must be unique within a concatenation of the ebXML ConversationId and the Accredited System Identifier carried in BatchRequest.communicationFunctionSnd.device.id. This allows both the sender of the request and the sender of the response to manage sequencing independently. The BSN will allow the receiver to physically order the in-going interactions for further processing; thus preserving message order. Message ordering is not mandatory behaviour it is the responsibility of the receiver to determine whether it is required. The BSN can assist the receiver in determining missing batch messages within a sequence. A missing batch message is determined at the receiver by analysing BSNs, and looking for gaps. However, the BSN does not aid the receiver in identifying a lost last Send Batch message. Hence, it is the responsibility of the sender to determine that batch requests have gone missing and have not been processed by the receiver. Application specific behaviour is required to recover from a missing interaction. Due to the behavioural characteristics of batching, the responses to the individual messages in a request batch interaction can be sent in more than one response interaction. For correlation purposes, the BSN of the batch request interaction is provided in the batch response in an AttentionLine item for an individual message response. |
|||||||||
Used by: BatchRequest, | ||||||||||
[1..1] value (II) |
The batch sequence number will be carried in an identifier using the Identifier External datatype flavour as follows:
The sequence number shall start at 0 for the first send batch message in a related sequence of batch messages and increment by 1 for each subsequent batch message. The maximum number is 99999999. If the maximum is reached, the sender must re-start at 0. |
|||||||||
BatchControlActEvent |
A batch Control Act which is mandatory and occurs once within each batch. It allows those participations that are common to all interactions in a batch, author and author1, to be carried once only. |
|||||||||
Used by: BatchRequest, | ||||||||||
[1..1] classCode (CS {CNE:CACT } ) { Fixed="CACT " } |
Indicates that this is Control Act.
|
|||||||||
[1..1] moodCode (CS {CNE:EVN } ) { Fixed="EVN " } |
Indicates that the control act mood is an event.
|
|||||||||
[1..2] author1 | ||||||||||
[1..1] typeCode (CS {CNE:AUT } ) { Fixed="AUT " } | ||||||||||
[1..1] agent [CMET: UKCT_MT121001UK01] | ||||||||||
[0..1] author | ||||||||||
[1..1] typeCode (CS {CNE:AUT } ) { Fixed="AUT " } | ||||||||||
[1..1] agent [CMET: UKCT_MT120901UK01] | ||||||||||
[1..*] message (Message) |
A link to one or more message interactions contained
within the batch.
|
|||||||||
ManifestValue |
A unique identifier relating to a single message
interaction contained in the batch.
In this instance the batch response mandates the inclusion of a single identifier per message interaction:
|
|||||||||
Used by: ManifestItem, | ||||||||||
[1..1] manifestItemKey (CV) ({CNE:ManifestItemType}) |
A keyword identifying the type of identifier.
Any of the CodedValue datatype flavours can be used to carry this information as follows:
There shall be one fixed keyword value available in this instance:
|
|||||||||
[1..1] manifestItemValue (II) |
The value pertaining to the keyword carried in
manifestItemKey.
Where the keyword is "interaction", the value shall be the interaction identifier of the interaction identified by payloadId. The Identifier External datatype flavour is used to carry this information as follows:
|
|||||||||
Message |
The entry point into each interaction within the batch.
|
|||||||||
Used by: BatchControlActEvent, | ||||||||||