Merge pull request #8 from jkiddo/patch-1

Update ITI-118.md

input/pagecontent/ITI-118.md

@@ -57,7 +57,7 @@ The Scheduling Client may use a GET or POST based search. The Scheduling Server
 
 
 For example, search appointments for patient (identifier 12345), after October 21st, 2023 with practitioner (npi number: 12345678)
-```GET https://server.example.com/fhir/4/Patient?patient.identifier=urn:oid:1.2.3.4.5|12345&date=gt20231021&practitioner.identifier=urn:oid:2.16.840.1.113883.4.6|12345678```
+```GET https://server.example.com/fhir/4/Appointment?patient.identifier=urn:oid:1.2.3.4.5|12345&date=gt20231021&practitioner.identifier=urn:oid:2.16.840.1.113883.4.6|12345678```
 
 ###### Patient Identifiers
 Patient identifier shall be fully qualified and consist of an identifier value and system (a.k.a. assigning authority or patient identity domain). Preferably identifier systems are identified with an OID value (e.g. urn:oid:1.2.3.4.5). Alternatively a URI value may be used (e.g. http://hl7.org/fhir/sid/us-ssn or http://hospital-1.org). 
@@ -156,4 +156,4 @@ The Scheduling Server shall be grouped with an [ATNA Secure Node or Secure Appli
 
 ### Other Profile Groupings
 
-Both the Scheduling Client and Scheduling Server may be grouped with their respective [Internet User Authentication (IUA)](https://profiles.ihe.net/ITI/IUA/index.html) Actors. 
+Both the Scheduling Client and Scheduling Server may be grouped with their respective [Internet User Authentication (IUA)](https://profiles.ihe.net/ITI/IUA/index.html) Actors.