MedMij:V2020.01/FHIR eAfspraak-LocationExample: verschil tussen versies
Naar navigatie springen
Naar zoeken springen
k (Gekopieerd van MedMij:Vprepub-2020.01/FHIR eAfspraak-LocationExample, versie 108832) |
k (Publish prepub to live environment) |
||
| Regel 1: | Regel 1: | ||
| − | |||
__NUMBEREDHEADINGS__ | __NUMBEREDHEADINGS__ | ||
{{DISPLAYTITLE:Example: Location as forwarder}} | {{DISPLAYTITLE:Example: Location as forwarder}} | ||
| − | {{MedMij: | + | {{MedMij:V2020.01/Issuebox_FHIR_IG}} |
If a Location is not registered as separate data in relation to Organization data at the source system (especially at General Practitioner Systems (Huisartsen Informatie Systeem)), a Location resource with minimal data should be constructed as a forwarder to the Organization resource where the Appointment will take place, in the following way: | If a Location is not registered as separate data in relation to Organization data at the source system (especially at General Practitioner Systems (Huisartsen Informatie Systeem)), a Location resource with minimal data should be constructed as a forwarder to the Organization resource where the Appointment will take place, in the following way: | ||
Versie van 22 nov 2022 13:34
If a Location is not registered as separate data in relation to Organization data at the source system (especially at General Practitioner Systems (Huisartsen Informatie Systeem)), a Location resource with minimal data should be constructed as a forwarder to the Organization resource where the Appointment will take place, in the following way:
<Location>
<id value="locationresourceid" />
<meta>
<profile value="http://fhir.nl/fhir/StructureDefinition/nl-core-location" />
</meta>
<name value="Aesculaap" />
<managingOrganization>
<reference value="Organization/organizationresourceid" />
<display value="Aesculaap" />
</managingOrganization>
</Location>