Download presentation
Presentation is loading. Please wait.
Published byAlyson Neal Modified over 8 years ago
1
Archetype Modeling Language (AML) for CIMI UML for Archetypes Status update April 11, 2013
2
January 2013 Archetype Modeling Language for CIMI2 AML Objectives UML Style Guide and profile for archetype modeling Representation of ADL structures, constraints, and ontology Independent of reference model selection CIMI, openEHR, iso13606, CEM, others Define UML stereotypes, as necessary, to extend UML language Most archetype structure already supported by UML Primary addition: Terminology bindings (meaning and value set constraints)
3
January 2013 Archetype Modeling Language for CIMI3 AML RFP Status with OMG Submission postponed until September Additional status update from Harold Solbrig
4
January 2013 Archetype Modeling Language for CIMI4 Benefits of UML: Model Transformation Design AML profiles to simplify implementation and use Model-to-Model XSD Ecore and Java AOM CEM/ CDL CDA Model-to-Text ADL DITA (for publishing documentation) Mapping To C-CDA
5
January 2013 Archetype Modeling Language for CIMI5 AML Core Profile
6
January 2013 Archetype Modeling Language for CIMI6 AML Terminology Profile (meaning)
7
January 2013 Archetype Modeling Language for CIMI7 AML Terminology Profile (value sets)
8
January 2013 Archetype Modeling Language for CIMI8 Example Model-to-Model transform (using ATL) --- Transform ResolvedValueSet to to XSD enumeration with documentation and appinfo rule ResolvedValueSet { from valueSet : AMLTerm!ResolvedValueSet to outEnum : UML!Enumeration ( name <- valueSet.getName(), ownedComment <- valueSetURI, ownedLiteral <- valueSet.getMembers() ), valueSetURI : UML!Comment ( -- TODO XSD appinfo body <- valueSet.uri ) }
9
January 2013 Archetype Modeling Language for CIMI9 ValueSetMember -> XSD enumeration facet rule ValueSetMember { from valueSetMember : AMLTerm!ValueSetMember to literal : UML!EnumerationLiteral ( name <- valueSetMember.getName(), ownedComment <- designation, ownedComment <- conceptURI ), designation : UML!Comment ( body <- valueSetMember.designation ), conceptURI : UML!Comment ( body <- valueSetMember.uri ) do { designation.applyStereotype('XMLSchema::Documentation'); conceptURI.applyStereotype('XMLSchema::AppInfo'); }
10
January 2013 Archetype Modeling Language for CIMI10 CIMI Archetypes with Terminology Bindings
11
January 2013 Archetype Modeling Language for CIMI11 SNOMED CT references in UML, from CTS2
12
January 2013 Archetype Modeling Language for CIMI12 BACKUP SLIDES
13
January 2013 Archetype Modeling Language for CIMI13 Archetypes in openEHR Workbench
14
January 2013 Archetype Modeling Language for CIMI14 UML Table Editor for AML
15
January 2013 Archetype Modeling Language for CIMI15 Reference Model
16
January 2013 Archetype Modeling Language for CIMI16 Entry – Cluster – Element
17
January 2013 Archetype Modeling Language for CIMI17 Pattern Archetype in ADL definition ENTRY [at0000] matches { data matches { -- Result (in UML: nested, or inner, class) CLUSTER [at0002] occurrences matches {1} matches { items matches { ITEM [at0003] occurrences matches {*} matches {*} -- value ITEM [at0004] occurrences matches {0..1} matches {*} -- reference range } -- archetype slot, re-use a shared archetype for Body Location allow_archetype CLUSTER [at0005] occurrences matches {*} matches { include archetype_id/value matches {/cimi-RM-CLUSTER\.body_location\.v*/} }
18
January 2013 Archetype Modeling Language for CIMI18 Body Location CLUSTER Archetype definition CLUSTER [at0000] matches { items matches { ELEMENT [at0001] occurrences matches {0..1} matches { value matches { CODED_TEXT matches {*} } ELEMENT [at0002] occurrences matches {0..1} matches { value matches { PLAIN_TEXT matches {*} }
19
January 2013 Archetype Modeling Language for CIMI19 Pattern Archetype in UML
20
January 2013 Archetype Modeling Language for CIMI20 Clinical Archetype (extends Pattern) definition ENTRY [at0000.1] matches { -- redefine Result (using path to inherited CLUSTER) /data[at0002]/items matches { -- “heart rate value” is subset of Result value -- ELEMENT with Quantity value is specialization of Result ITEM ELEMENT [at0003.2] occurrences matches {0..1} matches { value matches { QUANTITY matches { units matches { CODED_TEXT matches { terminology_id matches { TERMINOLOGY_ID matches { value matches {"local"} } term_id matches {"at0.5"} }
21
January 2013 Archetype Modeling Language for CIMI21 Clinical Archetype (extends Pattern)
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.