This wiki has undergone a migration to Confluence found Here
Difference between revisions of "March 23rd, Templates Minutes"
Jump to navigation
Jump to search
Brett Esler (talk | contribs) |
Brett Esler (talk | contribs) |
||
Line 7: | Line 7: | ||
Discussion about model: | Discussion about model: | ||
− | # Metadata could cross reference with Order Sets, RLUS, Decision Support Service - Knowledge Module (be) | + | ## Metadata could cross reference with Order Sets, RLUS, Decision Support Service - Knowledge Module (be) |
− | # Example of RIM constraints using such a model (ms) | + | ## Example of RIM constraints using such a model (ms) |
− | # More detail required on where constraint statements reside in this model such as "if code is x then value must be y" (ms) | + | ## More detail required on where constraint statements reside in this model such as "if code is x then value must be y" (ms) |
− | # Constraint path expressions could use algebraic notation e.g. CareProvisionEvent.subject.Patient.Person.name | + | ## Constraint path expressions could use algebraic notation e.g. CareProvisionEvent.subject.Patient.Person.name |
# Next Agenda Topics | # Next Agenda Topics | ||
No determined | No determined |
Revision as of 21:40, 23 March 2006
- Roll Call
- Brett Esler (be)
- Mark Shafarman (ms)
- Jaing Dingli (jd)
- Agenda Check
- Domain Analysis Model
Discussion about model:
- Metadata could cross reference with Order Sets, RLUS, Decision Support Service - Knowledge Module (be)
- Example of RIM constraints using such a model (ms)
- More detail required on where constraint statements reside in this model such as "if code is x then value must be y" (ms)
- Constraint path expressions could use algebraic notation e.g. CareProvisionEvent.subject.Patient.Person.name
- Next Agenda Topics
No determined
- Adjourn
http://informatics.mayo.edu/wiki/index.php/March_8th%2C_Templates_Agenda