This wiki has undergone a migration to Confluence found Here
Batch Topic DSTU R1 Issues
Revision as of 12:30, 16 September 2006 by Rene spronk (talk | contribs)
This page documents an INM Workitem, i.e. an issue within scope of the INM Committee that either is still being discussed, or the resolution of which has not yet been included in an INM ballot.
This page contains approved changes to the MCCI Batch topic that have to be included in the upcoming DSTU Release.
- Harmonization: Transmission Inheritance
- Harmonization: Batch.contentProcessingMode
- Harmonization: add Attachment to Batch,
- Harmonization: enable Batch.profileId attribute
- Harmonization: add priorTransmission to support Transmission Sequencing
- Transmission Addressing
- Sequence Number Protocol
- Transmission.id
- Error Location
- Minimalistic full-unheritance R-MIM as per the NHS proposal prsented THU Q4/Sept2006 WGM.
From Open Transmission Wrapper Issues
- (issue resolved, needs to be documented in next release) It is the intent of the committee not to require an instance of the reference control id attribute in the initial batch transmission. (John Arnett / Tony Davey 11–0-3 Jan06 WGM THU Q4)
- (issue resolved, needs documentation) There is an element of tension between the statement that a Batch wrapper is "only a grouping of interactions for transmission purposes" and the presence of the batch.referenceControlId and batch.name. These seem to hint that a Batch is a "unit of processing". Well: is it, or isn't it?
INM out of cycle: Transmission Wrapper will be a thin grouper of transmissions only. NHS use-case for syncing databases via message-batches will be discussed separately.
- Mead Walker/Robert Hausam have come forward with use-cases for the inclusion of a time-interval of a Batch (e.g. this is a batch containing all invoices from 20050101 up to 20050201) - The comittee has commited itself to include a solution for this use case in the next publication of the MCCI domain. This has been resolved (??) by the very fact that at a later point in time we defined a Batch wrapper to be "only a grouping of interactions for transmission purposes".
