...
- OPENSHR-31: Entries within a document SHALL indicate their conformance to a template by appending <templateId> elements to the entry's clinical statement identifying the templates to which the entry conforms. Entries which do not carry a <templateId> SHALL NOT be imported by the SHR.
- OPENSHR-31: Entries within a document SHALL contain an <id> element containing a globally unique identifier (OID + ID) pointing to the discrete data record which was used to generate the data. This <id> will represent a series of unchanging unique identifiers for the data and SHALL always be conveyed consistently across document instances.
- OPENSHR-31.1: The OID portion of the identifier SHALL contain an OID which identifies the source system and type of data (ex: If System A with OID=1.2.3.4.5 conveys an observation from it's observations table with primary key "4" it would produce id with OID=1.2.3.4.5.6 (System A + Observations) and ID="4").
- OPENSHR-31.2: If the consumer is not the source of the information (i.e. it imported the information from another source such as another CDA), it SHALL use the ID it received from the source and MAY append additional <id> elements representing its local identifierNOT convey this information in the CDA. The SHR SHALL NOT process entries for which it already has recorded the unique id (i.e. the SHR will ignore return an error if it encounters entries carrying an ID which it already has information). If the consumer wishes to update the data conveyed in the entry, it SHALL do this using the mechanism identified in OPENSHR-33.
- OPENSHR-32: Consumer systems SHALL NOT convey entries within the clinical document for it does no possess discrete data (ex. do not produce allergy entries if no allergies exist in the source system).
- OPENSHR-33: All entries within a clinical document represent an amendment to existing data within the shared health record (i.e. all entries are considered new data), if a consumer wishes to convey that an entry is intended to replace existing data (ex: updating erroneous data) it SHALL indicate this by appending <reference> elements to the clinical statement.
- OPENSHR-33.1: The <reference> element SHALL carry @typeCode of RPLC indicating a replacement
- OPENSHR-33.2: The <reference> element SHALL contain an <externalAct> element having an <id> element matching the unchanging global identifier (OID + ID) of the entry to be replaced.
...