9/10/2003
1) PA: Definition change
PatientEncounter.dischargeDispositionCode

From: A code depicting the actual disposition of the patient at the time of discharge (e.g., discharged to home, expired, against medical advice, etc.).

To: A code depicting the disposition of the patient at the time of discharge (e.g., discharged to home, expired, against medical advice, etc.).  While the encounter is still "active" (the encounter doesn't have an end date yet) this ATTRIBUTE should be interpreted as the expected discharge disposition. When the encounter is "completed" this field contains the actual discharge disposition.

2) SDTC: Sort Order change:
	Change sort order such that Act.title sorts above Act.text in R-MIMs / HMDs / Schemas. APPROVED


3) SDTC: 	Remove the following RIM classes: APPROVED
?	LinkHtml
?	LocalAttr
?	LocalMarkup
?	Table
?	TableStructure
?	TableCell
?	TableColumnStructure

4) SDTC: FormalNaming
	Clone name for "x_ActRelationshipPertinentInfo" comes out as "sourceOf", but should be "pertinentInformation". notify Woody (formal naming issue)


10/10/2003

PA: Change PatientEncounter.specialAccommodationCode to specialArrangementCode, and
change Domain SpecialAccomodation to SpecialArrangement and
Change attribute definition to: 
A code indicating the type of special arrangements provided for a patient encounter (e.g., wheelchair, stretcher, interpreter, attendant, seeing eye dog). For encounters in intention moods, this information can be used to identify special arrangements that will need to be made for the incoming patient. This is not related to the AccommodationEvent.

CD: Change InfrastructureRoot.typeID to InfrastructureRoot.typeId

11/17/2003

FI: Proposal delete attribute Account.name in favor Act.title.

SDTC: new x-domain "ActRelationshipEntry", as an ActRelationshipType, with Formal Name of "entry", comprised of "COMP" and "DRIV"
	Remove x-domain x_ActRelationshipPertinentInfo.
	Create a new x-domain "x_EntryRelationship" with a formal name of "entryRelationship", 
	Create a new x-domain "x_RelatedOrder" with a formal name of "relatedOrder", having 
Create formal names for new Act Class codes:
	Extract (code = "EXTRACT")
o	Electronic Health Record (code = "EHR")
	Folder (code = "FOLDER")
	Composition (code = "COMPOSITION")
o	Document (Code = "DOC")
?	Clinical document (code = "DOCCLIN")
	Organizer (Code = "ORGANIZER")
o	Document body (Code = "DOCBODY")
o	Document section (Code = "DOCSECT") 
o	Topic (Code = "TOPIC")
o	Category (Code = "CATEGORY")
	Entry (Code = "ENTRY")
o	Cluster (Code = "CLUSTER")
o	Battery (Code = "BATTERY")

PA FormalNames
x_ActEncounterReason" abstract concept with two existing codes as children -- "Medical Necessity" and "Patient request"
EncounterAdmissionUrgency to x_EncounterAdmissionUrgency
x_LocationRoleType to the RoleCode domain
Action: add two existing concepts as children under x_LocationRoleType -- AdministrativeLocationRoleType (V19393) and ServiceDeliveryLocationRoleType 


