From 3bd7f970e7f583e44aeee18ea13244fdda108b11 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 10:38:24 +0500
Subject: [PATCH 01/26] Create readme.md

---
 .../readme.md                                 | 36 +++++++++++++++++++
 1 file changed, 36 insertions(+)
 create mode 100644 patient-charting/manage-immunization-recommendation/readme.md

diff --git a/patient-charting/manage-immunization-recommendation/readme.md b/patient-charting/manage-immunization-recommendation/readme.md
new file mode 100644
index 0000000..48323fc
--- /dev/null
+++ b/patient-charting/manage-immunization-recommendation/readme.md
@@ -0,0 +1,36 @@
+####Description
+--------------
+
+The ImmunizationRecommendation resource is intended to cover communication of a specified patient's immunization recommendation and status across all healthcare disciplines in all care settings and all regions.
+
+Additionally, the ImmunizationRecommendation resource is expected to cover key concepts related to the querying of a patient's immunization recommendation and status.
+
+The Developed Application will allow user to maintain and acces health care plans. It will allow user to create new care plan, modify existing plan and accessing existing plans. It will also provide the ability to provide access to standard care plan when requested at the time of the clinical encounter.
+
+![use-case-model](https://f.cloud.github.com/assets/5391320/1799562/05c6776e-6ba3-11e3-912a-0926dda4a11c.png)
+
+####Functional Requirements
+* REQ-1: Create Care Plan
+* REQ-2: List Care Plans
+* REQ-3: Get Care Plan Details
+* REQ-4: Update Care Plan
+* REQ-6: Print Care Plan Details
+
+_______________________________________________________________
+**Reference Hl7 RMIM:** [More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference FHIR Resource:**
+[More Details](http://www.hl7.org/implement/standards/fhir/careplan.html)
+
+![careplan fhir resource](https://f.cloud.github.com/assets/5391320/1799911/79a0a0d8-6bb2-11e3-916a-a927fca477e2.png)
+
+_______________________________________________________________
+**Reference CDA Template:** [More Details](http://www.hl7.org/Special/committees/structure/index.cfm)
+
+Document Level Template **"Care Plan (NEW)"**
+_______________________________________________________________
+**Reference OpenEHR Archetypes (Version 1.4):** [More Details](http://www.openehr.org/ckm/)
+
+N/A

From 24df57ddcc2a6750a2e501913bb5c3c235c53d3d Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 11:01:55 +0500
Subject: [PATCH 02/26] Update readme.md

---
 .../readme.md                                 | 103 +++++++++++++++---
 1 file changed, 88 insertions(+), 15 deletions(-)

diff --git a/patient-charting/manage-immunization-recommendation/readme.md b/patient-charting/manage-immunization-recommendation/readme.md
index 48323fc..d4a5c08 100644
--- a/patient-charting/manage-immunization-recommendation/readme.md
+++ b/patient-charting/manage-immunization-recommendation/readme.md
@@ -1,20 +1,15 @@
 ####Description
 --------------
 
-The ImmunizationRecommendation resource is intended to cover communication of a specified patient's immunization recommendation and status across all healthcare disciplines in all care settings and all regions.
+The Immunization Recommendation is intended to cover communication of a specified patient's immunization recommendation and status across all healthcare disciplines in all care settings and all regions. Additionally, the Immunization Recommendation is expected to cover key concepts related to the querying of a patient's immunization recommendation and status.
 
-Additionally, the ImmunizationRecommendation resource is expected to cover key concepts related to the querying of a patient's immunization recommendation and status.
-
-The Developed Application will allow user to maintain and acces health care plans. It will allow user to create new care plan, modify existing plan and accessing existing plans. It will also provide the ability to provide access to standard care plan when requested at the time of the clinical encounter.
-
-![use-case-model](https://f.cloud.github.com/assets/5391320/1799562/05c6776e-6ba3-11e3-912a-0926dda4a11c.png)
+![image](https://f.cloud.github.com/assets/4283040/1810153/5ba0dcd0-6e17-11e3-992c-4cab21fac617.png)
 
 ####Functional Requirements
-* REQ-1: Create Care Plan
-* REQ-2: List Care Plans
-* REQ-3: Get Care Plan Details
-* REQ-4: Update Care Plan
-* REQ-6: Print Care Plan Details
+* REQ-1: Create Immunization Recommendation
+* REQ-2: List Immunization Recommendation
+* REQ-3: Get Immunization Recommendation
+* REQ-4: Update Immunization Recommendation
 
 _______________________________________________________________
 **Reference Hl7 RMIM:** [More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
@@ -22,15 +17,93 @@ _______________________________________________________________
 N/A
 _______________________________________________________________
 **Reference FHIR Resource:**
-[More Details](http://www.hl7.org/implement/standards/fhir/careplan.html)
+[More Details](http://www.hl7.org/implement/standards/fhir/immunizationrecommendation.html)
 
-![careplan fhir resource](https://f.cloud.github.com/assets/5391320/1799911/79a0a0d8-6bb2-11e3-916a-a927fca477e2.png)
+![image](https://f.cloud.github.com/assets/4283040/1810160/a161abd2-6e17-11e3-9c99-8dd73c7117a1.png)
 
 _______________________________________________________________
 **Reference CDA Template:** [More Details](http://www.hl7.org/Special/committees/structure/index.cfm)
 
-Document Level Template **"Care Plan (NEW)"**
+Section Level Template **"Immunizations V2"**
 _______________________________________________________________
 **Reference OpenEHR Archetypes (Version 1.4):** [More Details](http://www.openehr.org/ckm/)
 
-N/A
+```
+archetype (adl_version=1.4)
+	openEHR-EHR-COMPOSITION.vaccination_list.v1
+concept
+	[at0000]	-- Vaccination List
+language
+	original_language = <[ISO_639-1::en]>
+description
+	original_author = <
+		["name"] = <"Heather Leslie">
+		["organisation"] = <"Ocean Informatics">
+		["email"] = <"heather.leslie@oceaninformatics.com">
+		["date"] = <"2013-03-12">
+	>
+	details = <
+		["en"] = <
+			language = <[ISO_639-1::en]>
+			purpose = <"To record a persistent a list of vaccinations that have been administered to the subject over time and to enable sharing of a vaccination list to other healthcare providers.">
+			use = <"Use to record a persistent list of all vaccinations administered to the subject.
+
+In local systems it is possible to generate a list of vaccinations by querying the database for all ACTION.medication archetypes that have been used to record vaccinations. However this list is useful to support exchange of a local vaccination list with other healthcare providers.">
+			keywords = <"vaccination", "immunisation", "list">
+			misuse = <"">
+			copyright = <"© openEHR Foundation">
+		>
+	>
+	lifecycle_state = <"CommitteeDraft">
+	other_contributors = <"Ian McNicoll, Ocean Informatics, United Kingdom (Editor)", "Sam Heard, Ocean Informatics, Australia", "Sistine Barretto-Daniels, Ocean Informatics, Australia">
+	other_details = <
+		["current_contact"] = <"Heather Leslie, Ocean Informatics, heather.leslie@oceaninformatics.com">
+		["MD5-CAM-1.0.1"] = <"2D1B12194E93B860DBD6E553CB0D0344">
+	>
+definition
+	COMPOSITION[at0000] matches {	-- Vaccination List
+		category matches {
+			DV_CODED_TEXT matches {
+				defining_code matches {[openehr::431]}
+			}
+		}
+		content cardinality matches {1..*; unordered} matches {
+			allow_archetype ACTION[at0001] occurrences matches {0..*} matches {	-- Vaccinations Administered
+				include
+					archetype_id/value matches {/openEHR-EHR-ACTION\.medication(-[a-zA-Z0-9_]+)*\.v1/}
+			}
+			allow_archetype EVALUATION[at0002] occurrences matches {0..*} matches {	-- Exclusion Statement
+				include
+					archetype_id/value matches {/.*/}
+			}
+			allow_archetype EVALUATION[at0003] occurrences matches {0..*} matches {	-- Absent Information
+				include
+					archetype_id/value matches {/openEHR-EHR-EVALUATION\.absence(-[a-zA-Z0-9_]+)*\.v1/}
+			}
+		}
+	}
+ontology
+	term_definitions = <
+		["en"] = <
+			items = <
+				["at0000"] = <
+					text = <"Vaccination List">
+					description = <"A persistent a list of vaccinations that have been administered to the subject over time, that may influence clinical decision-making and care provision.">
+				>
+				["at0001"] = <
+					text = <"Vaccinations Administered">
+					description = <"Details about vaccinations that have been administered to the subject.">
+				>
+				["at0002"] = <
+					text = <"Exclusion Statement">
+					description = <"Positive statement about the known exclusion of vaccination administration.">
+					comment = <"For example: \"No vaccinations have been administered\".">
+				>
+				["at0003"] = <
+					text = <"Absent Information">
+					description = <"Positive statement that no information is available about vaccine administration.">
+				>
+			>
+		>
+>
+```

From d2bd474212a4b112267b26e64293607cf039cb59 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 11:16:31 +0500
Subject: [PATCH 03/26] Update readme.md

---
 patient-charting/manage-immunization-recommendation/readme.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/patient-charting/manage-immunization-recommendation/readme.md b/patient-charting/manage-immunization-recommendation/readme.md
index d4a5c08..037058e 100644
--- a/patient-charting/manage-immunization-recommendation/readme.md
+++ b/patient-charting/manage-immunization-recommendation/readme.md
@@ -3,7 +3,7 @@
 
 The Immunization Recommendation is intended to cover communication of a specified patient's immunization recommendation and status across all healthcare disciplines in all care settings and all regions. Additionally, the Immunization Recommendation is expected to cover key concepts related to the querying of a patient's immunization recommendation and status.
 
-![image](https://f.cloud.github.com/assets/4283040/1810153/5ba0dcd0-6e17-11e3-992c-4cab21fac617.png)
+![image](https://f.cloud.github.com/assets/4283040/1813453/5decedec-6ebe-11e3-84a0-e8db992c5956.png)
 
 ####Functional Requirements
 * REQ-1: Create Immunization Recommendation

From 64530123902b7a81d85c68870f3e01d20fb601d6 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 11:40:19 +0500
Subject: [PATCH 04/26] Create create-immunization-recommendation.md

---
 .../create-immunization-recommendation.md     | 38 +++++++++++++++++++
 1 file changed, 38 insertions(+)
 create mode 100644 patient-charting/manage-immunization-recommendation/create/create-immunization-recommendation.md

diff --git a/patient-charting/manage-immunization-recommendation/create/create-immunization-recommendation.md b/patient-charting/manage-immunization-recommendation/create/create-immunization-recommendation.md
new file mode 100644
index 0000000..7335b4d
--- /dev/null
+++ b/patient-charting/manage-immunization-recommendation/create/create-immunization-recommendation.md
@@ -0,0 +1,38 @@
+#####Use Case ID: UC-PC40
+#####Use Case Name: Create Immunization Recommendation
+
+**Level:**                     User Level Goal
+
+**Primary Actors:**            Physician
+
+**Stakeholders:**              Physician, Nurse
+
+**Purpose:**                   The main intent of this use case is to create a immunization recommendation for a patient condition.
+
+**Pre Condition:**             Physician must be identified and authenticated.
+
+**Post Condition:**            Immunization Recommendation recorded successfully.
+
+**Frequency of Occurrence:**   High
+__________________________________________________________
+**Main Success Scenario: (Create Immunization Recommendation)**
+
+1. Physician selects a immunization recommendation option.
+2. System asks user to specify the following information:
+    * Immunization type and dose 
+    * date and time of administration 
+    * route and site
+    * manufacturer
+    * user ID.
+3. Physician enters the required fields.
+4. System validates the fields and records the immunization recommendation.
+________________________________________________________________________
+**Reference Hl7 V3 Interaction Identifiers:**
+[More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference CCHIT Criteria:**
+[More Details](https://www.cchit.org/cchit-certified)
+
+FN 16.03

From 8b1cbcbc9cb2a29fd2b7908e0bcf6a7ae6e0ad8f Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 11:41:22 +0500
Subject: [PATCH 05/26] Update create-immunization-recommendation.md

---
 .../create/create-immunization-recommendation.md                 | 1 +
 1 file changed, 1 insertion(+)

diff --git a/patient-charting/manage-immunization-recommendation/create/create-immunization-recommendation.md b/patient-charting/manage-immunization-recommendation/create/create-immunization-recommendation.md
index 7335b4d..f00e548 100644
--- a/patient-charting/manage-immunization-recommendation/create/create-immunization-recommendation.md
+++ b/patient-charting/manage-immunization-recommendation/create/create-immunization-recommendation.md
@@ -26,6 +26,7 @@ __________________________________________________________
     * user ID.
 3. Physician enters the required fields.
 4. System validates the fields and records the immunization recommendation.
+
 ________________________________________________________________________
 **Reference Hl7 V3 Interaction Identifiers:**
 [More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)

From 264ea20d86599b79d086c4394292475d38c9d40e Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 11:43:40 +0500
Subject: [PATCH 06/26] Update and rename create-immunization-recommendation.md
 to PC73-create-immunization-recommendation.md

---
 ...mmendation.md => PC73-create-immunization-recommendation.md} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename patient-charting/manage-immunization-recommendation/create/{create-immunization-recommendation.md => PC73-create-immunization-recommendation.md} (98%)

diff --git a/patient-charting/manage-immunization-recommendation/create/create-immunization-recommendation.md b/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
similarity index 98%
rename from patient-charting/manage-immunization-recommendation/create/create-immunization-recommendation.md
rename to patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
index f00e548..54d3897 100644
--- a/patient-charting/manage-immunization-recommendation/create/create-immunization-recommendation.md
+++ b/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
@@ -1,4 +1,4 @@
-#####Use Case ID: UC-PC40
+#####Use Case ID: UC-PC73
 #####Use Case Name: Create Immunization Recommendation
 
 **Level:**                     User Level Goal

From 221e86af44598c4d2a93803f3de189469534f6a3 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 12:07:08 +0500
Subject: [PATCH 07/26] Create PC74-list-immunization-recommendation.md

---
 .../PC74-list-immunization-recommendation.md  | 50 +++++++++++++++++++
 1 file changed, 50 insertions(+)
 create mode 100644 patient-charting/manage-immunization-recommendation/read/PC74-list-immunization-recommendation.md

diff --git a/patient-charting/manage-immunization-recommendation/read/PC74-list-immunization-recommendation.md b/patient-charting/manage-immunization-recommendation/read/PC74-list-immunization-recommendation.md
new file mode 100644
index 0000000..fb07b39
--- /dev/null
+++ b/patient-charting/manage-immunization-recommendation/read/PC74-list-immunization-recommendation.md
@@ -0,0 +1,50 @@
+#####Use Case ID: UC-PC74
+#####Use Case Name: List Immunization Recommendations
+
+**Level:**                     User Level Goal
+
+**Primary Actors:**            Physician
+
+**Stakeholders:**              Physician, Nurse
+
+**Purpose:**                   The main intent of this use case is to display a list of immunization recommendations for a patient condition.
+
+**Pre Condition:**             Physician must be identified and authenticated.
+
+**Post Condition:**            Immunization Recommendations listed uccessfully.
+
+**Frequency of Occurrence:**   High
+__________________________________________________________
+**Main Success Scenario: (List Immunization Recommendations)**
+
+1.	Physician requests to display list of immunization recommendations.
+2.	System asks user to specify the filtering criteria(if any) such as 
+      * Immunization type
+      * date and time of administration 
+      * route and site
+      * manufacturer
+3.	Physician enters the filtering criteria.
+4.	System then displays the list of immunization recommendations as per criteria.
+
+__________________________________________________________
+**Alternate Flows:**
+
+**Alt-1: List Immunization Recommendations in a Patient Chart**
+
+1.	Physician selects [find patients](../../../patient-administration/manage-patient-registry/find-patients.md) option.
+2.	System displays the list of patients.
+3.	Physician navigate to an appropriate patient and then selects view patient's chart option.
+4.	System displays the full patient chart.
+5.	Physician selectes the immunization recommendation tab.
+6.	System then displays the patient's immunization recommendation list.
+
+________________________________________________________________________
+**Reference Hl7 V3 Interaction Identifiers:**
+[More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference CCHIT Criteria:**
+[More Details](https://www.cchit.org/cchit-certified)
+
+FN 16.03

From b64eb1b459e1a1bc3bff7ae5e0eba087afe2f0ae Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 12:12:20 +0500
Subject: [PATCH 08/26] Update PC73-create-immunization-recommendation.md

---
 .../PC73-create-immunization-recommendation.md     | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md b/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
index 54d3897..b8bacdd 100644
--- a/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
+++ b/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
@@ -27,6 +27,18 @@ __________________________________________________________
 3. Physician enters the required fields.
 4. System validates the fields and records the immunization recommendation.
 
+__________________________________________________________
+**Alternate Flows:**
+
+**Alt-1: Interaction Checking**
+
+1.	Repeat step 1 to 3 from the main scenario.
+2.	Physician review the system response of interaction checking and take actions as: 
+  * In case any drug or allergy interaction reveals, it sort some other alternate immunization and proceed with normal order flow if find no drug to drug or drug to allergy interaction, 
+  * In case absence of any drug to drug or drug to allergy interaction, the physician proceeds with normal flow of immunization recommendation process, 
+  * System will set the immunization recommendation status to active.
+3.	The step 4 in main scenario of events are then executed.
+
 ________________________________________________________________________
 **Reference Hl7 V3 Interaction Identifiers:**
 [More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
@@ -36,4 +48,4 @@ _______________________________________________________________
 **Reference CCHIT Criteria:**
 [More Details](https://www.cchit.org/cchit-certified)
 
-FN 16.03
+FN 16.02, FN 16.03

From b97ff0a9b3588687f783289ee91992bd9d99622f Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 12:14:03 +0500
Subject: [PATCH 09/26] Update PC73-create-immunization-recommendation.md

---
 .../create/PC73-create-immunization-recommendation.md         | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md b/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
index b8bacdd..57cb057 100644
--- a/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
+++ b/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
@@ -34,8 +34,8 @@ __________________________________________________________
 
 1.	Repeat step 1 to 3 from the main scenario.
 2.	Physician review the system response of interaction checking and take actions as: 
-  * In case any drug or allergy interaction reveals, it sort some other alternate immunization and proceed with normal order flow if find no drug to drug or drug to allergy interaction, 
-  * In case absence of any drug to drug or drug to allergy interaction, the physician proceeds with normal flow of immunization recommendation process, 
+  * In case any allergy interaction reveals, it sort some other alternate immunization and proceed with normal order flow if find no allergy interaction, 
+  * In case absence of any allergy interaction, the physician proceeds with normal flow of immunization recommendation process, 
   * System will set the immunization recommendation status to active.
 3.	The step 4 in main scenario of events are then executed.
 

From e68ab8e7f07da5f6efabe2a1f73e32f113912173 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 12:20:15 +0500
Subject: [PATCH 10/26] Create PC75-get-immunization-recommendation.md

---
 .../PC75-get-immunization-recommendation.md   | 55 +++++++++++++++++++
 1 file changed, 55 insertions(+)
 create mode 100644 patient-charting/manage-immunization-recommendation/read/PC75-get-immunization-recommendation.md

diff --git a/patient-charting/manage-immunization-recommendation/read/PC75-get-immunization-recommendation.md b/patient-charting/manage-immunization-recommendation/read/PC75-get-immunization-recommendation.md
new file mode 100644
index 0000000..e0d2fb0
--- /dev/null
+++ b/patient-charting/manage-immunization-recommendation/read/PC75-get-immunization-recommendation.md
@@ -0,0 +1,55 @@
+#####Use Case ID: UC-PC75
+#####Use Case Name: Get Immunization Recommendations
+
+**Level:**                     User Level Goal
+
+**Primary Actors:**            Physician
+
+**Stakeholders:**              Physician, Nurse
+
+**Purpose:**                   The main intent of this use case is to display the details of immunization recommendation of a patient condition.
+
+**Pre Condition:**             Physician must be identified and authenticated.
+
+**Post Condition:**            Immunization Recommendations details displayed uccessfully.
+
+**Frequency of Occurrence:**   High
+__________________________________________________________
+**Main Success Scenario: (Get Immunization Recommendations)**
+
+1.	Physician requests to display list of immunization recommendations.
+2.	System asks user to specify the filtering criteria(if any) such as 
+      * Immunization type
+      * date and time of administration 
+      * route and site
+      * manufacturer
+3.	Physician enters the filtering criteria.
+4.	System then displays the list of immunization recommendations as per criteria.
+
+1.  User performs the actions in [list immunization recommendations usecase](PC74-list-immunization-recommendation.md).
+2.	System displays the list of immunization recommendations.
+3.	User selects an appropriate immunization recommendation and selects view details option.
+4.	System displays the details of selected immunization recommendations.
+
+__________________________________________________________
+**Alternate Flows:**
+
+**Alt-1: List Immunization Recommendations in a Patient Chart**
+
+1.	Physician selects [find patients](../../../patient-administration/manage-patient-registry/find-patients.md) option.
+2.	System displays the list of patients.
+3.	Physician navigate to an appropriate patient and then selects view patient's chart option.
+4.	System displays the full patient chart.
+5.	Physician selectes the immunization recommendation tab.
+6.	System then displays the patient's immunization recommendation list.
+
+________________________________________________________________________
+**Reference Hl7 V3 Interaction Identifiers:**
+[More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference CCHIT Criteria:**
+[More Details](https://www.cchit.org/cchit-certified)
+
+FN 16.03

From 28ec2c24b3b98f582c73ba7ef7a6395b8eabdaf7 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 12:39:00 +0500
Subject: [PATCH 11/26] Create PC76-check-immunization-recommendation-status.md

---
 ...heck-immunization-recommendation-status.md | 33 +++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 patient-charting/manage-immunization-recommendation/read/PC76-check-immunization-recommendation-status.md

diff --git a/patient-charting/manage-immunization-recommendation/read/PC76-check-immunization-recommendation-status.md b/patient-charting/manage-immunization-recommendation/read/PC76-check-immunization-recommendation-status.md
new file mode 100644
index 0000000..0670b0f
--- /dev/null
+++ b/patient-charting/manage-immunization-recommendation/read/PC76-check-immunization-recommendation-status.md
@@ -0,0 +1,33 @@
+#####Use Case ID: UC-PC76
+#####Use Case Name: Check Immunization Recommendation Status
+
+**Level:**                     User Level Goal
+
+**Primary Actors:**            Physician
+
+**Stakeholders:**              Physician, Nurse
+
+**Purpose:**                   The main intent of this use case is to check the immunization recommendation status of a patient condition.
+
+**Pre Condition:**             Physician must be identified and authenticated.
+
+**Post Condition:**            Immunization Recommendations status checked uccessfully.
+
+**Frequency of Occurrence:**   High
+__________________________________________________________
+**Main Success Scenario: (Check Immunization Recommendation Status)**
+
+1.	User selects the immunization from the list of recommended immunization list and request for its status.
+2.	System responds with the status of the immunization (like active, complete, discontinue, refused etc)
+3.	User checks the status of immunization.
+
+________________________________________________________________________
+**Reference Hl7 V3 Interaction Identifiers:**
+[More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference CCHIT Criteria:**
+[More Details](https://www.cchit.org/cchit-certified)
+
+FN 16.03, IP 15.12

From aa83d7fabbd76f9cb29e58daa31cad96fc6b4093 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 12:41:54 +0500
Subject: [PATCH 12/26] Update PC73-create-immunization-recommendation.md

---
 .../create/PC73-create-immunization-recommendation.md         | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md b/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
index 57cb057..0c01cc5 100644
--- a/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
+++ b/patient-charting/manage-immunization-recommendation/create/PC73-create-immunization-recommendation.md
@@ -24,7 +24,7 @@ __________________________________________________________
     * route and site
     * manufacturer
     * user ID.
-3. Physician enters the required fields.
+3. Physician enters the required fields and specifies the clinical assesments required for immunization if required.
 4. System validates the fields and records the immunization recommendation.
 
 __________________________________________________________
@@ -48,4 +48,4 @@ _______________________________________________________________
 **Reference CCHIT Criteria:**
 [More Details](https://www.cchit.org/cchit-certified)
 
-FN 16.02, FN 16.03
+FN 16.02, FN 16.03, IP 15.07

From 0f32d91daccc16c569073e4d2170c130c9795681 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 12:54:57 +0500
Subject: [PATCH 13/26] Create PC77-update-immunization -recommendation.md

---
 ...C77-update-immunization -recommendation.md | 48 +++++++++++++++++++
 1 file changed, 48 insertions(+)
 create mode 100644 patient-charting/manage-immunization-recommendation/update/PC77-update-immunization -recommendation.md

diff --git a/patient-charting/manage-immunization-recommendation/update/PC77-update-immunization -recommendation.md b/patient-charting/manage-immunization-recommendation/update/PC77-update-immunization -recommendation.md
new file mode 100644
index 0000000..9022fd1
--- /dev/null
+++ b/patient-charting/manage-immunization-recommendation/update/PC77-update-immunization -recommendation.md	
@@ -0,0 +1,48 @@
+#####Use Case ID: UC-PC77
+#####Use Case Name: Update Immunization Recommendation
+
+**Level:**                     User Level Goal
+
+**Primary Actors:**            Physician
+
+**Stakeholders:**              Physician, Nurse
+
+**Purpose:**                   The main intent of this use case is to update a immunization recommendation for a patient condition.
+
+**Pre Condition:**             Physician must be identified and authenticated.
+
+**Post Condition:**            Immunization Recommendation updated successfully.
+
+**Frequency of Occurrence:**   High
+__________________________________________________________
+**Main Success Scenario: (Update Immunization Recommendation)**
+
+1.  User performs the actions in [list immunization recommendations usecase](../read/PC74-list-immunization-recommendation.md).
+2.	System displays the list of immunization recommendations.
+3.	User selects an appropriate immunization recommendation.
+4.	System displays the immunization recommendation details and asks user to modify desired fields.
+5.	User modifies the immunization details such as immunizatio type, date/time, route, site and manufacturer.
+6.	System validates the changes, creates a modified version of immunization recommendation and records the time of changes commited.
+
+__________________________________________________________
+**Alternate Flows:**
+
+**Alt-1: Interaction Checking**
+
+1.	Repeat step 1 to 5 from the main scenario.
+2.	Physician review the system response of interaction checking and take actions as: 
+  * In case any allergy interaction reveals, it sort some other alternate immunization and proceed with normal order flow if find no allergy interaction, 
+  * In case absence of any allergy interaction, the physician proceeds with normal flow of immunization recommendation process, 
+  * System will set the immunization recommendation status to active.
+3.	The step 6 in main scenario of events are then executed.
+
+________________________________________________________________________
+**Reference Hl7 V3 Interaction Identifiers:**
+[More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference CCHIT Criteria:**
+[More Details](https://www.cchit.org/cchit-certified)
+
+FN 16.02, FN 16.03, IP 15.07

From a6225944781d87ab9ffe0d871b3a6fff7c9d3074 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 13:03:11 +0500
Subject: [PATCH 14/26] Create
 PC78-change-immunization-recommendation-status.md

---
 ...ange-immunization-recommendation-status.md | 33 +++++++++++++++++++
 1 file changed, 33 insertions(+)
 create mode 100644 patient-charting/manage-immunization-recommendation/update/PC78-change-immunization-recommendation-status.md

diff --git a/patient-charting/manage-immunization-recommendation/update/PC78-change-immunization-recommendation-status.md b/patient-charting/manage-immunization-recommendation/update/PC78-change-immunization-recommendation-status.md
new file mode 100644
index 0000000..116537d
--- /dev/null
+++ b/patient-charting/manage-immunization-recommendation/update/PC78-change-immunization-recommendation-status.md
@@ -0,0 +1,33 @@
+#####Use Case ID: UC-PC78
+#####Use Case Name: Change Immunization Recommendation Status
+
+**Level:**                     User Level Goal
+
+**Primary Actors:**            Physician
+
+**Stakeholders:**              Physician, Nurse
+
+**Purpose:**                   The main intent of this use case is to change the immunization recommendation status of a patient condition.
+
+**Pre Condition:**             Physician must be identified and authenticated.
+
+**Post Condition:**            Immunization Recommendations status changed uccessfully.
+
+**Frequency of Occurrence:**   High
+__________________________________________________________
+**Main Success Scenario: (Changed Immunization Recommendation Status)**
+
+1.	User selects the immunization from the list of recommended immunization list and request for its status.
+2.	System responds with the status of the immunization (like active, complete, discontinue, refused etc)
+3.	User checks and change the status of immunization.
+
+________________________________________________________________________
+**Reference Hl7 V3 Interaction Identifiers:**
+[More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference CCHIT Criteria:**
+[More Details](https://www.cchit.org/cchit-certified)
+
+FN 16.03, IP 15.12

From 62bfd9f556f518ac8ff6eddebf399d0ba71fec02 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 13:58:44 +0500
Subject: [PATCH 15/26] Create
 PC79-add-comment-to-immunization-recommendation.md

---
 ...-comment-to-immunization-recommendation.md | 34 +++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100644 patient-charting/manage-immunization-recommendation/create/PC79-add-comment-to-immunization-recommendation.md

diff --git a/patient-charting/manage-immunization-recommendation/create/PC79-add-comment-to-immunization-recommendation.md b/patient-charting/manage-immunization-recommendation/create/PC79-add-comment-to-immunization-recommendation.md
new file mode 100644
index 0000000..bb7c78e
--- /dev/null
+++ b/patient-charting/manage-immunization-recommendation/create/PC79-add-comment-to-immunization-recommendation.md
@@ -0,0 +1,34 @@
+#####Use Case ID: UC-PCS79
+#####Use Case Name: Add Comment to Immunization Recommendation
+
+**Level:**                     User Level Goal
+
+**Primary Actors:**            Physician 
+
+**Stakeholders:**              Patient Charting User
+
+**Purpose:**                   The main intent of this use case is to add comment/note to the recommended immunization.
+
+**Pre Condition:**             Physician must be identified and authenticated.  
+
+**Post Condition:**            The comment/note added successfully.    
+
+**Frequency of Occurrence:**   High
+
+**Priority:**                  High
+__________________________________________________________
+**Main Success Scenario: (Add Comment to Immunization Recommendation)**
+
+1.	Physician will select the recommended immunization from the list and will add comment/note to it.
+2.	Physician will save the comment.
+3.	System will associate the comment to particular immunization recommendation.
+
+_______________________________________________________________
+**Reference Hl7 V3 Interaction Identifiers (Domain: Problem List):**
+
+-NA-
+_______________________________________________________________
+**Reference CCHIT Criteria:**
+
+IP 15.05 
+

From 7b9053ad7cf0ee5a14b6bdf117adb2757be5ac78 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 14:07:07 +0500
Subject: [PATCH 16/26] Update readme.md

---
 .../manage-immunization-recommendation/readme.md           | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/patient-charting/manage-immunization-recommendation/readme.md b/patient-charting/manage-immunization-recommendation/readme.md
index 037058e..d560ea8 100644
--- a/patient-charting/manage-immunization-recommendation/readme.md
+++ b/patient-charting/manage-immunization-recommendation/readme.md
@@ -3,13 +3,16 @@
 
 The Immunization Recommendation is intended to cover communication of a specified patient's immunization recommendation and status across all healthcare disciplines in all care settings and all regions. Additionally, the Immunization Recommendation is expected to cover key concepts related to the querying of a patient's immunization recommendation and status.
 
-![image](https://f.cloud.github.com/assets/4283040/1813453/5decedec-6ebe-11e3-84a0-e8db992c5956.png)
+![image](https://f.cloud.github.com/assets/4283040/1813840/37f08bc2-6ed6-11e3-84f8-3dc58991e755.png)
 
 ####Functional Requirements
 * REQ-1: Create Immunization Recommendation
 * REQ-2: List Immunization Recommendation
 * REQ-3: Get Immunization Recommendation
-* REQ-4: Update Immunization Recommendation
+* REQ-4: Check Immunization Recommendation Status
+* REQ-5: Update Immunization Recommendation
+* REQ-6: Change Immunization Recommendation Status
+* REQ-7: Add Comment to Immunization Recommendation
 
 _______________________________________________________________
 **Reference Hl7 RMIM:** [More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)

From c4a8689e5e6ee20847e8c955cebba726631dbce5 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Fri, 27 Dec 2013 16:39:03 +0500
Subject: [PATCH 17/26] Create readme.md

---
 .../manage-adverse-reaction/readme.md         | 109 ++++++++++++++++++
 1 file changed, 109 insertions(+)
 create mode 100644 patient-charting/manage-adverse-reaction/readme.md

diff --git a/patient-charting/manage-adverse-reaction/readme.md b/patient-charting/manage-adverse-reaction/readme.md
new file mode 100644
index 0000000..6116f45
--- /dev/null
+++ b/patient-charting/manage-adverse-reaction/readme.md
@@ -0,0 +1,109 @@
+####Description
+--------------
+
+Allergens, including immunizations, and substances are identified and coded (whenever possible) and the list is captured and maintained over time. All pertinent dates, including patient-reported events, are stored and the description of the patient allergy and adverse reaction is modifiable over time.
+
+![image](https://f.cloud.github.com/assets/4283040/1813840/37f08bc2-6ed6-11e3-84f8-3dc58991e755.png)
+
+####Functional Requirements
+* REQ-1: Create Adverse Reaction
+* REQ-2: List Adverse Reaction
+* REQ-3: Get Adverse Reaction
+* REQ-4: Update Adverse Reaction
+
+_______________________________________________________________
+**Reference Hl7 RMIM:** [More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference FHIR Resource:**
+[More Details](http://www.hl7.org/implement/standards/fhir/immunizationrecommendation.html)
+
+![image](https://f.cloud.github.com/assets/4283040/1810160/a161abd2-6e17-11e3-9c99-8dd73c7117a1.png)
+
+_______________________________________________________________
+**Reference CDA Template:** [More Details](http://www.hl7.org/Special/committees/structure/index.cfm)
+
+Section Level Template **"Immunizations V2"**
+_______________________________________________________________
+**Reference OpenEHR Archetypes (Version 1.4):** [More Details](http://www.openehr.org/ckm/)
+
+```
+archetype (adl_version=1.4)
+	openEHR-EHR-COMPOSITION.vaccination_list.v1
+concept
+	[at0000]	-- Vaccination List
+language
+	original_language = <[ISO_639-1::en]>
+description
+	original_author = <
+		["name"] = <"Heather Leslie">
+		["organisation"] = <"Ocean Informatics">
+		["email"] = <"heather.leslie@oceaninformatics.com">
+		["date"] = <"2013-03-12">
+	>
+	details = <
+		["en"] = <
+			language = <[ISO_639-1::en]>
+			purpose = <"To record a persistent a list of vaccinations that have been administered to the subject over time and to enable sharing of a vaccination list to other healthcare providers.">
+			use = <"Use to record a persistent list of all vaccinations administered to the subject.
+
+In local systems it is possible to generate a list of vaccinations by querying the database for all ACTION.medication archetypes that have been used to record vaccinations. However this list is useful to support exchange of a local vaccination list with other healthcare providers.">
+			keywords = <"vaccination", "immunisation", "list">
+			misuse = <"">
+			copyright = <"© openEHR Foundation">
+		>
+	>
+	lifecycle_state = <"CommitteeDraft">
+	other_contributors = <"Ian McNicoll, Ocean Informatics, United Kingdom (Editor)", "Sam Heard, Ocean Informatics, Australia", "Sistine Barretto-Daniels, Ocean Informatics, Australia">
+	other_details = <
+		["current_contact"] = <"Heather Leslie, Ocean Informatics, heather.leslie@oceaninformatics.com">
+		["MD5-CAM-1.0.1"] = <"2D1B12194E93B860DBD6E553CB0D0344">
+	>
+definition
+	COMPOSITION[at0000] matches {	-- Vaccination List
+		category matches {
+			DV_CODED_TEXT matches {
+				defining_code matches {[openehr::431]}
+			}
+		}
+		content cardinality matches {1..*; unordered} matches {
+			allow_archetype ACTION[at0001] occurrences matches {0..*} matches {	-- Vaccinations Administered
+				include
+					archetype_id/value matches {/openEHR-EHR-ACTION\.medication(-[a-zA-Z0-9_]+)*\.v1/}
+			}
+			allow_archetype EVALUATION[at0002] occurrences matches {0..*} matches {	-- Exclusion Statement
+				include
+					archetype_id/value matches {/.*/}
+			}
+			allow_archetype EVALUATION[at0003] occurrences matches {0..*} matches {	-- Absent Information
+				include
+					archetype_id/value matches {/openEHR-EHR-EVALUATION\.absence(-[a-zA-Z0-9_]+)*\.v1/}
+			}
+		}
+	}
+ontology
+	term_definitions = <
+		["en"] = <
+			items = <
+				["at0000"] = <
+					text = <"Vaccination List">
+					description = <"A persistent a list of vaccinations that have been administered to the subject over time, that may influence clinical decision-making and care provision.">
+				>
+				["at0001"] = <
+					text = <"Vaccinations Administered">
+					description = <"Details about vaccinations that have been administered to the subject.">
+				>
+				["at0002"] = <
+					text = <"Exclusion Statement">
+					description = <"Positive statement about the known exclusion of vaccination administration.">
+					comment = <"For example: \"No vaccinations have been administered\".">
+				>
+				["at0003"] = <
+					text = <"Absent Information">
+					description = <"Positive statement that no information is available about vaccine administration.">
+				>
+			>
+		>
+>
+```

From f85af8aae658828cf8724050d69d367a5b1dc0e5 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Mon, 30 Dec 2013 11:54:11 +0500
Subject: [PATCH 18/26] Update readme.md

---
 .../manage-adverse-reaction/readme.md         | 69 +++++++++++--------
 1 file changed, 40 insertions(+), 29 deletions(-)

diff --git a/patient-charting/manage-adverse-reaction/readme.md b/patient-charting/manage-adverse-reaction/readme.md
index 6116f45..7b7ffc2 100644
--- a/patient-charting/manage-adverse-reaction/readme.md
+++ b/patient-charting/manage-adverse-reaction/readme.md
@@ -3,7 +3,7 @@
 
 Allergens, including immunizations, and substances are identified and coded (whenever possible) and the list is captured and maintained over time. All pertinent dates, including patient-reported events, are stored and the description of the patient allergy and adverse reaction is modifiable over time.
 
-![image](https://f.cloud.github.com/assets/4283040/1813840/37f08bc2-6ed6-11e3-84f8-3dc58991e755.png)
+![image](https://f.cloud.github.com/assets/4283040/1820974/3c4060c4-7117-11e3-92f6-71da534e8e24.png)
 
 ####Functional Requirements
 * REQ-1: Create Adverse Reaction
@@ -17,22 +17,23 @@ _______________________________________________________________
 N/A
 _______________________________________________________________
 **Reference FHIR Resource:**
-[More Details](http://www.hl7.org/implement/standards/fhir/immunizationrecommendation.html)
+[More Details](http://www.hl7.org/implement/standards/fhir/adversereaction.html)
 
-![image](https://f.cloud.github.com/assets/4283040/1810160/a161abd2-6e17-11e3-9c99-8dd73c7117a1.png)
+![image](https://f.cloud.github.com/assets/4283040/1821071/e411ebf0-711d-11e3-946d-a448b6385e0a.png)
 
 _______________________________________________________________
 **Reference CDA Template:** [More Details](http://www.hl7.org/Special/committees/structure/index.cfm)
 
-Section Level Template **"Immunizations V2"**
+Section Level Template **"Allergies Section (V2)"**
 _______________________________________________________________
 **Reference OpenEHR Archetypes (Version 1.4):** [More Details](http://www.openehr.org/ckm/)
 
 ```
 archetype (adl_version=1.4)
-	openEHR-EHR-COMPOSITION.vaccination_list.v1
+	openEHR-EHR-COMPOSITION.adverse_reaction_list.v1
+
 concept
-	[at0000]	-- Vaccination List
+	[at0000]	-- Adverse Reaction List
 language
 	original_language = <[ISO_639-1::en]>
 description
@@ -40,16 +41,23 @@ description
 		["name"] = <"Heather Leslie">
 		["organisation"] = <"Ocean Informatics">
 		["email"] = <"heather.leslie@oceaninformatics.com">
-		["date"] = <"2013-03-12">
+		["date"] = <"2013-03-14">
 	>
 	details = <
 		["en"] = <
 			language = <[ISO_639-1::en]>
-			purpose = <"To record a persistent a list of vaccinations that have been administered to the subject over time and to enable sharing of a vaccination list to other healthcare providers.">
-			use = <"Use to record a persistent list of all vaccinations administered to the subject.
+			purpose = <"To record a persistent and managed list of all known adverse reactions experienced by the subject, or statements about positive exclusion or actual absence of information about adverse reactions, that may influence clinical decision-making and care provision.">
+			use = <"Use to record a persistent and managed list of all known adverse reactions (including allergies, hypersensitivities, side effects or intolerances) experienced by the subject, or statements about positive exclusion or actual absence of information about adverse reactions, that may influence clinical decision-making and care provision. 
+
+This list can be utilised as a source of up-to-date adverse reaction data for exchange or as the basis for decision support. 
+
+This list can be comprised of three types of archetype:
+- statements about the positive use of medications are recorded using the EVALUATION.adverse_reaction archetype; OR
+- a statement about the positive exclusion of medication use can be recorded using the specific EVALUATION.exclusion-adverse_reaction archetype - for example: \"No known adverse reactions\"; OR
+- a statement about no information being available - neither a positive and known presence of an adverse reaction nor a positive exclusion - can be recorded using the EVALUATION.absence archetype.
 
-In local systems it is possible to generate a list of vaccinations by querying the database for all ACTION.medication archetypes that have been used to record vaccinations. However this list is useful to support exchange of a local vaccination list with other healthcare providers.">
-			keywords = <"vaccination", "immunisation", "list">
+In order for this list to be accurate and safe to use as the basis for decision support activities and for exchange, this list should ideally be curated by a clinician responsible for the health record, rather than managed automatically by the clinical system through business rules alone.">
+			keywords = <"adverse", "reaction", "allergy", "intolerance", "effect", "hypersensitivity", "list", "side">
 			misuse = <"">
 			copyright = <"© openEHR Foundation">
 		>
@@ -58,52 +66,55 @@ In local systems it is possible to generate a list of vaccinations by querying t
 	other_contributors = <"Ian McNicoll, Ocean Informatics, United Kingdom (Editor)", "Sam Heard, Ocean Informatics, Australia", "Sistine Barretto-Daniels, Ocean Informatics, Australia">
 	other_details = <
 		["current_contact"] = <"Heather Leslie, Ocean Informatics, heather.leslie@oceaninformatics.com">
-		["MD5-CAM-1.0.1"] = <"2D1B12194E93B860DBD6E553CB0D0344">
+		["MD5-CAM-1.0.1"] = <"7C6282FE2D669F7DF0CC7CA4958E4A57">
 	>
+
 definition
-	COMPOSITION[at0000] matches {	-- Vaccination List
+	COMPOSITION[at0000] matches {	-- Adverse Reaction List
 		category matches {
 			DV_CODED_TEXT matches {
 				defining_code matches {[openehr::431]}
 			}
 		}
 		content cardinality matches {1..*; unordered} matches {
-			allow_archetype ACTION[at0001] occurrences matches {0..*} matches {	-- Vaccinations Administered
+			allow_archetype EVALUATION[at0002] occurrences matches {0..*} matches {	-- Adverse Reactions
 				include
-					archetype_id/value matches {/openEHR-EHR-ACTION\.medication(-[a-zA-Z0-9_]+)*\.v1/}
+					archetype_id/value matches {/openEHR-EHR-EVALUATION\.adverse_reaction(-[a-zA-Z0-9_]+)*\.v1/}
 			}
-			allow_archetype EVALUATION[at0002] occurrences matches {0..*} matches {	-- Exclusion Statement
+			allow_archetype EVALUATION[at0003] occurrences matches {0..*} matches {	-- Exclusion Statement
 				include
-					archetype_id/value matches {/.*/}
+					archetype_id/value matches {/openEHR-EHR-EVALUATION\.exclusion-adverse_reaction(-[a-zA-Z0-9_]+)*\.v1/}
 			}
-			allow_archetype EVALUATION[at0003] occurrences matches {0..*} matches {	-- Absent Information
+			allow_archetype EVALUATION[at0004] occurrences matches {0..*} matches {	-- Absent Information
 				include
 					archetype_id/value matches {/openEHR-EHR-EVALUATION\.absence(-[a-zA-Z0-9_]+)*\.v1/}
 			}
 		}
 	}
+
+
 ontology
 	term_definitions = <
 		["en"] = <
 			items = <
 				["at0000"] = <
-					text = <"Vaccination List">
-					description = <"A persistent a list of vaccinations that have been administered to the subject over time, that may influence clinical decision-making and care provision.">
-				>
-				["at0001"] = <
-					text = <"Vaccinations Administered">
-					description = <"Details about vaccinations that have been administered to the subject.">
+					text = <"Adverse Reaction List">
+					description = <"A persistent and managed list of adverse reactions experienced by the subject that may influence clinical decision-making and care provision.">
 				>
 				["at0002"] = <
-					text = <"Exclusion Statement">
-					description = <"Positive statement about the known exclusion of vaccination administration.">
-					comment = <"For example: \"No vaccinations have been administered\".">
+					text = <"Adverse Reactions">
+					description = <"Details about known adverse reactions.">
 				>
 				["at0003"] = <
+					text = <"Exclusion Statement">
+					description = <"Positive statement about exclusion of known adverse reactions.">
+					comment = <"For example: \"No known adverse reactions\".">
+				>
+				["at0004"] = <
 					text = <"Absent Information">
-					description = <"Positive statement that no information is available about vaccine administration.">
+					description = <"Positive statement that no information is available about adverse reactions.">
 				>
 			>
 		>
->
+	>
 ```

From b54bb9eb2ec822faa5ffa1ca4123ab67754e0209 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Mon, 30 Dec 2013 12:16:01 +0500
Subject: [PATCH 19/26] Create PC80-create-adverse-reaction.md

---
 .../create/PC80-create-adverse-reaction.md    | 41 +++++++++++++++++++
 1 file changed, 41 insertions(+)
 create mode 100644 patient-charting/manage-adverse-reaction/create/PC80-create-adverse-reaction.md

diff --git a/patient-charting/manage-adverse-reaction/create/PC80-create-adverse-reaction.md b/patient-charting/manage-adverse-reaction/create/PC80-create-adverse-reaction.md
new file mode 100644
index 0000000..714aa6e
--- /dev/null
+++ b/patient-charting/manage-adverse-reaction/create/PC80-create-adverse-reaction.md
@@ -0,0 +1,41 @@
+#####Use Case ID: UC-PC80
+#####Use Case Name: Create Adverse Reaction
+
+**Level:**                     User Level Goal
+
+**Primary Actors:**            Physician
+
+**Stakeholders:**              Physician, Nurse
+
+**Purpose:**                   The main intent of this use case is to add a adverse reaction of a patient condition.
+
+**Pre Condition:**             Physician must be identified and authenticated.
+
+**Post Condition:**            Adverse Reactioh recorded successfully.
+
+**Frequency of Occurrence:**   High
+__________________________________________________________
+**Main Success Scenario: (Create Adverse Reaction)**
+
+1. User selects a adverse reaction option.
+2. System asks user to specify the type, severity and substance (if known).
+3. User enters the required fields. 
+4. System validates the fields and records the adverse reaction.
+
+__________________________________________________________
+**Alternate Flow:**
+
+1. Repeat step 1-3  from the main success scenario.
+2. If substance is known, associate particular substance with the reaction.
+3. Repeat step 4 from the main success scenario.
+
+________________________________________________________________________
+**Reference Hl7 V3 Interaction Identifiers:**
+[More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference CCHIT Criteria:**
+[More Details](https://www.cchit.org/cchit-certified)
+
+FN 05.05, FN 05.13

From 93b13df1176973dda2353c2dd5db688882cb1168 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Mon, 30 Dec 2013 14:38:28 +0500
Subject: [PATCH 20/26] Create PC81-list-adverse-reactions.md

---
 .../read/PC81-list-adverse-reactions.md       | 46 +++++++++++++++++++
 1 file changed, 46 insertions(+)
 create mode 100644 patient-charting/manage-adverse-reaction/read/PC81-list-adverse-reactions.md

diff --git a/patient-charting/manage-adverse-reaction/read/PC81-list-adverse-reactions.md b/patient-charting/manage-adverse-reaction/read/PC81-list-adverse-reactions.md
new file mode 100644
index 0000000..a8a9dec
--- /dev/null
+++ b/patient-charting/manage-adverse-reaction/read/PC81-list-adverse-reactions.md
@@ -0,0 +1,46 @@
+#####Use Case ID: UC-PC74
+#####Use Case Name: List Adverse Reactions
+
+**Level:**                     User Level Goal
+
+**Primary Actors:**            Physician
+
+**Stakeholders:**              Physician, Nurse
+
+**Purpose:**                   The main intent of this use case is to display a list of adverse reactions of a patient condition.
+
+**Pre Condition:**             Physician must be identified and authenticated.
+
+**Post Condition:**            Adverse Reactions listed uccessfully.
+
+**Frequency of Occurrence:**   High
+__________________________________________________________
+**Main Success Scenario: (List Adverse Reactions)**
+
+1.	User requests to display list of adverse reactions.
+2.	System asks user to specify the filtering criteria(if any) such as type and severity.
+3.	User enters the filtering criteria.
+4.	System then displays the list of adverse reactions as per criteria.
+
+__________________________________________________________
+**Alternate Flows:**
+
+**Alt-1: List Adverse Reactions in a Patient Chart**
+
+1.	Physician selects [find patients](../../../patient-administration/manage-patient-registry/find-patients.md) option.
+2.	System displays the list of patients.
+3.	Physician navigate to an appropriate patient and then selects view patient's chart option.
+4.	System displays the full patient chart.
+5.	Physician selectes the adverse reaction tab.
+6.	System then displays the patient's adverse reaction list.
+
+________________________________________________________________________
+**Reference Hl7 V3 Interaction Identifiers:**
+[More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference CCHIT Criteria:**
+[More Details](https://www.cchit.org/cchit-certified)
+
+FN 05.12

From 5d87a1c25f532e34b6231bd09d604d95b3d70cb0 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Mon, 30 Dec 2013 14:41:58 +0500
Subject: [PATCH 21/26] Update PC75-get-immunization-recommendation.md

---
 .../read/PC75-get-immunization-recommendation.md         | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/patient-charting/manage-immunization-recommendation/read/PC75-get-immunization-recommendation.md b/patient-charting/manage-immunization-recommendation/read/PC75-get-immunization-recommendation.md
index e0d2fb0..2412822 100644
--- a/patient-charting/manage-immunization-recommendation/read/PC75-get-immunization-recommendation.md
+++ b/patient-charting/manage-immunization-recommendation/read/PC75-get-immunization-recommendation.md
@@ -17,15 +17,6 @@
 __________________________________________________________
 **Main Success Scenario: (Get Immunization Recommendations)**
 
-1.	Physician requests to display list of immunization recommendations.
-2.	System asks user to specify the filtering criteria(if any) such as 
-      * Immunization type
-      * date and time of administration 
-      * route and site
-      * manufacturer
-3.	Physician enters the filtering criteria.
-4.	System then displays the list of immunization recommendations as per criteria.
-
 1.  User performs the actions in [list immunization recommendations usecase](PC74-list-immunization-recommendation.md).
 2.	System displays the list of immunization recommendations.
 3.	User selects an appropriate immunization recommendation and selects view details option.

From 88b8954e2a098b804e950079f14338e500274b95 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Mon, 30 Dec 2013 14:48:17 +0500
Subject: [PATCH 22/26] Create PC82-get-adverse-reaction.md

---
 .../read/PC82-get-adverse-reaction.md         | 46 +++++++++++++++++++
 1 file changed, 46 insertions(+)
 create mode 100644 patient-charting/manage-adverse-reaction/read/PC82-get-adverse-reaction.md

diff --git a/patient-charting/manage-adverse-reaction/read/PC82-get-adverse-reaction.md b/patient-charting/manage-adverse-reaction/read/PC82-get-adverse-reaction.md
new file mode 100644
index 0000000..713a80f
--- /dev/null
+++ b/patient-charting/manage-adverse-reaction/read/PC82-get-adverse-reaction.md
@@ -0,0 +1,46 @@
+#####Use Case ID: UC-PC82
+#####Use Case Name: Get Adverse Reaction
+
+**Level:**                     User Level Goal
+
+**Primary Actors:**            Physician
+
+**Stakeholders:**              Physician, Nurse
+
+**Purpose:**                   The main intent of this use case is to display the details of adverse reaction of a patient condition.
+
+**Pre Condition:**             Physician must be identified and authenticated.
+
+**Post Condition:**            Adverse Reaction details displayed successfully.
+
+**Frequency of Occurrence:**   High
+__________________________________________________________
+**Main Success Scenario: (Get Adverse Reaction)**
+
+1.  User performs the actions in [list adverse reactions usecase](PC81-list-adverse-reactions.md).
+2.	System displays the list of adverse reactions.
+3.	User selects an appropriate adverse reaction and selects view details option.
+4.	System displays the details of selected adverse reactions.
+
+__________________________________________________________
+**Alternate Flows:**
+
+**Alt-1: List Adverse Reactions in a Patient Chart**
+
+1.	Physician selects [find patients](../../../patient-administration/manage-patient-registry/find-patients.md) option.
+2.	System displays the list of patients.
+3.	Physician navigate to an appropriate patient and then selects view patient's chart option.
+4.	System displays the full patient chart.
+5.	Physician selectes the adverse reaction tab.
+6.	System then displays the patient's adverse reactions list.
+
+________________________________________________________________________
+**Reference Hl7 V3 Interaction Identifiers:**
+[More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference CCHIT Criteria:**
+[More Details](https://www.cchit.org/cchit-certified)
+
+FN 05.12

From 681697f74c6d5fa7d89ab0c40633ea5e25cc87da Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Mon, 30 Dec 2013 14:50:56 +0500
Subject: [PATCH 23/26] Update PC82-get-adverse-reaction.md

---
 .../read/PC82-get-adverse-reaction.md                      | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/patient-charting/manage-adverse-reaction/read/PC82-get-adverse-reaction.md b/patient-charting/manage-adverse-reaction/read/PC82-get-adverse-reaction.md
index 713a80f..7a41dae 100644
--- a/patient-charting/manage-adverse-reaction/read/PC82-get-adverse-reaction.md
+++ b/patient-charting/manage-adverse-reaction/read/PC82-get-adverse-reaction.md
@@ -20,12 +20,12 @@ __________________________________________________________
 1.  User performs the actions in [list adverse reactions usecase](PC81-list-adverse-reactions.md).
 2.	System displays the list of adverse reactions.
 3.	User selects an appropriate adverse reaction and selects view details option.
-4.	System displays the details of selected adverse reactions.
+4.	System displays the details including the associated agents such as medication of selected adverse reactions.
 
 __________________________________________________________
 **Alternate Flows:**
 
-**Alt-1: List Adverse Reactions in a Patient Chart**
+**Alt-1: Get Adverse Reaction in a Patient Chart**
 
 1.	Physician selects [find patients](../../../patient-administration/manage-patient-registry/find-patients.md) option.
 2.	System displays the list of patients.
@@ -33,6 +33,7 @@ __________________________________________________________
 4.	System displays the full patient chart.
 5.	Physician selectes the adverse reaction tab.
 6.	System then displays the patient's adverse reactions list.
+7.	Repeat step 3 and 4 from the success scenario.
 
 ________________________________________________________________________
 **Reference Hl7 V3 Interaction Identifiers:**
@@ -43,4 +44,4 @@ _______________________________________________________________
 **Reference CCHIT Criteria:**
 [More Details](https://www.cchit.org/cchit-certified)
 
-FN 05.12
+FN 05.12, FN 05.13

From 65affd709135d84468ffa200de754bdf0d2a4960 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Mon, 30 Dec 2013 15:04:54 +0500
Subject: [PATCH 24/26] Create PC83-update-adverse-reaction.md

---
 .../update/PC83-update-adverse-reaction.md    | 45 +++++++++++++++++++
 1 file changed, 45 insertions(+)
 create mode 100644 patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md

diff --git a/patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md b/patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md
new file mode 100644
index 0000000..dc0776a
--- /dev/null
+++ b/patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md
@@ -0,0 +1,45 @@
+#####Use Case ID: UC-PC77
+#####Use Case Name: Update Adverse Reaction
+
+**Level:**                     User Level Goal
+
+**Primary Actors:**            Physician
+
+**Stakeholders:**              Physician, Nurse
+
+**Purpose:**                   The main intent of this use case is to update adverse reaction of a patient.
+
+**Pre Condition:**             Physician must be identified and authenticated.
+
+**Post Condition:**            Adverse Reaction updated successfully.
+
+**Frequency of Occurrence:**   High
+__________________________________________________________
+**Main Success Scenario: (Update Adverse Reaction)**
+
+1.  User performs the actions in [list adverse reactions usecase](../read/PC81-list-adverse-reactions.md).
+2.	System displays the list of adverse reactions.
+3.	User selects an appropriate adverse reaction.
+4.	System displays the adverse reactions details and asks user to modify desired fields.
+5.	User modifies the reaction details such as type, date/time and severity.
+6.	System validates the changes, creates a modified version of adverse reaction and records the time and user of committed changes.
+
+__________________________________________________________
+**Alternate Flows:**
+
+**Alt-1: Interaction Checking**
+
+1.	Repeat step 1 to 5 from the main scenario.
+2.	User modifies the status of the adverse reaction such as activate or de-activate.
+3.	The step 6 in main scenario of events are then executed.
+
+________________________________________________________________________
+**Reference Hl7 V3 Interaction Identifiers:**
+[More Details](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=306)
+
+N/A
+_______________________________________________________________
+**Reference CCHIT Criteria:**
+[More Details](https://www.cchit.org/cchit-certified)
+
+FN 05.01, FN 05.05, FN 05.07, FN 05.12, FN 05.13

From 4774aa0a091da780ab3f1b1b935faa7a099cdb5c Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Mon, 30 Dec 2013 15:05:42 +0500
Subject: [PATCH 25/26] Update PC83-update-adverse-reaction.md

---
 .../update/PC83-update-adverse-reaction.md                      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md b/patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md
index dc0776a..d4125d5 100644
--- a/patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md
+++ b/patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md
@@ -1,4 +1,4 @@
-#####Use Case ID: UC-PC77
+#####Use Case ID: UC-PC83
 #####Use Case Name: Update Adverse Reaction
 
 **Level:**                     User Level Goal

From eef7494355d8a7478d9777ad3a08c5913496f0a7 Mon Sep 17 00:00:00 2001
From: sidra shahbaz <sidra.shahbaz@seecs.edu.pk>
Date: Mon, 30 Dec 2013 15:07:04 +0500
Subject: [PATCH 26/26] Update PC83-update-adverse-reaction.md

---
 .../update/PC83-update-adverse-reaction.md                      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md b/patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md
index d4125d5..c16d2e9 100644
--- a/patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md
+++ b/patient-charting/manage-adverse-reaction/update/PC83-update-adverse-reaction.md
@@ -27,7 +27,7 @@ __________________________________________________________
 __________________________________________________________
 **Alternate Flows:**
 
-**Alt-1: Interaction Checking**
+**Alt-1: Update Adverse Reaction Status**
 
 1.	Repeat step 1 to 5 from the main scenario.
 2.	User modifies the status of the adverse reaction such as activate or de-activate.