1 / 6

RIM ITS overview

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”

hagop
Download Presentation

RIM ITS overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. RIM ITS overview

  2. Just to get it right... • We already have an ITS: the XML ITS • We will discuss another ITS: the RIM ITS

  3. 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>

  4. 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="?"/>

  5. 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

  6. 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

More Related