We will cleanup a few items in the $everything page:   This narrative will be updated from: "In the US Realm, at a minimum, the resources returned SHALL include all the data covered by the meaningful use common data elements as defined in the US Core Implementation Guide. Other applicable implementation guides may make additional rules about how much information that is returned." to: "Implementation guides may make additional rules about how much information that is returned."   This section will be updated from: This frees the client from needing to determine what it could or should ask for, particularly with regard to included resources. Servers should consider returning appropriate Provenance and AuditTrail on the returned resources, even though these are not directly part of the patient compartment. to: This frees the client from needing to determine what it could or should ask for, particularly with regard to included resources.     We will update this from: When this operation is used to access multiple patient records at once, the return bundle could be rather a lot of data; servers may choose to require that such requests are made  asynchronously , and associated with  bulk data formats . Alternatively, clients may choose to page through the result set (or servers may require this). Paging through the results is done the same as for  Searching , using the  _count  parameter, and Bundle links. Implementers should note that paging will be slower than simply returning all the results at once (more network traffic, multiple latency delays) but may be required in order not to exhaust available memory reading or writing the whole response in a single package. Unlike searching, there is no inherent user-display order for the $everything operation. Servers might consider sorting the returned resources in descending order of last record update, but are not required to do so. to: When this operation is used to access multiple patient records at once, the return bundle could be rather a lot of data; servers may choose to require that such requests are made  asynchronously , and associated with  bulk data formats . Alternatively, clients may choose to page through the result set (or servers may require this). Paging through the results is done the same as for  Searching , using the  _count parameter, and Bundle links. There is no defined order for the results of $everything. Servers MAY consider sorting the returned resources in descending order of last record update.