openEHR XML Schema Release 1.0 candidate

Super-types:	st:LOCATABLE < CONTENT_ITEM (by extension) < ENTRY (by extension) < CARE_ENTRY (by extension) < OBSERVATION (by extension)
Sub-types:	None

Name	OBSERVATION
Abstract	no

XML Instance Representation

<...>

<language> bt:CODE_PHRASE </language> [1]

<encoding> bt:CODE_PHRASE </encoding> [1]

<subject> bt:PARTY_PROXY </subject> [1]

<provider> bt:PARTY_PROXY </provider> [0..1]

<other_participations> bt:PARTICIPATION </other_participations> [0..*]

<work_flow_id> bt:OBJECT_REF </work_flow_id> [0..1]

<protocol> st:ITEM_STRUCTURE </protocol> [0..1]

<guideline_id> bt:OBJECT_REF </guideline_id> [0..1]

<data> st:HISTORY </data> [1]

<state> st:HISTORY </state> [0..1]

</...>

Schema Component Representation

<xs:complexType name="OBSERVATION">

<xs:complexContent>

<xs:extension base="CARE_ENTRY">

<xs:sequence>

<xs:element name="data" type="st:HISTORY"/>

<-- It is recommended that state data is recorded for each event (see EVENT class) On occasions where it is necessary to have a detailed event model for state separately than the data itself, then use this state History. It is not possible to use this element and the state element of events contained in the data history. -->

<xs:element name="state" type="st:HISTORY" minOccurs="0"/>

</xs:sequence>

</xs:extension>

</xs:complexContent>

</xs:complexType>

Generated by <oXygen/> XML Editor using a modified version of xs3p that adds schema diagrams and chunking support. Last modified:

openEHR XML Schema Release 1.0 candidate

Complex Type: OBSERVATION

[Table of contents]