60 likes | 170 Views
RIM ITS overview. Just to get it right. We already have an ITS: the XML ITS We will discuss another ITS: the RIM ITS. XML ITS example. < c omponent typeCode="COMP"> < commonObservationEvent classCode="OBS" moodCode =" EVN”
E N D
Just to get it right... • We already have an ITS: the XML ITS • We will discuss another ITS: the RIM ITS
XML ITS example <component typeCode="COMP"> <commonObservationEvent classCode="OBS" moodCode="EVN” <code code="8302-2" codeSystem="2.16.840.1.113883.6.1" displayName="Lichaamslengte" <statusCode code="completed"/> <effectiveTime value="200907011346" /> <value xsi:type="PQ" value="90" unit="cm" /> <subject typeCode="SBJ" contextControlCode="OP"> <patient classCode="PAT"> <patientPerson classCode="PSN“ determinerCode="INSTANCE"> <name>ROELOFSEN, TOM</name>
RIM ITS example <outboundRelationship xsi:type="ActRelationship" assocName="subject" cloneName="Subject2" contextControlCode="AN" typeCode="SUBJ" contextConductionInd="false"><target xsi:type="SubstanceAdministration" classCode="SBADM" moodCode="RQO"><id root=""/><code code="DRUG" codeSystem=""/><participation xsi:type="Participation" contextControlCode="OP" typeCode="DIR"><role xsi:type="Role" assocName="medication" cloneName="Medication" classCode="ADMM"> <player xsi:type="ManufacturedMaterial" assocName="administerableMedicine" cloneName="Medicine" classCode="MMAT" determinerCode="KIND"> <code code="" codeSystem="?"/>
XML ITS • Clonenames do not carry semantic meaning • They are there for XSD validation • And disambiguation (clonenames are unique) • Readable • Tons of schema’s • Clonenames irrelevant in storage • Hard to convert to in-mem RIM Object model
RIM ITS • Clonenames are stripped, unchanging names from the RIM Classdiagram used instead • The “one” schema: RIM UML -> XSD • Aligns with RIM-database • Disambiguation by template or order • Validation requires new artifacts