We will call these resources the child resources. Suppose this CDR also contains Encounter/1 and Encounter/2, as well as Observation/3 and MedicationAdministration/4, and all of these resources have a reference to the resource Patient/A.
#How to wipe a cdr clean skin
This means that the last non-deleted version is version 11, and this could be accessed using a version-specific read to the following URL:Ī common problem – frequently in test systems but sometimes in production systems, too – is cleaning up batches of interdependent data.įor example, suppose you have a CDR containing a patient resource with the ID Patient/A. Cleaning and disinfection of hand and skin and alcohol resistant small objects.
In this example, we can see that the deleted version of the resource is version 12. Note that HTTP 410 Gone responses will include a Location header containing the fully qualified resource ID as well as the version ID. Using a FHIR instance-history: GET Patient/123/_history.Using a FHIR version-specific read: GET Patient/123/_history/1.It can still be found using two FHIR operations: The original content of the resource is not destroyed however. This patient will no longer appear in search results, and attempts to read the resource (using an HTTP GET Patient/123) will fail with an "HTTP 410 Gone" response. This will cause a second version of the Patient/123 resource to be created with version Patient/123/_history/2 that is marked as deleted. This means that data is not physically removed from the database.įor example, suppose a Patient resource with ID 123 is created (via an HTTP POST /Patient and subsequently deleted (via an HTTP DELETE Patient/123). The FHIR delete operation performs a "logical" delete. Cross-Organizational Data Access Profile 43.117.Inbound SMART on FHIR Authentication 43.113.Endpoint Validation: Request Validating 43.108.Prior Authorization Coverage Requirement Discovery 43.104.Da Vinci Health Record Exchange (HRex) 43.87.HL7 v2.x to FHIR Mapper - ORDER_OBSERVATION Group 43.78.HL7 v2.x to FHIR Mapper - OBSERVATION Group 43.77.HL7 v2.x Mapper - Forced Namespace Mode 43.73.HL7 v2.x Mapper - Contained Resource 43.71.FHIR Storage Module Scheduled Tasks 43.63.Encounter Start CDS hook configuration 43.33.Cross-Origin Resource Sharing (CORS) 43.27.Amazon HealthLake Outbound REST Connector 42.47.Subscription Matcher (R4 - Deprecated) 42.44.Subscription Matcher (DSTU3 - Deprecated) 42.43.Subscription Matcher (DSTU2 - Deprecated) 42.42.Subscription Matcher (All FHIR Versions) 42.41.FHIR REST Endpoint (R4 - Deprecated) 42.16.FHIR REST Endpoint (DSTU3 - Deprecated) 42.15.FHIR REST Endpoint (DSTU2 - Deprecated) 42.14.FHIR REST Endpoint (All Versions) 42.13.Documentation Templates and Rules (DTR) 42.9.
0 kommentar(er)
