Comments below.
Thanks,
Paul
Paul Lipton
CA Technologies
VP, Industry Standards and Open Source
Member, CA Council for Technical Excellence
Office Phone: +1 609 583-9718
Mobile: +1 267 987-6887
Email:
THIS MESSAGE MAY CONTAIN CONFIDENTIAL, PRIVILEGED OR OTHER LEGALLY
PROTECTED INFORMATION. IT IS INTENDED FOR THE ADDRESSEE ONLY. IF YOU ARE NOT
THE ADDRESSEE (OR SOMEONE THE ADDRESSEE AUTHORIZED TO RECEIVE THIS MESSAGE),
YOU ARE PROHIBITED FROM COPYING, DISTRIBUTING OR OTHERWISE USING IT. PLEASE
NOTIFY THE SENDER AND RETURN IT AT OUR COST. THANK YOU.
From: Vaught, Jeffrey A
[mailto:]
Sent: Monday, December 06, 2010 10:35 AM
To:
Subject: [saf] Issue 015 - alternatives to Protocol
Proposals for
replacement for Protocol/Prescription:
PrescriptionTemplate
/ PrescriptionInstance. Not really class/instance relationship.
PrescriptionTemplate
/ Prescription (leave latter unchanged).
PrescriptionClass
/ PrescriptionInstance. Not really class/instance relationship.
Prescription /
Prescription (but make distinction in the spec).
[[Paul]] Confusing?
Prescription /
PrescriptionInstance. Not really class/instance relationship.
Treatment /
Prescription. Treatment doesn’t capture diagnostics,
optimizations??
[[Paul]] It does. Treatments routinely
include diagnostics. I treat you with Coumadin (a blood thinner and monitor
kidney function). Or I you come into an allergist’s office complaining of
allergies and treatment consists of evaluation your allergies with tests before
deciding on a treatment regimen.
I suppose you could use the class of
Regimen, too, for that matter! :-)
Jeff likes
#2 & #6.
