e-Laboratory observation report message
other Linktoparent
Submitted date | Last Update Date | Version |
---|
Project Proposal Status | Project Page | |||||||
---|---|---|---|---|---|---|---|---|
|
|
|
|
|
e-Laboratory observation report message |
Project Purpose
Text Area | ||||
---|---|---|---|---|
| ||||
The project's purpose is to create Business Process Models and Business Class Diagrams for documenting the business scenarios and business transactions involved in the electronic exchange of the agricultural laboratory observations between a laboratory and its partners. |
Project Scope
Text Area | ||||
---|---|---|---|---|
| ||||
The objective of this project is to standardize the Business Processes, the Business Transactions and the Information Entities of the electronic exchange of the laboratory observation report between a laboratory and its partners. This project will describe the business processes for the electronic exchange of the laboratory observation report between a laboratory and its partners. The observation report contains information about the measurements and observations performed in a laboratory on one or more samples of crops, live animals, post mortem material, animal products, plant products, soil, animal feed, silage, soil and so on. The laboratory observation report is used by several business partners to provide quality and health information about agricultural commodities and products, about plant health and animal health and abiotic conditions (soil and water). The business partners are active in trade, transport, food processing, animal feed, farming, agri consultancy, finance and insurance. |
Project Deliverables
Text Area | ||||
---|---|---|---|---|
| ||||
The project deliverables are - A catalogue of Business Process Models using UMM/UML covering the e-laboratory observation report exchange - A guide for users which enables them to select the model appropriate to their needs - The class diagrams of the business transactions for the creation of the XML message - The BRS and RSM documents - XML schema to support the business transactions |
Exit Criteria
Text Area | ||||
---|---|---|---|---|
| ||||
TBD |
Project Team Membership and Required Functional Expertise
Text Area | ||||
---|---|---|---|---|
| ||||
Membership is open to experts with broad knowledge in the area of agriculture, horticulture, crop farming, animal farming, livestock, animal and plant health, laboratory observation and reporting and EDI and their e-business operation, and the functions of UN/CEFACT and its groups. In addition, Heads of Delegations may invite technical experts from their constituency to participate in the work. Experts are expected to contribute to the work based solely on their expertise and to comply with the UN/CEFACT Code of Ethics. |
Head of Delegation Support
Text Area | ||||
---|---|---|---|---|
| ||||
The project is supported by The Netherlands, France, and Italy. |
Geographical Focus
Text Area | ||||
---|---|---|---|---|
| ||||
The geographical focus is global. |
Initial Contributions
Text Area | ||||
---|---|---|---|---|
| ||||
ISO and HL7 standards and LOINC will be considered. The following working documents drafted by a working group which was organized in the Netherlands to facilitate this project, could be submitted as part of this proposal. It is understood that these contributions are only for consideration by the project team and that other participants may submit additional contributions in order to ensure that as much information as possible is obtained from those with expertise and a material interest in the project. |
Resource Requirements
Text Area | ||||
---|---|---|---|---|
| ||||
Resources required are business experts with a broad knowledge of electronic data exchange and EDI in any region or country. Modeling expertise is also required in the project. Note: The project does not require any additional resources from the UN/ECE secretariat. |
Project Leadership
Text Area | ||||
---|---|---|---|---|
| ||||
Project Leader: Frans VAN DIEPEN Editors: Henk ZWINKELS |
Milestones
DELIVERABLE NAME | Project Inception | Expected Completion Date | Requirements Gathering | Expected Completion Date | Draft Development | Expected Completion Date | Public Review | Expected Completion Date | Project Exit | Expected Completion Date | Publication | Expected Completion Date | Maintenance | Expected Completion Date | |||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project Proposal Files
Attachments | ||
---|---|---|
|