Incident Id Proposal

Folks,

For my AI from today's call:

Proposal:

Include a new top level, optional element in Symptom.

Field:		IncidentId
Type:		anyURI
Properties:	Optional, Unique (to the incident in question), Immutable
Description:	This optional identifier may be included in a Symptom to assist consumers in associating this symptom with others. Care should be taken to establish basic mechanisms to ensure that it is unique to an incident.

Schema:	<IncidentID>xsd:anyURI</IncidentID>

Notes: 

	- We could use a more generic term like CoordinationID.
	- We might consider saying how this might be passed (in a standard way) to Practitioners in the prescription.

Just a thought.
	
Take care:

    Dr. David Snelling < David . Snelling . UK . Fujitsu . com >
    Fujitsu Laboratories of Europe Limited
    Hayes Park Central
    Hayes End Road
    Hayes, Middlesex  UB4 8FE
    Reg. No. 4153469

    +44-7590-293439 (Mobile)


______________________________________________________________________
                                        
 Fujitsu Laboratories of Europe Limited
 Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE
 Registered No. 4153469
 
 This e-mail and any attachments are for the sole use of addressee(s) and
 may contain information which is privileged and confidential. Unauthorised
 use or copying for disclosure is strictly prohibited. The fact that this
 e-mail has been scanned by Trendmicro Interscan does not guarantee that 
 it has not been intercepted or amended nor that it is virus-free.