informatiestandaarden - Gebruikersbijdragen [nl]

Bestand:PatientCorrectionCommunication.png

2021-08-26T13:58:09Z

Stephan Opdenberg: PatientCorrectioCommunication statemachine

== Beschrijving ==
PatientCorrectioCommunication statemachine

FHIR:V1.0 FHIR IG STU3

2021-04-22T08:01:03Z

Stephan Opdenberg: MM-1795 Added CapabilityStatement description

__NOINDEX__
__NUMBEREDHEADINGS__
{{DISPLAYTITLE:FHIR Implementation Guide}}

__TOC__

=Introduction=
This implementation guide describes the considerations for using '''HL7® FHIR®''' in context of information standards that are maintained by Nictiz. It applies specifically to HL7® FHIR® version 3 (STU3).

This implementation guide is aimed at software vendors and developers that need to implement FHIR based information standards maintained by Nictiz. Users of this guide are expected to be familiar with the [https://hl7.org/fhir/STU3 FHIR STU3 specification] and resource processing. Where relevant, links to the FHIR specification are provided. This implementation guide is not intended to be a tutorial on that subject.

<section begin=OverarchingPrinciples />
=Use case overarching principles=
==Content Types and encodings==
Unless stated otherwise, the information standards use the [https://hl7.org/fhir/http.html#mime-type FHIR RESTful framework]. This framework defines at least three content-types to send/retrieve information:
* XML: application/fhir+xml
* JSON: application/fhir+json
* RDF: text/turtle - Not supported in this context

Servers SHALL support both XML and JSON, while clients MAY use either format for the request and the response. For the response, servers SHALL support server-driven content negotiation as described in [https://www.hl7.org/fhir/stu3/http.html#mime-type the FHIR specification]. This means that clients can indicate the desired response format using the optional <code>_format=[mimetype]</code> URL parameter, or the acceptable response format(s) using the <code>Accept</code> header. The URL parameter takes precedence over the header. If a client does not request a specific content-type, then it is server discretion to respond using XML or JSON.

FHIR uses UTF-8 for all request and response bodies. Since the [https://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7.1 HTTP specification (section 3.7.1)] defines a default character encoding of ISO-8859-1, requests and responses SHALL explicitly set the character encoding to UTF-8 using the <code>charset</code> parameter of the MIME-type in the <code>Content-Type</code> header. Requests MAY also specify this <code>charset</code> parameter in the <code>Accept</code> header and/or use the <code>Accept-Charset</code> header.

==Use of coded concepts==
===Textual description of coded concepts===
Coded information is extremely important for interoperability between systems. It enables systems to act on information rather than have humans read everything for interpretation - it enables medication related alerts, exercise encouragements because of weight increase, and many more things. In the HCIMs and profiles, we therefore strive for complete coverage of all possible situations.

However it is likely that unknown codes present themselves in the communication, for example because the sending system has updated its medication codes to a newer version than the receiving system, or because an older record item is coded in a way that now has been deprecated. It is therefore vital that, in addition to the code itself, the sender includes the semantics of the code. Therefore, systems SHOULD include [https://hl7.org/fhir/STU3/datatypes.html#coding {{fhir|(CodeableConcept).coding.display}}] and/or [https://hl7.org/fhir/STU3/datatypes.html#codeableconcept {{fhir|CodeableConcept.text}}] for coded data in FHIR instances. These fields may only be absent in rare circumstances, for example when dealing with historic data, or in data acquired without such info from a third party.

===Code system URIs===
A coded value in FHIR is communicated as a combination of a code (in {{fhir|.code}}) and the canonical URI for the code system from which it was drawn (in {{fhir|.system}}). Implementers SHALL use the canonical URI that is defined in the FHIR conformance resource. This canonical URI can be found by inspecting the ValueSet that is bound to a coded element in the appropriate FHIR profile.<ref>Although the canonical URI is not formally defined in the ValueSet, in practical terms it can be found here.</ref>

'''Please note''': it is an error to assume that the OID assigned to a code system can be used to construct its canonical URI. The canonical URI for use in a FHIR context will always be assigned through the conformance resources<ref>There are exceptions to this, in which case other rules apply, see [https://www.hl7.org/fhir/stu3/terminologies.html#system the FHIR specifications]. However, this situation is not expected to occur in the use cases that this IG covers.</ref>. It ''can'' align with this OID (as a (<code><nowiki>urn:oid:[oid]</nowiki></code> URI), but this is not always the case. For example, SNOMED CT is referenced by URL rather than by <code><nowiki>urn:oid:[oid]</nowiki></code>.

===Mapping of coded concepts===
Terminology from HCIMs or UCSDs (use case specific datasets) needs to be faithfully applied to the FHIR profiles, but this is not directly possible when the base FHIR resource defines required terminology that bears no direct relationship with the HCIM or UCSD. These cases include, but are not limited to, the FHIR resource elements of datatype {{datatype|code}} ({{fhir|Patient.gender}}, {{fhir|status}} elements, structural type elements, etc.). This datatype always describes FHIR specific terminology, which usually doesn't align with the HCIM/UCSD terminology.

In these cases, a mapping will be provided to explain the relationship between de HCIM/UCSD terminology and the FHIR terminology. This is normally done through a FHIR [https://hl7.org/fhir/STU3/conceptmap.html ConceptMap], which can translate between the terminology used in the HCIM/UCSD, and the terminology that FHIR instances need to adhere to. When the ConceptMap {{fhir|.equivalence}} is not {{term|equal}} or {{term|equivalent}}, the original terminology from the HCIM/UCSD SHALL be communicated as well using the extension [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/StructureDefinition/code-specification code-specification] on the same element. It is recommended to use this extension in other situations as well. This allows unambiguous interpretation on the receiver end.

Example snippet from an {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance|title=AllergyIntolerance}} where both the FHIR terminology {{term|high}} and the SNOMED CT {{term|24484000}} terminology are communicated. The FHIR terminology is obtained from the HCIM terminology using ConceptMap {{Simplifier|http://nictiz.nl/fhir/ConceptMap/MateVanKritiekZijnCodelijst-to-allergy-intolerance-criticality|title=MateVanKritiekZijnCodelijst-to-allergy-intolerance-criticality}}:

<syntaxhighlight lang="xml">
<criticality value="high">
<extension url="http://nictiz.nl/fhir/StructureDefinition/code-specification">
<valueCodeableConcept>
<coding>
<system value="http://snomed.info/sct"/>
<code value="24484000"/>
<display value="Severe"/>
</coding>
</valueCodeableConcept>
</extension>
</criticality>
</syntaxhighlight>

'''Please note''': Unfortunately, FHIR doesn't have a core structured way for indicating which ConceptMaps to use. Instead, mappings are documented in the description of the element in the profile and/or specifically on the mapping description contained in the element.

To retrieve the indicated ConceptMap on Simplifier, the canonical url from the description needs to be used as search term. We are still examining ways to make this more user friendly, for example by using the [https://hl7.org/fhir/STU3/extension-11179-permitted-value-conceptmap.html extension for ConceptMaps], but that does not work unless various third party tooling is updated.

==Use of the reference datatype==
A key feature of FHIR is the ability of resources to reference each other. This is done using the [https://hl7.org/fhir/STU3/references.html#Reference {{datatype|Reference}} datatype]. This datatype supports two modes of referencing:
; [https://hl7.org/fhir/STU3/references.html#literal Literal references], using the {{fhir|.reference}} element: A relative or absolute REST endpoint containing {{fhir|.id}} of the referenced resource. In a Bundle context, this may also be a reference to a {{fhir|Bundle.resource.fullUrl}}.
; [https://hl7.org/fhir/references.html#logical Logical references], using the {{fhir|.identifier}} element: Meaning a match on the business identifier ({{fhir|.identifier}}) for the referenced resource, without specifying where to find the referenced resource. Note: confusingly, although this reference type is called "logical reference", it does ''not'' act on the "logical identifier" ({{fhir|.id}}) of resources.

The resource/profile will usually constrain which resources may be targeted from a given element. For example, {{fhir|Patient.generalPractitioner}} may point only to an Organization or Practitioner resource, and the nl-core-patient profile further restricts this to the nl-core-organization and nl-core-practitioner profiles{{ref|weakness-target-unavailable}}.

The basic requirements for using references in this context are:
* Either a literal or logical reference SHALL be specified, unless specified otherwise.
** Literal references are preferred over logical references when multiple target resource types/profiles may be used{{ref|weakness-unknown-type}}.
* Literal references SHALL be resolvable.
** External references SHALL be regarded in the same context as the resource itself. If the current security context is insufficient for retrieving the reference, then additional negotiation for appropriate privileges may be required.
** Relative references are preferred over absolute references.
* A short description of the target resource SHALL be included using the {{fhir|.display}} element.

''Note 1'': {{note|weakness-target-unavailable}}In some circumstances, the constraints om the target are too strict for the use case and the appropriate resource can't be referenced (examples are {{fhir|Encounter.participant}}, which cannot reference a PractitionerRole resource to provide context of the attending physician, and {{fhir|Media.operator}}, which cannot target Patient resources and thus doesn't recognize patient-generated Media). In such cases, the proper reference type is added using an extension within the element that is used to refer the other resource. Because some receiving systems may not be able to handle this extension, the {{fhir|.display}} on both the element itself and the extension SHOULD be populated with the same value.

''Note 2'': {{note|weakness-unknown-type}}There is a known weakness in the Reference datatype for FHIR STU3 which is fixed in FHIR R4: if the reference might have more than one type of resource as target, a receiving system cannot know what type is meant when only an identifier is provided.

==Relating FHIR profiles with their functional definitions==
All profiles have a traceable relationship with their functional counterpart(s) based on the element mapping mechanism in FHIR. This allows to:
# define one or more references from a FHIR profile to an external URL where the functional definition can be found
# define for each FHIR profile element to which concept ''within'' a functional definition it corresponds

The functional definition(s) underlying the profile can thus be resolved using the [https://hl7.org/fhir/STU3/structuredefinition-definitions.html#StructureDefinition.mapping {{fhir|StructureDefinition.mapping}}] metadata field of a profile. To relate a FHIR profile field to a concept from the functional description, the concept ID defined in the [https://hl7.org/fhir/STU3/dataelement-definitions.html#DataElement.mapping {{fhir|DataElement.mapping}}] can be used to look up the concept in the functional definition. It is possible that a single profile element refers concepts from multiple functional descriptions. Simplifier will show an overview of all the mappings for a FHIR profile on the dedicated 'mappings' tab, together with a clickable URL to the functional definition. In addition, on the 'overview' tab for each field the relevant mapping can be found.

For example, the profile nl-core-address defines a relationship with [https://simplifier.net/NictizSTU3-Zib2017/nl-core-address/~mappings with four functional definitions], one of which is [https://zibs.nl/wiki/AddressInformation-v1.0(2017EN) AddressInformation-v1.0(2017EN)]. This mapping is identified within the profile using 'hcim-addressinformation-v1.0-2017EN'. Looking at the {{fhir|Address.city}} element in this profile, one of the mappings is defined as 'hcim-addressinformation-v1.0-2017EN:NL-CM:20.5.3'. This reveals that this element implements (amongst others) the concept from the HCIM AddressInformation-v1.0(2017EN) described using ID 'NL-CM:20.5.3'.

==Profile use and declaration==
The implementation guides for the various information standards list the profiles to use for the FHIR resources. In the interest of interoperability it is important that, when using said information standard:
* Each resource SHALL be a valid instance of the applicable profile. Note that this applies not only to profiles listed directly in the IG, but also to profiles referred from/used by listed profiles.
* Each resource SHALL include the canonical URL of this profile in the {{fhir|meta.profile}} element. The canonical of compatible base or derived profiles MAY be included as well.

=={{fhir|Resource.text}} or "the narrative"==
The FHIR STU3 specification says instances SHOULD contain a human readable summary of the contained data, which can be used as fallback by the receiver. This human readable text is contained in the [https://hl7.org/fhir/STU3/domainresource-definitions.html#DomainResource.text {{fhir|.text}} element] with datatype [https://hl7.org/fhir/STU3/narrative.html {{datatype|Narrative}}]. This human readable text is often referred to as "the narrative".

This implementation guide has the following expectations regarding the use of narratives:
* Senders SHOULD provide a "clinically safe" ([[#"Clinically safe" narratives|see below]]) narrative of status {{term|extensions}} (preferred) or {{term|generated}} ([[#Narrative status|see below]]), unless:
** The resource does not support narratives. This is the case for resources that do not derive from DomainResource, like Binary.
** The resource is contained in another resource.
** It is explicitly documented in the information standard to do otherwise.
* Receiver SHALL support the narrative. Ignoring the narrative is considered passive support. Support for the narrative SHALL be in accordance with the status and explicitly documented use in the relevant information standard.
* Receiver SHALL NOT generically depend on presence of a clinically safe narrative as their only means to present data to users when an explicitly documented use case for status empty or additional exists. Also, using just the narrative you would not expect to produce graphs, support for medication alerts and other functionality.

==="Clinically safe" narratives===
Regarding the contents of the narrative, the [https://hl7.org/fhir/STU3/domainresource-definitions.html#DomainResource.text FHIR STU3 spec states] that:
<blockquote>The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative.</blockquote>
And for the Narrative datatype:
<blockquote>Structured data SHOULD NOT generally contain information of importance to human readers that is omitted from the narrative. Creators of FHIR resources should not assume that systems will render (or that humans will see) data that is not in the narrative.</blockquote>

The decision to what entails "clinically safe" information, is somewhat arbitrary. Guidelines for "clinically safe" inspired by the [https://hl7.org/fhir/STU3/w5.html FHIR W5 report]:
* If you only had the narrative: the intention and context should be clear to you.
* Who. Patient/subject, performer, author and/or other primary actors. Is this about family history or the actual patient.
* What. The topic for the resource is clear.
* When. Is this past, present, or future information.
* Why. What led up to the event. E.g. Condition, Referral that caused Encounter or Procedure.
* Where. Location of the event/action in the resource.
* Context. Relevant context as present as presented in the resource. status, Encounter, EpisodeOfCare, Diagnosis, Condition, BodySite.
* Rendering every identifier and/or code detail may not be necessary. {{fhir|Resource.text}} is for human assessment of the situation so emphasis should be on display text, representing identifier/code/system as relevant in the context.

Informal note: Producing a "clinically safe" narrative can be cumbersome. Various reference frameworks like [https://hapifhir.io/hapi-fhir/docs/model/narrative_generation.html HAPI] include a Narrative Generator of some sort.

===Narrative status===

Datatype {{datatype|Narrative}} [https://hl7.org/fhir/STU3/valueset-narrative-status.html defines different status codes] to indicate the origin of the narrative text. This implementation guide expects the most common use case to be the status {{term|extensions}}, which means that the narrative is generated entirely from the structured data and the extensions used. The reason for this is that most resources can have extension content defined on them. This status can still be used if a particular instance doesn't contain any extensions.

Alternatively, status {{term|generated}} may be used if the sender did not anticipate inclusion of regular extension content in the narrative.

'''Note''': for both status {{term|extensions}} and {{term|generated}}, all modifier extensions SHOULD be included in the narrative as they always affect the semantics.

Senders SHOULD NOT use the other possible statuses unless it is explicitly documented why, e.g. in an information standard. Receivers MAY choose to support narratives with status {{term|additional}}, which means that it holds information not contained in the structured data. Receivers - upon rendering narrative with status {{term|additional}} - SHOULD make it clear to the user that the information is a fragment, and not the entire thing, in some suitable way.

==Search==

===Search URLs and search parameters===
Each use case of the various information standards lists the search parameters to use for a client to query the relevant information on a server. Usually, this is done in the form of (a number of) search URL(s), although individual use cases may use some other form if necessary (for example, listing optional parameters). Regarding the search parameters, the following guidelines apply:

* Unless explicitly marked as optional, the listed search parameters are considered the minimum for a request, meaning that:
** All stated parameters and modifiers SHALL be supported both by clients and servers.
** All stated parameters and modifiers SHALL be used for searching as specified in the information standard.
* A client MAY use additional search parameters in the search (such as date-range) not defined in the information standard. These may serve to further constrain the result set.
* A server MAY ignore and MAY support additional search parameters. A server SHALL report the applied parameters [https://www.hl7.org/fhir/stu3/search.html#conformance in the self link] of the response and SHOULD provide additional information about the search process using an OperationOutcome in the search result Bundle (as an entry with {{fhir|search.mode}} set to {{term|outcome}}). A client MAY use the self link and/or OperationOutcome to inform the user, independently apply these filters to the result set, or take some other action.
* A server SHALL reject any search request that contains parameters suffixed by a modifier that the server does '''not''' support for that parameter. For example, if the server supports the name search parameter, but not the :exact modifier on the name, it should reject a search with the parameter {{fhir|1=name:exact=Bill}}, using an HTTP 400 error with an OperationOutcome with a clear error message.
* A server SHALL NOT return information that is out of scope for the defined use case or authorization, even if the request by the client is wider than the use case.
* Repeating search parameters constitute a logical AND. Repeating search parameter values constitute a logical OR. Where applicable, this will be described further in the implementation guide.
* The order of the search parameters is always irrelevant.

General guidance on the use of search parameters can be found [https://www.hl7.org/fhir/stu3/search.html in the FHIR specification].

====Search on date, number or quantity====
When a search parameter has a type of date, number or quantity, the request [https://www.hl7.org/fhir/stu3/search.html#prefix uses prefixes] to control the search behavior. Unless explicitly stated otherwise, the minimum set of supported prefixes for these types is {{fhir|eq}}, {{fhir|gt}}, {{fhir|lt}}, {{fhir|ge}} and {{fhir|le}}. For example:
GET [base]/Observation?date=ge2019-01-01&date=le2020-01-01
Searches on all Observation resources that have an {{fhir|.effective[x]}} between January 1, 2019 and January 1, 2020.

====The {{fhir|_lastUpdated}} search parameter====
Retrieving information that was added, changed, deleted relative to a date may be done using the search parameter {{fhir|_lastUpdated}}, which is available for any resource. Using the parameter {{fhir|_lastUpdated}}, a system may query for data that is ''new'' since a specified date. Any FHIR server is expected to support this parameter. More information can be found in [https://hl7.org/fhir/STU3/search.html#lastUpdated the section on {{fhir|_lastUpdated}}] in the FHIR specification.

An example search request is shown below.

<pre>GET [base]/Consent?category=http://snomed.info/sct|11291000146105&_lastUpdated=gt2018-10-01</pre>

This search finds all Consent resources with a category SNOMED code 11291000146105 that have been modified since Oct 1, 2018.

===Search results===
====Including referenced resources====
Servers may not support read interactions, but all references from search results need to be resolvable (see [[#Use of the reference datatype]]). Therefore servers MAY choose to include the referenced resources in the ''searchset'' Bundle, even if the client didn't use any <code>_include</code> parameters. These resources SHALL have <code>Bundle.entry.mode</code> set to "''include''". Servers SHOULD NOT use contained resources for this purpose.

====Paging====
Servers MAY use [https://www.hl7.org/fhir/stu3/search.html#count paging] for performance reasons. Client SHALL support this mechanism to prevent loss of information.

== Usage of the {{fhir|.id}} and {{fhir|.fullUrl}} elements in FHIR instances ==

=== {{fhir|.id}} versus {{fhir|.identifier}} ===
FHIR recognizes two fields that are used as identifier for instances: {{fhir|.id}} and {{fhir|.identifier}}. Although these are both identifiers, they are unrelated and serve a completely different purpose:
* {{fhir|.id}} is the logical identifier, or technical identifier, akin to the id-field in a database. It is used as a unique handle for every instance on a particular server, and is needed to construct the URL to the instance. As such, it is used for referring between resources. The {{fhir|.id}} has no further meaning outside of the server.
* {{fhir|.identifier}} is a business identifier, which usually has a meaning ''outside'' of the server. Examples are a registration number of a healthcare provider, a BSN or social security number for citizens, ISBNs for books, etc. Any instance may have multiple kinds of identifiers.

This section is about the {{fhir|.id}} field and more general about the concept of a logical/technical id to identify instances on a server. The usage of the {{fhir|.identifier}} field, i.e. the business identifier, cannot be described in general terms and will be dictated one a use-case basis by the particular profiles.

=== When is {{fhir|.id}} expected? ===

As stated above, the logical id is meant to uniquely identify instances on a particular server; it is a vital component when using FHIR within a RESTful context. So as a rule of thumb, the {{fhir|.id}} element should always be present when dealing with instances that have a logical id, thus with instances on a server. This means:
* When a client reads, updates or otherwise addresses an existing resource on a server, the {{fhir|.id}} element SHALL be populated in the request and response, and it SHALL match the id in the request URL.
* When a client sends a ''new'' instance to a server using a create operation, the <code>id</code> element is ''not'' expected to be present -- these new instances don't exist yet on the server, so a logical id has no meaning. However, the server SHALL assign a logical id and populate the {{fhir|.id}} element in the response. ''Note'': It is not strictly prohibited to populate the {{fhir|.id}} field when sending a new instance, but the server SHOULD ignore it.
* When a client performs a search on a server, all instances in the returned searchset Bundle SHOULD have the {{fhir|.id}} field populated. ''Note'': A server SHOULD try its best to create stable ids for the resources it serves. Omitting {{fhir|.id}} elements is strongly discouraged as it breaks the assumptions about RESTful behavior. However, a server that omits {{fhir|.id}}s is still considered conformant when the conditions below are met:
*# The server does not natively support logical ids, for example when it is a stateless middleware server that gets its input from a non-FHIR XIS backend.
*# ''And'' the use case doesn't require read / update / delete / patch support for any of the returned of referenced resources, as stated by the CapabilityStatement for the information standard.
*# ''And'' the server includes all referenced resources in the searchset Bundle (regardless of whether the client asked to do so). These resources refer to each other based on the fullUrl mechanism as described below.

=== Logical ids, {{fhir|.fullUrl}}s and references in Bundles ===

There are several FHIR operations, like searching or batch create operations, where multiple instances are placed together in a Bundle. These instances will usually contain references to each other. These internal references cannot be resolved simply by inspecting the {{fhir|.id}} element of every instance; it is not guaranteed that all instances have a logical id. Instead, Bundles allow an {{fhir|entry.fullUrl}} element for each instance which may be used for references. This is an additional mechanism to the logical id, not a replacement:
* The [[#When_is_id_expected.3F|guidelines above]] for populating the {{fhir|.id}} field still apply.
* If {{fhir|.id}} is present, {{fhir|.fullUrl}} SHALL correspond with it (see below).

{{fhir|.fullUrl}}s may be RESTful URLs, UUIDs or even OIDs, based on the situation (which may be mixed within the same Bundle):
; Instances with a logical id: If an instance can be accessed on the server using RESTful operations, the {{fhir|.id}} of that instance in the Bundle will be populated. The corresponding {{fhir|.fullUrl}} in this case SHALL be the absolute URL to the instance on the server.Instances within the Bundle may use relative references to each other, like they are on the same server. The FHIR machinery specifies how to find the matching instance based on the {{fhir|.fullUrl}}.
; Instances without a logical id: When instances are to be created on a server or when the server doesn't support reading individual instances, they don't have a logical id. When these id-less instances need to be referenced from within a Bundle, there are two alternatives:
:* UUIDs can be used as single-use ids that will change each time the Bundle is generated. The {{fhir|.fullUrl}} for the instance will be the UUID prefixed with <code><nowiki>urn:uuid:</nowiki></code>. <ref name="id-ambiguous">Some implementations may choose to populate the {{fhir|.id}} element with the unprefixed UUID or OID in cases when the {{fhir|.id}} field is expected, for example in searchset Bundles. The FHIR specification is ambiguous on the requirements to do so. For a long discussion on the topic, see [https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Confused.20about.20URN.20fullUrl's.20and.20resource.2Eid's chat.fhir.org].</ref>
:* OIDs can be used if the instance has an OID-based ''business'' identifier (i.e. the {{fhir|.identifier}} field), like the UZI number of a healthcare provider. The {{fhir|.fullUrl}} will be the OID prefixed with <code><nowiki>urn:oid:</nowiki></code><ref name="id-ambiguous"/><ref>The use of OIDs as id has some limitations:
* The {{fhir|.id}} has a maximum length of 64 characters, so only OIDs that contain less than 64 characters can be used.
* OID based ids are expected to be stable, just like RESTful ids. Different Bundle instances SHALL always use the same OID based ids.
* Some ''objects'' may have multiple OID based identifiers, like AGB and UZI for practitioners. Which one do you choose? And what happens when the UZI number becomes available after you've already used the AGB as {{fhir|.id}}?
* Specifically for HL7 V3 based backends: an HL7 V3 II datatype normally consists of a <code>@root</code> (OID) and an <code>@extension</code> (string). Concatenation of <code>@root</code> and <code>@extension</code> only yields a new OID if <code>@extension</code> is numeric. Other combinations of <code>@root.@extension</code>, may yield a valid {{fhir|.id}} (pattern <code>[A-Za-z0-9\-\.]{1,64}</code>), but may not be a valid OID. In this case it is no longer possible to create a {{fhir|.fullUrl}} consistent with the {{fhir|.id}} based the <nowiki>urn:oid:</nowiki> scheme.</ref>.
: Instances within the Bundle should use the prefixed version of the UUID/OID for referencing.

==== Example ====
Consider a client that wants to send a new Observation instance to a server and simultaneously link it to an existing Task instance. This can be done using a transaction Bundle:
<syntaxhighlight lang="xml" highlight="7-8,11,23-24,27-28,33-34,41-42" style="max-height:400px; overflow: auto;">
<Bundle xmlns="http://hl7.org/fhir">

<type value="transaction"/>


<entry>

<fullUrl value="urn:uuid:0e855422-b8ef-4247-9443-f3747e78747e"/>
<resource>
<Observation>

...
</Observation>
</resource>
</entry>
<request>
<method value="POST"/>
<url value="Observation"/>
</request>


<entry>

<fullUrl value="http://example-xis.com/Task/1234"/>
<resource>
<Task>

<id value="1234"/>
...
<output>
...
<valueReference>

<reference value="urn:uuid:0e855422-b8ef-4247-9443-f3747e78747e"/>
</valueReference>
</output>
</Task>
</resource>
<request>
<method value="PUT"/>

<url value="Task/1234"/>
</request>
</entry>
</Bundle>
</syntaxhighlight>

The server response should then look like:
<syntaxhighlight lang="xml" highlight="5-6,9-10,28-29" style="max-height:400px; overflow: auto;">
<Bundle xmlns="http://hl7.org/fhir">
<type value="transaction-response"/>

<entry>

<fullUrl value="http://example-xis.com/QuestionnaireResponse/5678"/>
<resource>
<Observation>

<id value="5678"/>
...
</Observation>
</resource>
</entry>
<response>
....
</request>

<entry>
<fullUrl value="http://example-xis.com/Task/1234"/>
<resource>
<Task>
<id value="1234"/>
...
<output>
...
<valueReference>

<reference value="Observation/5678"/>
</valueReference>
</output>
</Task>
</resource>
<response>
....
</response>
</entry>
</Bundle>
</syntaxhighlight>

== Handling errors==
Errors in FHIR interactions are usually communicated using the combination of an appropriate HTTP status code in the 4xx-5xx range, and an [https://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] resource providing more details regarding the error. The OperationOutcome resource contains mandatory elements to indicate the overall type and severity of the error (respectively {{fhir|.code}} and {{fhir|.severity}}) and MAY express the location (using {{fhir|.location}} or {{fhir|.expression}}) and a free-form or coded description of the error (using the {{fhir|.diagnostics}} or {{fhir|.detail}} element). Although these latter elements are not required, their usage is strongly encouraged.

For the most common errors, the expected handling is listed in table [xxx] below. This should be interpreted as a guideline, as the nature of an error is not always unambiguous and various FHIR reference implementations will make different choices. The FHIR specification provides more detail [https://www.hl7.org/fhir/stu3/http.html on error handling in general], [https://www.hl7.org/fhir/stu3/security.html#AccessDenied access denied responses] and [https://www.hl7.org/fhir/stu3/search.html#errors for search operations specifically].

In general, most FHIR-related errors (in addition to normal HTTP errors related to security, header and content type negotiation issues) will result in one of these HTTP status codes:
* 400 Bad Request - resource could not be parsed, search could not be processed or basic FHIR validation rules failed
* 403 Forbidden - the server was unable to execute the search, due to an authorization failure
* 404 Not Found - resource type not supported, or not an FHIR endpoint
* 422 Unprocessable Entity - the proposed resource violated applicable FHIR profiles or server business rules

{| class="wikitable"
|-
! Interaction
! Error
! Expected action
! Example
|-
| rowspan=2 |All
| Invalid authorization
|
* HTTP 403 Forbidden
* OperationOutcome with <code>code</code> set to "''security''"
| [[FHIR:Vprepub-1.0 FHIR_Error_handling_examples#Invalid_authorization Example|Example]]
|-
| Resource is not supported
|
* HTTP 404 Not Found
* OperationOutcome with {{fhir|.code}} set to {{term|not-supported}}
| [[FHIR:Vprepub-1.0 FHIR_Error_handling_examples#Resource_is_not_supported|Example]]
|-
| rowspan=4 |search
| No match for the given search parameters
| colspan="2" |''This is not considered an error, but a normal search without results.''
|-
| Unknown search parameter
| colspan="2" | ''This is not considered an error. See the [[#unknown_search_parameter_handling|guidance in the section on searching]].''
|-
| Syntactically incorrect parameter
|
* HTTP 400 Bad Request
* OperationOutcome. There are various issue type codes that could be used, depending on the nature of the error
| [[FHIR:Vprepub-1.0 FHIR_Error_handling_examples#Syntactically_incorrect_parameter|Example]]
|-
| Known but unsupported value. This situation applies to non-supported HCIM profiles when the Resource endpoint itself is supported.
|
* HTTP 200 OK
* Empty Bundle of {{fhir|.type}} {{term|searchset}}
* OperationOutcome in Bundle as an entry marked with {{fhir|Bundle.entry.search.mode}} of {{term|outcome}}.
* OperationOutcome with {{fhir|.code}} set to {{term|not-found}} and {{fhir|.severity}} not set to {{term|fatal}} or {{term|error}}.
| [[FHIR:Vprepub-1.0 FHIR_Error_handling_examples#Unkown_or_unsupported_search_parameter_value|Example]]
|-
| read
| Read request with unknown id
|
* HTTP 404 Not Found
* OperationOutcome with {{fhir|.code}} set to {{term|not-found}}
| [[FHIR:Vprepub-1.0 FHIR_Error_handling_examples#Request_on_an_unknown_id|Example]]
|-
| update
| No or incorrect Resource id
|
* HTTP 400 Bad Request
* OperationOutcome with {{fhir|.code}} set to {{term|invalid}}
| [[FHIR:Vprepub-1.0 FHIR_Error_handling_examples#No_or_incorrect_Resource_id|Example]]
|-
| create/update
| Resource syntax or data is incorrect or invalid
|
* HTTP 400 Bad Request or HTTP 422 Unprocessable Entity
* OperationOutcome with {{fhir|.code}} set to {{term|invalid}} or preferably a more specific child code.
| [[FHIR:Vprepub-1.0 FHIR_Error_handling_examples#Resource_syntax_or_data_is_incorrect_or_invalid|Example]]
|}
<section end=OverarchingPrinciples />
<section begin=FHIRPackages />

==CapabilityStatements==
Information standards may have a [https://www.hl7.org/fhir/stu3/capabilitystatement.html CapabilityStatement] that is informative in nature and does not represent the minimum or maximum set of capabilities the client or server should support. Nictiz will strive to provide CapabilityStatements that are as complete as possible, however for the exact set of capabilities the implementation guide of the corresponding information standard should be consulted.

=FHIR Packages=
The information standards maintained by Nictiz adopt the FHIR Packaging mechanism to support consistent versioning of profiles and related conformance resources such as OperationDefinitions. FHIR Packaging is based on the NPM Packaging mechanism and offers developers a convenient way to include the conformance resources in their favorite IDE. The relevant package version is indicated and linked in the information standards technical design page.

Please note that every effort has been made to ensure that the examples contained in the packages are correct and useful, but they are not a normative part of any information standard.

For even more background information:
* [https://confluence.hl7.org/display/FHIR/NPM+Package+Specification The HL7 base specification for FHIR pacakges]
* [https://blog.fire.ly/2017/11/28/versioning-and-canonical-urls/ What is the problem that packaging could address]
* [https://simplifier.net/organization/firely/news/55 Introducing the Simplifier FHIR Package Server] (includes what problem packaging addresses)
* [https://simplifier.net/organization/firely/news/56 Firely Torinox introduction] (this is one of the tools that's useful for working with FHIR packages)

{{NoteBox|It is '''not''' required to implement FHIR based information standards using the packaging mechanism. It is still possible to download all or selected resources from Simplifier on as-needed basis. You are however encouraged to invest in dealing with packages.}}
<section end=FHIRPackages />

FHIR:Vprepub-1.0 FHIR IG STU3

2021-04-22T08:01:03Z

Stephan Opdenberg: MM-1795 Added CapabilityStatement description

Gebz:V2.3 transaction beschikbaarstellen gegevens zwangerschapskaart

2021-04-16T09:15:26Z

Stephan Opdenberg:

=Addendum Beschikbaarstellen gegevens Zwangerschapskaart=
{{IssueBox|Generated code, do not change by hand}}
=beschikbaarstellen_gegevens_zwangerschapskaart=
<section begin=transaction />
{| class="wikitable"
| style="background-color: #1F497D;; color: white; font-weight: bold; text-align:center;" colspan="13" | PWD 2.3 to FHIR
|-style="background-color: #1F497D;; color: white; text-align:left;"
|style="width:30px;"| Type
|style="width:10px;"| #
||Concept
|style="width:40px;"| Card
|| Profile
|| Mapping
|| Example
|| Search URL
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||4
||Zorgverlening
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20290
||   Datum start zorgverantwoordelijkheid
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.start
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20340
||   Datum einde zorgverantwoordelijkheid
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.end
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||1
||Zorgverlener/Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization | nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization | nl-core-practitioner}}
||Organization | Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10001
||   Zorgverlener
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
* GET [base]/Practitioner/[zorgverlenerid]
* GET [base]/Practitioner?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10002
||      Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10003
||      Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10006
||      Naam zorgverlener
||1 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10010
||      Zorgverlenertype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty
||[https://simplifier.net/geboortezorg-stu3/practitionerrole-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10012
||      Telefoon waar zorgverlener is te bereiken
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.telecom
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10020
||   Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
* GET [base]/Organization/[zorginstellingid]
* GET [base]/Organization?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10021
||      Zorginstelling OID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10022
||      Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10023
||      Zorginstelling LVR-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10024
||      Zorginstelling URA
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10026
||      Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10027
||      Adres zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10032
||         Straatnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10033
||         Huisnummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10034
||         Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10041
||         Postcode
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10036
||         Plaatsnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.city
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10037
||         Gemeentenaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.district
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10038
||         Land
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.country
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10039
||         Adrestype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.extension:AddressType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10029
||      Type zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82019
||      Type zorginstelling (bij verwijzing)
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationTypee
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||2
||Vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
* GET [base]/Patient/[vrouwid]
* GET [base]/Patient?identifier=[bsn]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10031
||   Lokale persoonsidentificatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10035
||   Naamgegevens
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10042
||      Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82359
||      Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82360
||      Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82361
||      Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82362
||         Soort naam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82363
||         Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10043
||         Achternaam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10040
||   Geboortedatum
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.birthdate
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10300
||   Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10301
||      Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10302
||      Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10303
||      Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10304
||      Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10305
||      Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.city
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10306
||      Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.district
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10307
||      Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.country
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10308
||      Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.type
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82694
||   Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82695
||      Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82696
||         Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82697
||         TelecomType
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82698
||         NummerSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82699
||      EmailAdressen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82700
||         EmailAdres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82701
||         EmailSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80649
||   Betrokken zorgverlener/zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner/nl-core-organization}}
||Practitioner/Organization
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82022
||      Huisarts
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82027
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82028
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82029
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82023
||      Apotheek
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82030
||         Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82031
||         Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name.text
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82024
||      Specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82039
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82032
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82033
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82038
||         Type specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty.text
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82035
||         Zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82036
||            Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82037
||            Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10801
||   Medicatiegebruik?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-150 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80749
||   Medicatiegebruik
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10802
||      Soort medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|zib-Product|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse|zib-Product}}
||MedicationStatement.medicationReference|Medication.code.text
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80751
||      Begindatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.start
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80752
||      Einddatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.end
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80750
||      Dosering medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.dosage.doseQuantity
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80753
||      Bijzonderheden
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.note
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80688
||   BMI
||0 .. 1
||
||
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80689
||      Datum bepaling
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10806
||      BMI vrouw
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-120 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80675
||   Vrouwelijke genitale verminking?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-177 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80676
||   Type vrouwelijke genitale verminking
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-172 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10807
||   Actuele bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10808
||      Actuele bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10809
||      Actuele bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10810
||   Bloedgroep vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-79 example]
||
* GET [base]/Observation?code=883-9{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10811
||   Rhesus D Factor vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
* GET [base]/Observation?code=1305-2{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10816
||   Rhesus c Factor
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-82 example]
||
* GET [base]/Observation?code=1159-3{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80633
||   Partner
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80638
||      Persoonsnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80639
||         Voornamen
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.given
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80640
||         Voorvoegsel
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.family
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80641
||         Achternamen
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.family
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80636
||      Etniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||17
||Obstetrische anamnese gegroepeerd per voorgaande zwangerschap
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy}}
||Condition
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||18
||   Eerdere bevalling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||19
||      Vorige uitkomst (per kind)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80709
||         Vorige baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80710
||            Werkelijke plaats baring (type locatie)
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||21
||            Kindspecifieke gegevens vorige uitkomsten
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80624
||               Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||3
||Zwangerschap
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy}}
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
* GET [base]/Condition/[zwangerschapid]
* GET [base]/Condition?clinicalstatus=active
* GET [base]/Condition?clinicalstatus=inactive&_sort=_-id&_count=1
* GET [base]/Condition?subject=[patientid]&_revinclude=Observation:focus
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80664
||   Casemanager naam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.careManager.display
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20010
||   Graviditeit
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Gravidity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Gravidity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-84 example]
||
* GET [base]/Observation?code=11996-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20150
||   Pariteit (vóór deze zwangerschap)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Parity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Parity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-88 example]
||
* GET [base]/Observation?code=11977-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80617
||   Aantal levende kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-112 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80678
||   Fetal Loss
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20029
||   A terme datum (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20030
||      A terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20040
||      Datum bepaling à terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20050
||      A terme datum o.b.v.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.method
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82160
||   Definitieve à terme datum
||0 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-263 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80819
||   Foliumzuur gebruik
||0 .. 1
||
||
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20020
||   Hoeveelling
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20130
||   Amnioniciteit
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20140
||   Chorioniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80732
||   Prenatale controle
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80737
||      Datum controle
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter.period.start
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80736
||      Naam zorgverlener
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.display | Practitioner.name
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82067
||      Zorgverlenertype
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.extension:practitionerRole.specialty | PractitionerRole.specialty
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80738
||      Zwangerschapsduur
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80746
||      Leven voelen
||1 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-144 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80810
||      Rookgedrag
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TobaccoUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-TobaccoUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-191 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80747
||      Alcoholgebruik
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AlcoholUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-AlcoholUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-189 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82102
||      Drugsgebruik?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-190 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82103
||      Soort drugs
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.component:DrugOrMedicationType.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-190 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80832
||      Bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80833
||         Bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:SystolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80834
||         Bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:DiastolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20211
||      Gewicht (gemeten)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyWeight}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-187 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80621
||      Uitwendig onderzoek
||1 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82105
||         Hartactie
||1 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82106
||            Regelmaat hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82107
||            Frequentie hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80745
||         Hartactie op basis van
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82268
||   Diagnose
||0 .. *
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82272
||      Datum
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-21 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82285
||      Zwangerschapsduur
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82269
||      Gynaecologische aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82270
||      Bloedverlies?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-17 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82286
||      Partiële mola?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-35 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82271
||      Cervixinsufficiëntie?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-18 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82273
||      Infectie
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-29 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82274
||      Hyperemesis gravidarum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-27 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82275
||      Hypertensieve aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-28 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82276
||      Zwangerschapscholestase?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-14 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82277
||      Diabetes gravidarum met insuline?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-22 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82278
||      Afwijkende groei foetus
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-16 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82279
||      Dreigende partus immaturus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-23 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82280
||      Dreigende partus prematurus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-24 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82289
||      Abruptio placentae?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-15 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82452
||      Navelstrengprolaps?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-32 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82380
||      Liggingsafwijking
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-31 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||83405
||      Meerlingzwangerschap?
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||84193
||      Serotiniteit?
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80613
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82435
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82377
||   Interventie
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82376
||      Interventie
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82230
||   Intra-uteriene behandeling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||6
||Bevalling
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
* GET [base]/Procedure?code=236973005{&subject=[vrouwid]&context=[dossierid]&reasonReference=[zwangerschapid]}
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20500
||   Partusnummer
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.identifier
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82291
||   Diagnose bevalling
||1 .. *
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82381
||      Datum
||1 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82382
||      Zwangerschapsduur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82338
||      PPROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-37 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82290
||      PROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-39 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82292
||      Koorts?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-30 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82293
||      Niet vorderende ontsluiting?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-33 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82294
||      Niet vorderende uitdrijving?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-34 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82296
||      Verdenking foetale nood?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82443
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82444
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82295
||      Vastzittende placenta?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-42 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82398
||      Fluxus postpartum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20505
||   Aantal geboren kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-111 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20555
||   Interventies begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20560
||      Interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20570
||      Indicatie interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20550
||   Wijze waarop de baring begon
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-178 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20590
||   Tijdstip begin actieve ontsluiting
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-63 example]
||
* GET [base]/Observation?code=249120008{&subject=[vrouwid]&context=[dossierid]&focus=[bevallingid]}
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||7
||Uitkomst (per kind)
||0 .. *
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40002
||   Baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
* GET [base]/Procedure?code=3950001{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]&focus=[kindid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40003
||      Werkelijke plaats baring (type locatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ChildBirthAssistance|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ChildBirthAssistance}}
||Encounter.class:werkelijkePlaatsBaring
||[https://simplifier.net/geboortezorg-stu3/encounter-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40006
||      Demografische gegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient
||
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40007
||         Identificaties kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40010
||            BSN kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier:BSN
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40011
||            Lokale identificatie kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40015
||            Identificatie kind PRN formaat
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82051
||         Naamgegevens kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82353
||            Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82354
||            Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82052
||            Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82053
||            Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82054
||               Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannamePrefix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82055
||               Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannameOwnName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82364
||         Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82365
||            Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82366
||               Soort telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.use
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82367
||               Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40032
||         Adres t.b.v. hielprik
||0 .. 1
||
||
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82133
||            Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:streetName
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82134
||            Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:houseNumber
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82135
||            Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:buildingNumbersuffix
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82136
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82137
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patientaddress.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82138
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.country
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82139
||            Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.extension:AddressType
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40033
||         Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40034
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40040
||         Geslacht (administratief)
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40041
||         Geslacht (medische observatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.gender.Extension
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40050
||         Geboortedatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.birthdate & patient.birthtime (extension)
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40004
||         Geboorteplaats
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80629
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80630
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80631
||            Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.district
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80632
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension.birthPlace.country
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82087
||         Meerlingindicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthBoolean
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40025
||         Rangnummer kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthInteger
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||71
||      Kindspecifieke maternale gegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20616
||         Bijstimulatie toegediend?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-6 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20579
||         Amniotomie (groep)
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20580
||            Amniotomie?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80794
||         Indicatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||30055
||         Locatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.bodySite.extension
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82090
||         Pijnbestrijding?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82091
||         Pijnbestrijding
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82394
||            Datum/tijd
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.effectiveDateTime
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82093
||            Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82092
||               Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82094
||               Overig middel
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.route
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82095
||                  Middel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.medicationCodeableConcept
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||72
||      Kindspecifieke uitkomstgegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80626
||         Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCode
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
* GET [base]/Observation?code=364336006{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40189
||         Vaginale kunstverlossing (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40190
||            Vaginale kunstverlossing
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
* GET [base]/Procedure?code=3311000146109{&subject=[vrouwid]&context=[dossierid]&partof=[bevallingid,uitdrijvingsfaseid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40210
||            Indicatie vaginale kunstverlossing
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40219
||         Sectio caesarea (group)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82546
||            Indicatie primaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82547
||            Indicatie secundaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80766
||         Lichamelijk onderzoek kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PhysicalExamination|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PhysicalExamination}}
||DiagnosticReport
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40070
||            Apgarscore na 1 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40071
||            Apgarscore na 5 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-77 example]
||
* GET [base]/Observation?code=9274-2{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80757
||            Apgarscore na 10 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40060
||            Geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-180 example]
||
* GET [base]/Observation?code=8339-4{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80670
||            Percentiel van het geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.interpretation.extension:percentile
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-185 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80759
||            Lengte
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyHeight}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80760
||            Schedelomtrek
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HeadCircumference|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-HeadCircumference}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||14
||Medisch onderzoek
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||50020
||   Datum onderzoek
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||142
||   Maternale onderzoeksgegevens
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80959
||      Urine-, bloed- en aanvullende onderzoeken
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80949
||         PSIE
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80952
||            Bloedgroep vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80953
||            Rhesus D Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80954
||            Rhesus c Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80955
||            HBsAg
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80956
||            HIV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80957
||            Lues
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10812
||            Irregulaire antistoffen?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-181 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10813
||            Welke irregulaire antistoffen vrouw aanwezig.
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-260 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10814
||         Hb
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-80 example]
||
* GET [base]/Observation?code=718-7{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80991
||         Anemie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80951
||            MCV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80992
||            Hb-pathie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Problem}}
||Condition.code
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80993
||            Vit. B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80994
||            Actief-B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80995
||            Ferritine
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80996
||            Foliumzuur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80963
||         Schildklier diagnostiek
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80962
||            TSH receptor antistoffen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80964
||            Vrij T4
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80965
||            TSH
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80966
||         TORCH
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80967
||            Toxoplasmose IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80968
||            Toxoplasmose IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80969
||            Rubella IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80970
||            Rubella IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80971
||            CMV IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80972
||            CMV IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80973
||            Herpes IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80974
||            Herpes IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80975
||            Parvovirus IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80976
||            Parvovirus IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40051
||         Rhesus D Factor foetus
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
|}
<section end=transaction />

Gebz:V2.3 transaction beschikbaarstellen gegevens zwangerschapskaart

2021-04-16T07:57:50Z

Stephan Opdenberg:

=Addendum Beschikbaarstellen gegevens Zwangerschapskaart=
{{IssueBox|Generated code, do not change by hand}}
=beschikbaarstellen_gegevens_zwangerschapskaart=
<section begin=transaction />
{| class="wikitable"
| style="background-color: #1F497D;; color: white; font-weight: bold; text-align:center;" colspan="13" | PWD 2.3 to FHIR
|-style="background-color: #1F497D;; color: white; text-align:left;"
|style="width:30px;"| Type
|style="width:10px;"| #
||Concept
|style="width:40px;"| Card
|| Profile
|| Mapping
|| Example
|| Search URL
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||4
||Zorgverlening
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20290
||   Datum start zorgverantwoordelijkheid
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.start
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20340
||   Datum einde zorgverantwoordelijkheid
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.end
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||1
||Zorgverlener/Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization | nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization | nl-core-practitioner}}
||Organization | Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10001
||   Zorgverlener
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
* GET [base]/Practitioner/[zorgverlenerid]
* GET [base]/Practitioner?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10002
||      Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10003
||      Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10006
||      Naam zorgverlener
||1 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10010
||      Zorgverlenertype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty
||[https://simplifier.net/geboortezorg-stu3/practitionerrole-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10012
||      Telefoon waar zorgverlener is te bereiken
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.telecom
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10020
||   Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
* GET [base]/Organization/[zorginstellingid]
* GET [base]/Organization?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10021
||      Zorginstelling OID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10022
||      Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10023
||      Zorginstelling LVR-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10024
||      Zorginstelling URA
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10026
||      Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10027
||      Adres zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10032
||         Straatnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10033
||         Huisnummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10034
||         Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10041
||         Postcode
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10036
||         Plaatsnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.city
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10037
||         Gemeentenaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.district
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10038
||         Land
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.country
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10039
||         Adrestype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.extension:AddressType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10029
||      Type zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82019
||      Type zorginstelling (bij verwijzing)
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationTypee
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||2
||Vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
* GET [base]/Patient/[vrouwid]
* GET [base]/Patient?identifier=[bsn]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10031
||   Lokale persoonsidentificatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10035
||   Naamgegevens
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10042
||      Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82359
||      Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82360
||      Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82361
||      Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82362
||         Soort naam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82363
||         Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10043
||         Achternaam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10040
||   Geboortedatum
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.birthdate
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10300
||   Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10301
||      Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10302
||      Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10303
||      Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10304
||      Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10305
||      Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.city
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10306
||      Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.district
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10307
||      Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.country
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10308
||      Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.type
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82694
||   Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82695
||      Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82696
||         Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82697
||         TelecomType
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82698
||         NummerSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82699
||      EmailAdressen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82700
||         EmailAdres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82701
||         EmailSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80649
||   Betrokken zorgverlener/zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner/nl-core-organization}}
||Practitioner/Organization
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82022
||      Huisarts
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82027
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82028
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82029
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82023
||      Apotheek
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82030
||         Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82031
||         Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name.text
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82024
||      Specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82039
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82032
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82033
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82038
||         Type specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty.text
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82035
||         Zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82036
||            Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82037
||            Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10801
||   Medicatiegebruik?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-150 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80749
||   Medicatiegebruik
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10802
||      Soort medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|zib-Product|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse|zib-Product}}
||MedicationStatement.medicationReference|Medication.code.text
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80751
||      Begindatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.start
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80752
||      Einddatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.end
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80750
||      Dosering medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.dosage.doseQuantity
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80753
||      Bijzonderheden
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.note
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80688
||   BMI
||0 .. 1
||
||
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80689
||      Datum bepaling
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10806
||      BMI vrouw
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-120 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80675
||   Vrouwelijke genitale verminking?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-177 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80676
||   Type vrouwelijke genitale verminking
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-172 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10807
||   Actuele bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10808
||      Actuele bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10809
||      Actuele bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10810
||   Bloedgroep vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-79 example]
||
* GET [base]/Observation?code=883-9{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10811
||   Rhesus D Factor vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
* GET [base]/Observation?code=1305-2{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10816
||   Rhesus c Factor
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-82 example]
||
* GET [base]/Observation?code=1159-3{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80633
||   Partner
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80638
||      Persoonsnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80639
||         Voornamen
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.given
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80640
||         Voorvoegsel
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.family
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80641
||         Achternamen
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.family
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80636
||      Etniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||17
||Obstetrische anamnese gegroepeerd per voorgaande zwangerschap
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy}}
||Condition
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||18
||   Eerdere bevalling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||19
||      Vorige uitkomst (per kind)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80709
||         Vorige baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80710
||            Werkelijke plaats baring (type locatie)
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||21
||            Kindspecifieke gegevens vorige uitkomsten
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80624
||               Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||3
||Zwangerschap
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy}}
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
* GET [base]/Condition/[zwangerschapid]
* GET [base]/Condition?clinicalstatus=active
* GET [base]/Condition?clinicalstatus=inactive&_sort=_-id&_count=1
* GET [base]/Condition?subject=[patientid]&_revinclude=Observation:focus
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80664
||   Casemanager naam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.careManager.display
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20010
||   Graviditeit
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Gravidity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Gravidity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-84 example]
||
* GET [base]/Observation?code=11996-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20150
||   Pariteit (vóór deze zwangerschap)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Parity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Parity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-88 example]
||
* GET [base]/Observation?code=11977-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80617
||   Aantal levende kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-112 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80678
||   Fetal Loss
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20029
||   A terme datum (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20030
||      A terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20040
||      Datum bepaling à terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20050
||      A terme datum o.b.v.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.method
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82160
||   Definitieve à terme datum
||0 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-263 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80819
||   Foliumzuur gebruik
||0 .. 1
||
||
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20020
||   Hoeveelling
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20130
||   Amnioniciteit
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20140
||   Chorioniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80732
||   Prenatale controle
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80737
||      Datum controle
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter.period.start
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80736
||      Naam zorgverlener
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.display | Practitioner.name
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82067
||      Zorgverlenertype
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.extension:practitionerRole.specialty | PractitionerRole.specialty
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80738
||      Zwangerschapsduur
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80746
||      Leven voelen
||1 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-144 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80810
||      Rookgedrag
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TobaccoUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-TobaccoUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-191 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80747
||      Alcoholgebruik
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AlcoholUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-AlcoholUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-189 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82102
||      Drugsgebruik?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-190 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82103
||      Soort drugs
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.component:DrugOrMedicationType.valueCodeableConcept
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80832
||      Bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80833
||         Bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:SystolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80834
||         Bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:DiastolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20211
||      Gewicht (gemeten)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyWeight}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-187 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80621
||      Uitwendig onderzoek
||1 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82105
||         Hartactie
||1 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82106
||            Regelmaat hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82107
||            Frequentie hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80745
||         Hartactie op basis van
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82268
||   Diagnose
||0 .. *
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82272
||      Datum
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-21 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82285
||      Zwangerschapsduur
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82269
||      Gynaecologische aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82270
||      Bloedverlies?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-17 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82286
||      Partiële mola?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-35 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82271
||      Cervixinsufficiëntie?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-18 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82273
||      Infectie
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-29 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82274
||      Hyperemesis gravidarum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-27 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82275
||      Hypertensieve aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-28 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82276
||      Zwangerschapscholestase?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-14 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82277
||      Diabetes gravidarum met insuline?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-22 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82278
||      Afwijkende groei foetus
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-16 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82279
||      Dreigende partus immaturus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-23 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82280
||      Dreigende partus prematurus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-24 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82289
||      Abruptio placentae?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-15 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82452
||      Navelstrengprolaps?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-32 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82380
||      Liggingsafwijking
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-31 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||83405
||      Meerlingzwangerschap?
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||84193
||      Serotiniteit?
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80613
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82435
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82377
||   Interventie
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82376
||      Interventie
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82230
||   Intra-uteriene behandeling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||6
||Bevalling
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
* GET [base]/Procedure?code=236973005{&subject=[vrouwid]&context=[dossierid]&reasonReference=[zwangerschapid]}
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20500
||   Partusnummer
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.identifier
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82291
||   Diagnose bevalling
||1 .. *
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82381
||      Datum
||1 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82382
||      Zwangerschapsduur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82338
||      PPROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-37 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82290
||      PROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-39 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82292
||      Koorts?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-30 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82293
||      Niet vorderende ontsluiting?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-33 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82294
||      Niet vorderende uitdrijving?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-34 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82296
||      Verdenking foetale nood?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82443
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82444
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82295
||      Vastzittende placenta?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-42 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82398
||      Fluxus postpartum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20505
||   Aantal geboren kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-111 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20555
||   Interventies begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20560
||      Interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20570
||      Indicatie interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20550
||   Wijze waarop de baring begon
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-178 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20590
||   Tijdstip begin actieve ontsluiting
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-63 example]
||
* GET [base]/Observation?code=249120008{&subject=[vrouwid]&context=[dossierid]&focus=[bevallingid]}
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||7
||Uitkomst (per kind)
||0 .. *
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40002
||   Baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
* GET [base]/Procedure?code=3950001{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]&focus=[kindid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40003
||      Werkelijke plaats baring (type locatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ChildBirthAssistance|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ChildBirthAssistance}}
||Encounter.class:werkelijkePlaatsBaring
||[https://simplifier.net/geboortezorg-stu3/encounter-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40006
||      Demografische gegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient
||
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40007
||         Identificaties kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40010
||            BSN kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier:BSN
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40011
||            Lokale identificatie kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40015
||            Identificatie kind PRN formaat
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82051
||         Naamgegevens kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82353
||            Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82354
||            Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82052
||            Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82053
||            Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82054
||               Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannamePrefix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82055
||               Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannameOwnName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82364
||         Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82365
||            Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82366
||               Soort telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.use
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82367
||               Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40032
||         Adres t.b.v. hielprik
||0 .. 1
||
||
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82133
||            Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:streetName
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82134
||            Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:houseNumber
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82135
||            Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:buildingNumbersuffix
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82136
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82137
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patientaddress.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82138
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.country
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82139
||            Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.extension:AddressType
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40033
||         Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40034
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40040
||         Geslacht (administratief)
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40041
||         Geslacht (medische observatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.gender.Extension
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40050
||         Geboortedatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.birthdate & patient.birthtime (extension)
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40004
||         Geboorteplaats
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80629
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80630
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80631
||            Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.district
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80632
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension.birthPlace.country
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82087
||         Meerlingindicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthBoolean
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40025
||         Rangnummer kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthInteger
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||71
||      Kindspecifieke maternale gegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20616
||         Bijstimulatie toegediend?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-6 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20579
||         Amniotomie (groep)
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20580
||            Amniotomie?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80794
||         Indicatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||30055
||         Locatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.bodySite.extension
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82090
||         Pijnbestrijding?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82091
||         Pijnbestrijding
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82394
||            Datum/tijd
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.effectiveDateTime
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82093
||            Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82092
||               Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82094
||               Overig middel
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.route
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82095
||                  Middel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.medicationCodeableConcept
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||72
||      Kindspecifieke uitkomstgegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80626
||         Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCode
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
* GET [base]/Observation?code=364336006{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40189
||         Vaginale kunstverlossing (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40190
||            Vaginale kunstverlossing
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
* GET [base]/Procedure?code=3311000146109{&subject=[vrouwid]&context=[dossierid]&partof=[bevallingid,uitdrijvingsfaseid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40210
||            Indicatie vaginale kunstverlossing
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40219
||         Sectio caesarea (group)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82546
||            Indicatie primaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82547
||            Indicatie secundaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80766
||         Lichamelijk onderzoek kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PhysicalExamination|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PhysicalExamination}}
||DiagnosticReport
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40070
||            Apgarscore na 1 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40071
||            Apgarscore na 5 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-77 example]
||
* GET [base]/Observation?code=9274-2{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80757
||            Apgarscore na 10 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40060
||            Geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-180 example]
||
* GET [base]/Observation?code=8339-4{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80670
||            Percentiel van het geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.interpretation.extension:percentile
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-185 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80759
||            Lengte
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyHeight}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80760
||            Schedelomtrek
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HeadCircumference|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-HeadCircumference}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||14
||Medisch onderzoek
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||50020
||   Datum onderzoek
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||142
||   Maternale onderzoeksgegevens
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80959
||      Urine-, bloed- en aanvullende onderzoeken
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80949
||         PSIE
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80952
||            Bloedgroep vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80953
||            Rhesus D Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80954
||            Rhesus c Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80955
||            HBsAg
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80956
||            HIV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80957
||            Lues
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10812
||            Irregulaire antistoffen?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-181 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10813
||            Welke irregulaire antistoffen vrouw aanwezig.
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-260 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10814
||         Hb
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-80 example]
||
* GET [base]/Observation?code=718-7{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80991
||         Anemie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80951
||            MCV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80992
||            Hb-pathie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Problem}}
||Condition.code
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80993
||            Vit. B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80994
||            Actief-B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80995
||            Ferritine
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80996
||            Foliumzuur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80963
||         Schildklier diagnostiek
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80962
||            TSH receptor antistoffen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80964
||            Vrij T4
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80965
||            TSH
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80966
||         TORCH
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80967
||            Toxoplasmose IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80968
||            Toxoplasmose IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80969
||            Rubella IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80970
||            Rubella IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80971
||            CMV IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80972
||            CMV IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80973
||            Herpes IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80974
||            Herpes IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80975
||            Parvovirus IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80976
||            Parvovirus IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40051
||         Rhesus D Factor foetus
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
|}
<section end=transaction />

Gebz:V2.3 transaction beschikbaarstellen gegevens zwangerschapskaart

2021-04-09T11:19:55Z

Stephan Opdenberg:

=Addendum Beschikbaarstellen gegevens Zwangerschapskaart=
{{IssueBox|Generated code, do not change by hand}}
=beschikbaarstellen_gegevens_zwangerschapskaart=
<section begin=transaction />
{| class="wikitable"
| style="background-color: #1F497D;; color: white; font-weight: bold; text-align:center;" colspan="13" | PWD 2.3 to FHIR
|-style="background-color: #1F497D;; color: white; text-align:left;"
|style="width:30px;"| Type
|style="width:10px;"| #
||Concept
|style="width:40px;"| Card
|| Profile
|| Mapping
|| Example
|| Search URL
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||4
||Zorgverlening
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20290
||   Datum start zorgverantwoordelijkheid
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.start
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20340
||   Datum einde zorgverantwoordelijkheid
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.end
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||1
||Zorgverlener/Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization | nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization | nl-core-practitioner}}
||Organization | Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10001
||   Zorgverlener
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
* GET [base]/Practitioner/[zorgverlenerid]
* GET [base]/Practitioner?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10002
||      Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10003
||      Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10006
||      Naam zorgverlener
||1 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10010
||      Zorgverlenertype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty
||[https://simplifier.net/geboortezorg-stu3/practitionerrole-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10012
||      Telefoon waar zorgverlener is te bereiken
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.telecom
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10020
||   Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
* GET [base]/Organization/[zorginstellingid]
* GET [base]/Organization?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10021
||      Zorginstelling OID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10022
||      Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10023
||      Zorginstelling LVR-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10024
||      Zorginstelling URA
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10026
||      Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10027
||      Adres zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10032
||         Straatnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10033
||         Huisnummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10034
||         Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10041
||         Postcode
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10036
||         Plaatsnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.city
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10037
||         Gemeentenaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.district
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10038
||         Land
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.country
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10039
||         Adrestype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.extension:AddressType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10029
||      Type zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82019
||      Type zorginstelling (bij verwijzing)
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationTypee
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||2
||Vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
* GET [base]/Patient/[vrouwid]
* GET [base]/Patient?identifier=[bsn]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10031
||   Lokale persoonsidentificatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10035
||   Naamgegevens
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10042
||      Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82359
||      Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82360
||      Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82361
||      Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82362
||         Soort naam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82363
||         Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10043
||         Achternaam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10040
||   Geboortedatum
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.birthdate
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10300
||   Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10301
||      Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10302
||      Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10303
||      Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10304
||      Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10305
||      Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.city
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10306
||      Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.district
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10307
||      Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.country
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10308
||      Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.type
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82694
||   Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82695
||      Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82696
||         Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82697
||         TelecomType
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82698
||         NummerSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82699
||      EmailAdressen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82700
||         EmailAdres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82701
||         EmailSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80649
||   Betrokken zorgverlener/zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner/nl-core-organization}}
||Practitioner/Organization
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82022
||      Huisarts
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82027
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82028
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82029
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82023
||      Apotheek
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82030
||         Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82031
||         Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name.text
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82024
||      Specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82039
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82032
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82033
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82038
||         Type specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty.text
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82035
||         Zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82036
||            Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82037
||            Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10801
||   Medicatiegebruik?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-150 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80749
||   Medicatiegebruik
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10802
||      Soort medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|zib-Product|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse|zib-Product}}
||MedicationStatement.medicationReference|Medication.code.text
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80751
||      Begindatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.start
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80752
||      Einddatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.end
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80750
||      Dosering medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.dosage.doseQuantity
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80753
||      Bijzonderheden
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.note
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80688
||   BMI
||0 .. 1
||
||
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80689
||      Datum bepaling
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10806
||      BMI vrouw
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-120 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80675
||   Vrouwelijke genitale verminking?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-177 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80676
||   Type vrouwelijke genitale verminking
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-172 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10807
||   Actuele bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10808
||      Actuele bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10809
||      Actuele bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10810
||   Bloedgroep vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-79 example]
||
* GET [base]/Observation?code=883-9{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10811
||   Rhesus D Factor vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
* GET [base]/Observation?code=1305-2{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10816
||   Rhesus c Factor
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-82 example]
||
* GET [base]/Observation?code=1159-3{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80633
||   Partner
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80638
||      Persoonsnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80639
||         Voornamen
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.given
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80640
||         Voorvoegsel
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.family
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80641
||         Achternamen
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.family
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80636
||      Etniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||17
||Obstetrische anamnese gegroepeerd per voorgaande zwangerschap
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy}}
||Condition
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||18
||   Eerdere bevalling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||19
||      Vorige uitkomst (per kind)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80709
||         Vorige baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80710
||            Werkelijke plaats baring (type locatie)
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||21
||            Kindspecifieke gegevens vorige uitkomsten
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80624
||               Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||3
||Zwangerschap
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy}}
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
* GET [base]/Condition/[zwangerschapid]
* GET [base]/Condition?clinicalstatus=active
* GET [base]/Condition?clinicalstatus=inactive&_sort=_-id&_count=1
* GET [base]/Condition?subject=[patientid]&_revinclude=Observation:focus
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80664
||   Casemanager naam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.careManager.display
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20010
||   Graviditeit
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Gravidity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Gravidity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-84 example]
||
* GET [base]/Observation?code=11996-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20150
||   Pariteit (vóór deze zwangerschap)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Parity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Parity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-88 example]
||
* GET [base]/Observation?code=11977-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80617
||   Aantal levende kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-112 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80678
||   Fetal Loss
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20029
||   A terme datum (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20030
||      A terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20040
||      Datum bepaling à terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20050
||      A terme datum o.b.v.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.method
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82160
||   Definitieve à terme datum
||0 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-263 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80819
||   Foliumzuur gebruik
||0 .. 1
||
||
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20020
||   Hoeveelling
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20130
||   Amnioniciteit
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20140
||   Chorioniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80732
||   Prenatale controle
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80737
||      Datum controle
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter.period.start
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80736
||      Naam zorgverlener
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.display | Practitioner.name
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82067
||      Zorgverlenertype
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.extension:practitionerRole.specialty | PractitionerRole.specialty
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80738
||      Zwangerschapsduur
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80746
||      Leven voelen
||1 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-144 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80810
||      Rookgedrag
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TobaccoUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-TobaccoUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-191 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80747
||      Alcoholgebruik
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AlcoholUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-AlcoholUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-189 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82102
||      Drugsgebruik?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-190 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82103
||      Soort drugs
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.component:DrugOrMedicationType.valueCodeableConcept
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80832
||      Bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80833
||         Bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:SystolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80834
||         Bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:DiastolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20211
||      Gewicht (gemeten)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyWeight}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-187 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80621
||      Uitwendig onderzoek
||1 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82105
||         Hartactie
||1 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82106
||            Regelmaat hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82107
||            Frequentie hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80745
||         Hartactie op basis van
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82268
||   Diagnose
||0 .. *
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82272
||      Datum
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-21 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82285
||      Zwangerschapsduur
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82269
||      Gynaecologische aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82270
||      Bloedverlies?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-17 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82286
||      Partiële mola?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-35 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82271
||      Cervixinsufficiëntie?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-18 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82273
||      Infectie
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-29 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82274
||      Hyperemesis gravidarum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-27 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82275
||      Hypertensieve aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-28 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82276
||      Zwangerschapscholestase?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-14 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82277
||      Diabetes gravidarum met insuline?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-22 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82278
||      Afwijkende groei foetus
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-16 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82279
||      Dreigende partus immaturus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-23 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82280
||      Dreigende partus prematurus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-24 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82289
||      Abruptio placentae?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-15 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82452
||      Navelstrengprolaps?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-32 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82380
||      Liggingsafwijking
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-31 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||83405
||      Meerlingzwangerschap?
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||84193
||      Serotiniteit?
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80613
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82435
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82377
||   Interventie
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82376
||      Interventie
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82230
||   Intra-uteriene behandeling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||6
||Bevalling
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
* GET [base]/Procedure?code=236973005{&subject=[vrouwid]&context=[dossierid]&reasonReference=[zwangerschapid]}
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20500
||   Partusnummer
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.identifier
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82291
||   Diagnose bevalling
||1 .. *
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82381
||      Datum
||1 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82382
||      Zwangerschapsduur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82338
||      PPROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-37 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82290
||      PROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-39 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82292
||      Koorts?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-30 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82293
||      Niet vorderende ontsluiting?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-33 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82294
||      Niet vorderende uitdrijving?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-34 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82296
||      Verdenking foetale nood?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82443
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82444
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82295
||      Vastzittende placenta?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-42 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82398
||      Fluxus postpartum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20505
||   Aantal geboren kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-111 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20555
||   Interventies begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20560
||      Interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20570
||      Indicatie interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20550
||   Wijze waarop de baring begon
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-178 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20590
||   Tijdstip begin actieve ontsluiting
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-63 example]
||
* GET [base]/Observation?code=249120008{&subject=[vrouwid]&context=[dossierid]&focus=[bevallingid]}
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||7
||Uitkomst (per kind)
||0 .. *
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40002
||   Baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
* GET [base]/Procedure?code=3950001{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]&focus=[kindid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40003
||      Werkelijke plaats baring (type locatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ChildBirthAssistance|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ChildBirthAssistance}}
||Encounter.class:werkelijkePlaatsBaring
||[https://simplifier.net/geboortezorg-stu3/encounter-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40006
||      Demografische gegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient
||
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40007
||         Identificaties kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40010
||            BSN kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier:BSN
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40011
||            Lokale identificatie kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40015
||            Identificatie kind PRN formaat
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82051
||         Naamgegevens kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82353
||            Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82354
||            Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82052
||            Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82053
||            Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82054
||               Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannamePrefix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82055
||               Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannameOwnName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82364
||         Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82365
||            Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82366
||               Soort telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.use
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82367
||               Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40032
||         Adres t.b.v. hielprik
||0 .. 1
||
||
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82133
||            Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:streetName
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82134
||            Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:houseNumber
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82135
||            Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:buildingNumbersuffix
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82136
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82137
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patientaddress.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82138
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.country
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82139
||            Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.extension:AddressType
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40033
||         Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40034
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40040
||         Geslacht (administratief)
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40041
||         Geslacht (medische observatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.gender.Extension
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40050
||         Geboortedatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.birthdate & patient.birthtime (extension)
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40004
||         Geboorteplaats
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80629
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80630
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80631
||            Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.district
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80632
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension.birthPlace.country
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82087
||         Meerlingindicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthBoolean
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40025
||         Rangnummer kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthInteger
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||71
||      Kindspecifieke maternale gegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20616
||         Bijstimulatie toegediend?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-6 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20579
||         Amniotomie (groep)
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20580
||            Amniotomie?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80794
||         Indicatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||30055
||         Locatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.bodySite.extension
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82090
||         Pijnbestrijding?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82091
||         Pijnbestrijding
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82394
||            Datum/tijd
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.effectiveDateTime
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82093
||            Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82092
||               Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82094
||               Overig middel
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.route
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82095
||                  Middel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.medicationCodeableConcept
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||72
||      Kindspecifieke uitkomstgegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80626
||         Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCode
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
* GET [base]/Observation?code=364336006{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40189
||         Vaginale kunstverlossing (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40190
||            Vaginale kunstverlossing
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
* GET [base]/Procedure?code=3311000146109{&subject=[vrouwid]&context=[dossierid]&partof=[bevallingid,uitdrijvingsfaseid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40210
||            Indicatie vaginale kunstverlossing
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40219
||         Sectio caesarea (group)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82546
||            Indicatie primaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82547
||            Indicatie secundaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80766
||         Lichamelijk onderzoek kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PhysicalExamination|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PhysicalExamination}}
||DiagnosticReport
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40070
||            Apgarscore na 1 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40071
||            Apgarscore na 5 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-77 example]
||
* GET [base]/Observation?code=9274-2{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80757
||            Apgarscore na 10 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40060
||            Geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-180 example]
||
* GET [base]/Observation?code=8339-4{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80670
||            Percentiel van het geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.interpretation.extension:percentile
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-185 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80759
||            Lengte
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyHeight}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80760
||            Schedelomtrek
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HeadCircumference|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-HeadCircumference}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||14
||Medisch onderzoek
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||50020
||   Datum onderzoek
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||142
||   Maternale onderzoeksgegevens
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80959
||      Urine-, bloed- en aanvullende onderzoeken
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80949
||         PSIE
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80952
||            Bloedgroep vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80953
||            Rhesus D Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80954
||            Rhesus c Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80955
||            HBsAg
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80956
||            HIV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80957
||            Lues
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10812
||            Irregulaire antistoffen?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-181 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10813
||            Welke irregulaire antistoffen vrouw aanwezig.
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-260 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10814
||         Hb
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-80 example]
||
* GET [base]/Observation?code=718-7{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80991
||         Anemie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80951
||            MCV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80992
||            Hb-pathie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Problem}}
||Condition.code
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80993
||            Vit. B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80994
||            Actief-B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80995
||            Ferritine
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80996
||            Foliumzuur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80963
||         Schildklier diagnostiek
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80962
||            TSH receptor antistoffen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80964
||            Vrij T4
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80965
||            TSH
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80966
||         TORCH
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80967
||            Toxoplasmose IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80968
||            Toxoplasmose IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80969
||            Rubella IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80970
||            Rubella IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80971
||            CMV IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80972
||            CMV IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80973
||            Herpes IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80974
||            Herpes IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80975
||            Parvovirus IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80976
||            Parvovirus IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40051
||         Rhesus D Factor foetus
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
|}
<section end=transaction />

Gebz:V2.3 transaction beschikbaarstellen gegevens zwangerschapskaart

2021-04-09T09:53:52Z

Stephan Opdenberg:

=Addendum Beschikbaarstellen gegevens Zwangerschapskaart=
{{IssueBox|Generated code, do not change by hand}}
=beschikbaarstellen_gegevens_zwangerschapskaart=
<section begin=transaction />
{| class="wikitable"
| style="background-color: #1F497D;; color: white; font-weight: bold; text-align:center;" colspan="13" | PWD 2.3 to FHIR
|-style="background-color: #1F497D;; color: white; text-align:left;"
|style="width:30px;"| Type
|style="width:10px;"| #
||Concept
|style="width:40px;"| Card
|| Profile
|| Mapping
|| Example
|| Search URL
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||4
||Zorgverlening
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20290
||   Datum start zorgverantwoordelijkheid
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.start
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20340
||   Datum einde zorgverantwoordelijkheid
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.end
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||1
||Zorgverlener/Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization | nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization | nl-core-practitioner}}
||Organization | Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10001
||   Zorgverlener
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
* GET [base]/Practitioner/[zorgverlenerid]
* GET [base]/Practitioner?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10002
||      Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10003
||      Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10006
||      Naam zorgverlener
||1 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10010
||      Zorgverlenertype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty
||[https://simplifier.net/geboortezorg-stu3/practitionerrole-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10012
||      Telefoon waar zorgverlener is te bereiken
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.telecom
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10020
||   Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
* GET [base]/Organization/[zorginstellingid]
* GET [base]/Organization?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10021
||      Zorginstelling OID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10022
||      Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10023
||      Zorginstelling LVR-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10024
||      Zorginstelling URA
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10026
||      Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10027
||      Adres zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10032
||         Straatnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10033
||         Huisnummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10034
||         Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10041
||         Postcode
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10036
||         Plaatsnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.city
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10037
||         Gemeentenaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.district
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10038
||         Land
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.country
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10039
||         Adrestype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.extension:AddressType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10029
||      Type zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82019
||      Type zorginstelling (bij verwijzing)
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationTypee
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||2
||Vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
* GET [base]/Patient/[vrouwid]
* GET [base]/Patient?identifier=[bsn]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10031
||   Lokale persoonsidentificatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10035
||   Naamgegevens
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10042
||      Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82359
||      Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82360
||      Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82361
||      Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82362
||         Soort naam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82363
||         Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10043
||         Achternaam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10040
||   Geboortedatum
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.birthdate
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10300
||   Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10301
||      Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10302
||      Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10303
||      Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10304
||      Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10305
||      Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.city
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10306
||      Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.district
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10307
||      Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.country
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10308
||      Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.type
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82694
||   Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82695
||      Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82696
||         Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82697
||         TelecomType
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82698
||         NummerSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82699
||      EmailAdressen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82700
||         EmailAdres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82701
||         EmailSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80649
||   Betrokken zorgverlener/zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner/nl-core-organization}}
||Practitioner/Organization
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82022
||      Huisarts
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82027
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82028
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82029
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82023
||      Apotheek
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82030
||         Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82031
||         Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name.text
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82024
||      Specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82039
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82032
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82033
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82038
||         Type specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty.text
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82035
||         Zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82036
||            Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82037
||            Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10801
||   Medicatiegebruik?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-150 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80749
||   Medicatiegebruik
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10802
||      Soort medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|zib-Product|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse|zib-Product}}
||MedicationStatement.medicationReference|Medication.code.text
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80751
||      Begindatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.start
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80752
||      Einddatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.end
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80750
||      Dosering medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.dosage.doseQuantity
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80753
||      Bijzonderheden
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.note
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80688
||   BMI
||0 .. 1
||
||
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80689
||      Datum bepaling
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10806
||      BMI vrouw
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-120 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80675
||   Vrouwelijke genitale verminking?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-177 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80676
||   Type vrouwelijke genitale verminking
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-172 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10807
||   Actuele bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10808
||      Actuele bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10809
||      Actuele bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10810
||   Bloedgroep vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-79 example]
||
* GET [base]/Observation?code=883-9{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10811
||   Rhesus D Factor vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
* GET [base]/Observation?code=1305-2{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10816
||   Rhesus c Factor
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-82 example]
||
* GET [base]/Observation?code=1159-3{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80633
||   Partner
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80638
||      Persoonsnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80639
||         Voornamen
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.given
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80640
||         Voorvoegsel
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.family
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80641
||         Achternamen
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.family
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80636
||      Etniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||17
||Obstetrische anamnese gegroepeerd per voorgaande zwangerschap
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy}}
||Condition
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||18
||   Eerdere bevalling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||19
||      Vorige uitkomst (per kind)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80709
||         Vorige baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80710
||            Werkelijke plaats baring (type locatie)
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||21
||            Kindspecifieke gegevens vorige uitkomsten
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80624
||               Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||3
||Zwangerschap
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy}}
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
* GET [base]/Condition/[zwangerschapid]
* GET [base]/Condition?clinicalstatus=active
* GET [base]/Condition?clinicalstatus=inactive&_sort=_-id&_count=1
* GET [base]/Condition?subject=[patientid]&_revinclude=Observation:focus
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80664
||   Casemanager naam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.careManager.display
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20010
||   Graviditeit
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Gravidity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Gravidity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-84 example]
||
* GET [base]/Observation?code=11996-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20150
||   Pariteit (vóór deze zwangerschap)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Parity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Parity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-88 example]
||
* GET [base]/Observation?code=11977-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80617
||   Aantal levende kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-112 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80678
||   Fetal Loss
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20029
||   A terme datum (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20030
||      A terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20040
||      Datum bepaling à terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20050
||      A terme datum o.b.v.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.method
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82160
||   Definitieve à terme datum
||0 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-263 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80819
||   Foliumzuur gebruik
||0 .. 1
||
||
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20020
||   Hoeveelling
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20130
||   Amnioniciteit
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20140
||   Chorioniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80732
||   Prenatale controle
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80737
||      Datum controle
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter.period.start
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80736
||      Naam zorgverlener
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.display | Practitioner.name
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82067
||      Zorgverlenertype
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.extension:practitionerRole.specialty | PractitionerRole.specialty
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80738
||      Zwangerschapsduur
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80746
||      Leven voelen
||1 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-144 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80810
||      Rookgedrag
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TobaccoUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-TobaccoUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-191 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80747
||      Alcoholgebruik
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AlcoholUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-AlcoholUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-189 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82102
||      Drugsgebruik?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-190 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82103
||      Soort drugs
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.component:DrugOrMedicationType.valueCodeableConcept
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80832
||      Bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80833
||         Bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:SystolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80834
||         Bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:DiastolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20211
||      Gewicht (gemeten)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyWeight}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-187 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80621
||      Uitwendig onderzoek
||1 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82105
||         Hartactie
||1 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82106
||            Regelmaat hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82107
||            Frequentie hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80745
||         Hartactie op basis van
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82268
||   Diagnose
||0 .. *
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82272
||      Datum
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-21 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82285
||      Zwangerschapsduur
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82269
||      Gynaecologische aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82270
||      Bloedverlies?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-17 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82286
||      Partiële mola?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-35 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82271
||      Cervixinsufficiëntie?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-18 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82273
||      Infectie
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-29 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82274
||      Hyperemesis gravidarum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-27 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82275
||      Hypertensieve aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-28 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82276
||      Zwangerschapscholestase?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-14 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82277
||      Diabetes gravidarum met insuline?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-22 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82278
||      Afwijkende groei foetus
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-16 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82279
||      Dreigende partus immaturus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-23 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82280
||      Dreigende partus prematurus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-24 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82289
||      Abruptio placentae?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-15 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82452
||      Navelstrengprolaps?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-32 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82380
||      Liggingsafwijking
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-31 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||83405
||      Meerlingzwangerschap?
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||84193
||      Serotiniteit?
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80613
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82435
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82377
||   Interventie
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82376
||      Interventie
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82230
||   Intra-uteriene behandeling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||6
||Bevalling
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
* GET [base]/Procedure?code=236973005{&subject=[vrouwid]&context=[dossierid]&reasonReference=[zwangerschapid]}
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20500
||   Partusnummer
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.identifier
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82291
||   Diagnose bevalling
||1 .. *
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82381
||      Datum
||1 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82382
||      Zwangerschapsduur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82338
||      PPROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-37 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82290
||      PROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-39 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82292
||      Koorts?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-30 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82293
||      Niet vorderende ontsluiting?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-33 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82294
||      Niet vorderende uitdrijving?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-34 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82296
||      Verdenking foetale nood?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82443
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82444
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82295
||      Vastzittende placenta?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-42 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82398
||      Fluxus postpartum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20505
||   Aantal geboren kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-111 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20555
||   Interventies begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20560
||      Interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20570
||      Indicatie interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20550
||   Wijze waarop de baring begon
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-178 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20590
||   Tijdstip begin actieve ontsluiting
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-63 example]
||
* GET [base]/Observation?code=249120008{&subject=[vrouwid]&context=[dossierid]&focus=[bevallingid]}
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||7
||Uitkomst (per kind)
||0 .. *
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40002
||   Baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
* GET [base]/Procedure?code=3950001{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]&focus=[kindid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40003
||      Werkelijke plaats baring (type locatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ChildBirthAssistance|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ChildBirthAssistance}}
||Encounter.class:werkelijkePlaatsBaring
||[https://simplifier.net/geboortezorg-stu3/encounter-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40006
||      Demografische gegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient
||
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40007
||         Identificaties kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40010
||            BSN kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier:BSN
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40011
||            Lokale identificatie kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40015
||            Identificatie kind PRN formaat
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82051
||         Naamgegevens kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82353
||            Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82354
||            Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82052
||            Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82053
||            Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82054
||               Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannamePrefix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82055
||               Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannameOwnName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82364
||         Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82365
||            Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82366
||               Soort telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.use
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82367
||               Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40032
||         Adres t.b.v. hielprik
||0 .. 1
||
||
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82133
||            Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:streetName
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82134
||            Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:houseNumber
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82135
||            Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:buildingNumbersuffix
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82136
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82137
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patientaddress.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82138
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.country
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82139
||            Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.extension:AddressType
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40033
||         Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40034
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40040
||         Geslacht (administratief)
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40041
||         Geslacht (medische observatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.gender.Extension
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40050
||         Geboortedatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.birthdate & patient.birthtime (extension)
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40004
||         Geboorteplaats
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80629
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80630
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80631
||            Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.district
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80632
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension.birthPlace.country
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82087
||         Meerlingindicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthBoolean
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40025
||         Rangnummer kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthInteger
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||71
||      Kindspecifieke maternale gegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20616
||         Bijstimulatie toegediend?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-6 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20579
||         Amniotomie (groep)
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20580
||            Amniotomie?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80794
||         Indicatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||30055
||         Locatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.bodySite.extension
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82090
||         Pijnbestrijding?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82091
||         Pijnbestrijding
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82394
||            Datum/tijd
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.effectiveDateTime
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82093
||            Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82092
||               Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82094
||               Overig middel
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.route
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82095
||                  Middel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.medicationCodeableConcept
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||72
||      Kindspecifieke uitkomstgegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80626
||         Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCode
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
* GET [base]/Observation?code=364336006{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40189
||         Vaginale kunstverlossing (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40190
||            Vaginale kunstverlossing
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
* GET [base]/Procedure?code=3311000146109{&subject=[vrouwid]&context=[dossierid]&partof=[bevallingid,uitdrijvingsfaseid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40210
||            Indicatie vaginale kunstverlossing
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40219
||         Sectio caesarea (group)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82546
||            Indicatie primaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82547
||            Indicatie secundaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80766
||         Lichamelijk onderzoek kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PhysicalExamination|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PhysicalExamination}}
||DiagnosticReport
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40070
||            Apgarscore na 1 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40071
||            Apgarscore na 5 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-77 example]
||
* GET [base]/Observation?code=9274-2{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80757
||            Apgarscore na 10 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40060
||            Geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-180 example]
||
* GET [base]/Observation?code=8339-4{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80670
||            Percentiel van het geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.interpretation.extension:percentile
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-185 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80759
||            Lengte
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyHeight}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80760
||            Schedelomtrek
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HeadCircumference|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-HeadCircumference}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||14
||Medisch onderzoek
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||50020
||   Datum onderzoek
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||142
||   Maternale onderzoeksgegevens
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80959
||      Urine-, bloed- en aanvullende onderzoeken
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80949
||         PSIE
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80952
||            Bloedgroep vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80953
||            Rhesus D Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80954
||            Rhesus c Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80955
||            HBsAg
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80956
||            HIV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80957
||            Lues
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10812
||            Irregulaire antistoffen?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-181 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10813
||            Welke irregulaire antistoffen vrouw aanwezig.
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-260 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10814
||         Hb
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-80 example]
||
* GET [base]/Observation?code=718-7{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80991
||         Anemie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80951
||            MCV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80992
||            Hb-pathie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Problem}}
||Condition.code
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80993
||            Vit. B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80994
||            Actief-B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80995
||            Ferritine
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80996
||            Foliumzuur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80963
||         Schildklier diagnostiek
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80962
||            TSH receptor antistoffen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80964
||            Vrij T4
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80965
||            TSH
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80966
||         TORCH
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80967
||            Toxoplasmose IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80968
||            Toxoplasmose IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80969
||            Rubella IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80970
||            Rubella IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80971
||            CMV IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80972
||            CMV IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80973
||            Herpes IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80974
||            Herpes IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80975
||            Parvovirus IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80976
||            Parvovirus IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40051
||         Rhesus D Factor foetus
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
|}
<section end=transaction />

Gebz:V2.3 transaction beschikbaarstellen gegevens zwangerschapskaart

2021-04-08T13:31:15Z

Stephan Opdenberg:

=Addendum Beschikbaarstellen gegevens Zwangerschapskaart=
{{IssueBox|Generated code, do not change by hand}}
=beschikbaarstellen_gegevens_zwangerschapskaart=
<section begin=transaction />
{| class="wikitable"
| style="background-color: #1F497D;; color: white; font-weight: bold; text-align:center;" colspan="13" | PWD 2.3 to FHIR
|-style="background-color: #1F497D;; color: white; text-align:left;"
|style="width:30px;"| Type
|style="width:10px;"| #
||Concept
|style="width:40px;"| Card
|| Profile
|| Mapping
|| Example
|| Search URL
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||4
||Zorgverlening
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20290
||   Datum start zorgverantwoordelijkheid
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.start
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20340
||   Datum einde zorgverantwoordelijkheid
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.end
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||1
||Zorgverlener/Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization | nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization | nl-core-practitioner}}
||Organization | Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10001
||   Zorgverlener
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
* GET [base]/Practitioner/[zorgverlenerid]
* GET [base]/Practitioner?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10002
||      Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10003
||      Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10006
||      Naam zorgverlener
||1 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10010
||      Zorgverlenertype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty
||[https://simplifier.net/geboortezorg-stu3/practitionerrole-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10012
||      Telefoon waar zorgverlener is te bereiken
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.telecom
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10020
||   Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
* GET [base]/Organization/[zorginstellingid]
* GET [base]/Organization?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10021
||      Zorginstelling OID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10022
||      Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10023
||      Zorginstelling LVR-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10024
||      Zorginstelling URA
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10026
||      Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10027
||      Adres zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10032
||         Straatnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10033
||         Huisnummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10034
||         Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10041
||         Postcode
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10036
||         Plaatsnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.city
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10037
||         Gemeentenaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.district
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10038
||         Land
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.country
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10039
||         Adrestype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.extension:AddressType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10029
||      Type zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82019
||      Type zorginstelling (bij verwijzing)
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationTypee
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||2
||Vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
* GET [base]/Patient/[vrouwid]
* GET [base]/Patient?identifier=[bsn]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10031
||   Lokale persoonsidentificatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10035
||   Naamgegevens
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10042
||      Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82359
||      Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82360
||      Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82361
||      Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82362
||         Soort naam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82363
||         Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10043
||         Achternaam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10040
||   Geboortedatum
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.birthdate
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10300
||   Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10301
||      Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10302
||      Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10303
||      Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10304
||      Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10305
||      Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.city
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10306
||      Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.district
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10307
||      Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.country
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10308
||      Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.type
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82694
||   Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82695
||      Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82696
||         Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82697
||         TelecomType
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82698
||         NummerSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82699
||      EmailAdressen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82700
||         EmailAdres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82701
||         EmailSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80649
||   Betrokken zorgverlener/zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner/nl-core-organization}}
||Practitioner/Organization
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82022
||      Huisarts
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82027
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82028
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82029
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82023
||      Apotheek
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82030
||         Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82031
||         Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name.text
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82024
||      Specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82039
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82032
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82033
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82038
||         Type specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty.text
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82035
||         Zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82036
||            Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82037
||            Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10801
||   Medicatiegebruik?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-150 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80749
||   Medicatiegebruik
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10802
||      Soort medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|zib-Product|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse|zib-Product}}
||MedicationStatement.medicationReference|Medication.code.text
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80751
||      Begindatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.start
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80752
||      Einddatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.end
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80750
||      Dosering medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.dosage.doseQuantity
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80753
||      Bijzonderheden
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.note
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80688
||   BMI
||0 .. 1
||
||
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80689
||      Datum bepaling
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10806
||      BMI vrouw
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-120 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80675
||   Vrouwelijke genitale verminking?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-177 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80676
||   Type vrouwelijke genitale verminking
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-172 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10807
||   Actuele bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10808
||      Actuele bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10809
||      Actuele bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10810
||   Bloedgroep vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-79 example]
||
* GET [base]/Observation?code=883-9{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10811
||   Rhesus D Factor vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
* GET [base]/Observation?code=1305-2{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10816
||   Rhesus c Factor
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-82 example]
||
* GET [base]/Observation?code=1159-3{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80633
||   Partner
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80638
||      Persoonsnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80639
||         Voornamen
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.given
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80640
||         Voorvoegsel
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.family
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80641
||         Achternamen
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson.name.family
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80636
||      Etniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||17
||Obstetrische anamnese gegroepeerd per voorgaande zwangerschap
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy}}
||Condition
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||18
||   Eerdere bevalling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||19
||      Vorige uitkomst (per kind)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80709
||         Vorige baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80710
||            Werkelijke plaats baring (type locatie)
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||21
||            Kindspecifieke gegevens vorige uitkomsten
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80624
||               Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||3
||Zwangerschap
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy}}
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
* GET [base]/Condition/[zwangerschapid]
* GET [base]/Condition?clinicalstatus=active
* GET [base]/Condition?clinicalstatus=inactive&_sort=_-id&_count=1
* GET [base]/Condition?subject=[patientid]&_revinclude=Observation:focus
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80664
||   Casemanager naam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.careManager.display
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20010
||   Graviditeit
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Gravidity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Gravidity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-84 example]
||
* GET [base]/Observation?code=11996-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20150
||   Pariteit (vóór deze zwangerschap)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Parity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Parity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-88 example]
||
* GET [base]/Observation?code=11977-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80617
||   Aantal levende kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-112 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80678
||   Fetal Loss
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20029
||   A terme datum (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20030
||      A terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20040
||      Datum bepaling à terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20050
||      A terme datum o.b.v.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.method
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82160
||   Definitieve à terme datum
||0 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-263 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80819
||   Foliumzuur gebruik
||0 .. 1
||
||
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20020
||   Hoeveelling
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20130
||   Amnioniciteit
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20140
||   Chorioniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80732
||   Prenatale controle
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80737
||      Datum controle
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter.period.start
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80736
||      Naam zorgverlener
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.display | Practitioner.name
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82067
||      Zorgverlenertype
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.extension:practitionerRole.specialty | PractitionerRole.specialty
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80738
||      Zwangerschapsduur
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80746
||      Leven voelen
||1 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-144 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80810
||      Rookgedrag
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TobaccoUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-TobaccoUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-191 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80747
||      Alcoholgebruik
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AlcoholUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-AlcoholUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-189 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82102
||      Drugsgebruik?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-190 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82103
||      Soort drugs
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.component:DrugOrMedicationType.valueCodeableConcept
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80832
||      Bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80833
||         Bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:SystolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80834
||         Bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:DiastolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20211
||      Gewicht (gemeten)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyWeight}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-187 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80621
||      Uitwendig onderzoek
||1 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82105
||         Hartactie
||1 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82106
||            Regelmaat hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82107
||            Frequentie hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80745
||         Hartactie op basis van
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82268
||   Diagnose
||0 .. *
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82272
||      Datum
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-21 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82285
||      Zwangerschapsduur
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82269
||      Gynaecologische aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82270
||      Bloedverlies?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-17 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82286
||      Partiële mola?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-35 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82271
||      Cervixinsufficiëntie?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-18 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82273
||      Infectie
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-29 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82274
||      Hyperemesis gravidarum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-27 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82275
||      Hypertensieve aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-28 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82276
||      Zwangerschapscholestase?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-14 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82277
||      Diabetes gravidarum met insuline?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-22 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82278
||      Afwijkende groei foetus
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-16 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82279
||      Dreigende partus immaturus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-23 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82280
||      Dreigende partus prematurus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-24 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82289
||      Abruptio placentae?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-15 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82452
||      Navelstrengprolaps?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-32 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82380
||      Liggingsafwijking
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-31 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||83405
||      Meerlingzwangerschap?
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||84193
||      Serotiniteit?
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80613
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82435
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82377
||   Interventie
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82376
||      Interventie
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82230
||   Intra-uteriene behandeling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||6
||Bevalling
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
* GET [base]/Procedure?code=236973005{&subject=[vrouwid]&context=[dossierid]&reasonReference=[zwangerschapid]}
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20500
||   Partusnummer
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.identifier
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82291
||   Diagnose bevalling
||1 .. *
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82381
||      Datum
||1 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82382
||      Zwangerschapsduur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82338
||      PPROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-37 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82290
||      PROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-39 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82292
||      Koorts?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-30 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82293
||      Niet vorderende ontsluiting?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-33 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82294
||      Niet vorderende uitdrijving?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-34 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82296
||      Verdenking foetale nood?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82443
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82444
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82295
||      Vastzittende placenta?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-42 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82398
||      Fluxus postpartum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20505
||   Aantal geboren kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-111 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20555
||   Interventies begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20560
||      Interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20570
||      Indicatie interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20550
||   Wijze waarop de baring begon
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-178 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20590
||   Tijdstip begin actieve ontsluiting
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-63 example]
||
* GET [base]/Observation?code=249120008{&subject=[vrouwid]&context=[dossierid]&focus=[bevallingid]}
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||7
||Uitkomst (per kind)
||0 .. *
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40002
||   Baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
* GET [base]/Procedure?code=3950001{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]&focus=[kindid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40003
||      Werkelijke plaats baring (type locatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ChildBirthAssistance|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ChildBirthAssistance}}
||Encounter.class:werkelijkePlaatsBaring
||[https://simplifier.net/geboortezorg-stu3/encounter-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40006
||      Demografische gegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient
||
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40007
||         Identificaties kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40010
||            BSN kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier:BSN
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40011
||            Lokale identificatie kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40015
||            Identificatie kind PRN formaat
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82051
||         Naamgegevens kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82353
||            Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82354
||            Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82052
||            Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82053
||            Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82054
||               Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannamePrefix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82055
||               Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannameOwnName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82364
||         Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82365
||            Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82366
||               Soort telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.use
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82367
||               Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40032
||         Adres t.b.v. hielprik
||0 .. 1
||
||
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82133
||            Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:streetName
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82134
||            Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:houseNumber
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82135
||            Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:buildingNumbersuffix
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82136
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82137
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patientaddress.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82138
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.country
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82139
||            Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.extension:AddressType
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40033
||         Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40034
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40040
||         Geslacht (administratief)
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40041
||         Geslacht (medische observatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.gender.Extension
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40050
||         Geboortedatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.birthdate & patient.birthtime (extension)
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40004
||         Geboorteplaats
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80629
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80630
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80631
||            Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.district
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80632
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension.birthPlace.country
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82087
||         Meerlingindicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthBoolean
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40025
||         Rangnummer kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthInteger
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||71
||      Kindspecifieke maternale gegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20616
||         Bijstimulatie toegediend?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-6 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20579
||         Amniotomie (groep)
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20580
||            Amniotomie?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80794
||         Indicatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||30055
||         Locatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.bodySite.extension
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82090
||         Pijnbestrijding?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82091
||         Pijnbestrijding
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82394
||            Datum/tijd
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.effectiveDateTime
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82093
||            Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82092
||               Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82094
||               Overig middel
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.route
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82095
||                  Middel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.medicationCodeableConcept
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||72
||      Kindspecifieke uitkomstgegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80626
||         Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCode
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
* GET [base]/Observation?code=364336006{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40189
||         Vaginale kunstverlossing (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40190
||            Vaginale kunstverlossing
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
* GET [base]/Procedure?code=3311000146109{&subject=[vrouwid]&context=[dossierid]&partof=[bevallingid,uitdrijvingsfaseid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40210
||            Indicatie vaginale kunstverlossing
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40219
||         Sectio caesarea (group)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82546
||            Indicatie primaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82547
||            Indicatie secundaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80766
||         Lichamelijk onderzoek kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PhysicalExamination|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PhysicalExamination}}
||DiagnosticReport
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40070
||            Apgarscore na 1 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40071
||            Apgarscore na 5 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-77 example]
||
* GET [base]/Observation?code=9274-2{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80757
||            Apgarscore na 10 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40060
||            Geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-180 example]
||
* GET [base]/Observation?code=8339-4{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80670
||            Percentiel van het geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.interpretation.extension:percentile
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-185 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80759
||            Lengte
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyHeight}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80760
||            Schedelomtrek
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HeadCircumference|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-HeadCircumference}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||14
||Medisch onderzoek
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||50020
||   Datum onderzoek
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||142
||   Maternale onderzoeksgegevens
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80959
||      Urine-, bloed- en aanvullende onderzoeken
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80949
||         PSIE
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80952
||            Bloedgroep vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80953
||            Rhesus D Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80954
||            Rhesus c Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80955
||            HBsAg
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80956
||            HIV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80957
||            Lues
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10812
||            Irregulaire antistoffen?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-181 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10813
||            Welke irregulaire antistoffen vrouw aanwezig.
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-260 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10814
||         Hb
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-80 example]
||
* GET [base]/Observation?code=718-7{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80991
||         Anemie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80951
||            MCV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80992
||            Hb-pathie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Problem}}
||Condition.code
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80993
||            Vit. B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80994
||            Actief-B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80995
||            Ferritine
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80996
||            Foliumzuur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80963
||         Schildklier diagnostiek
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80962
||            TSH receptor antistoffen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80964
||            Vrij T4
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80965
||            TSH
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80966
||         TORCH
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80967
||            Toxoplasmose IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80968
||            Toxoplasmose IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80969
||            Rubella IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80970
||            Rubella IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80971
||            CMV IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80972
||            CMV IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80973
||            Herpes IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80974
||            Herpes IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80975
||            Parvovirus IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80976
||            Parvovirus IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40051
||         Rhesus D Factor foetus
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
|}
<section end=transaction />

Gebz:V2.3 transaction beschikbaarstellen gegevens zwangerschapskaart

2021-04-08T13:18:32Z

Stephan Opdenberg:

=Addendum Beschikbaarstellen gegevens Zwangerschapskaart=
{{IssueBox|Generated code, do not change by hand}}
=beschikbaarstellen_gegevens_zwangerschapskaart=
<section begin=transaction />
{| class="wikitable"
| style="background-color: #1F497D;; color: white; font-weight: bold; text-align:center;" colspan="13" | PWD 2.3 to FHIR
|-style="background-color: #1F497D;; color: white; text-align:left;"
|style="width:30px;"| Type
|style="width:10px;"| #
||Concept
|style="width:40px;"| Card
|| Profile
|| Mapping
|| Example
|| Search URL
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||4
||Zorgverlening
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20290
||   Datum start zorgverantwoordelijkheid
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.start
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20340
||   Datum einde zorgverantwoordelijkheid
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.period.end
||[https://simplifier.net/geboortezorg-stu3/episodeofcare-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||1
||Zorgverlener/Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization | nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization | nl-core-practitioner}}
||Organization | Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10001
||   Zorgverlener
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
* GET [base]/Practitioner/[zorgverlenerid]
* GET [base]/Practitioner?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10002
||      Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10003
||      Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10006
||      Naam zorgverlener
||1 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10010
||      Zorgverlenertype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty
||[https://simplifier.net/geboortezorg-stu3/practitionerrole-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10012
||      Telefoon waar zorgverlener is te bereiken
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.telecom
||[https://simplifier.net/geboortezorg-stu3/practitioner-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10020
||   Zorginstelling
||1 .. *
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
* GET [base]/Organization/[zorginstellingid]
* GET [base]/Organization?identifier=[lvrid]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10021
||      Zorginstelling OID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10022
||      Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10023
||      Zorginstelling LVR-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10024
||      Zorginstelling URA
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10026
||      Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10027
||      Adres zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10032
||         Straatnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10033
||         Huisnummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10034
||         Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10041
||         Postcode
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10036
||         Plaatsnaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.city
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10037
||         Gemeentenaam
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.district
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10038
||         Land
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.country
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10039
||         Adrestype
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.address.extension:AddressType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10029
||      Type zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationType
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82019
||      Type zorginstelling (bij verwijzing)
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.type:organizationTypee
||[https://simplifier.net/geboortezorg-stu3/organization-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||2
||Vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
* GET [base]/Patient/[vrouwid]
* GET [base]/Patient?identifier=[bsn]
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10031
||   Lokale persoonsidentificatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10035
||   Naamgegevens
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10042
||      Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82359
||      Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82360
||      Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82361
||      Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82362
||         Soort naam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82363
||         Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10043
||         Achternaam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10040
||   Geboortedatum
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.birthdate
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10300
||   Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10301
||      Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.streetName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10302
||      Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.HouseNumber
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10303
||      Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.line.Extension.BuildingNumberSuffix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10304
||      Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.postalCode
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10305
||      Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.city
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10306
||      Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.district
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10307
||      Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.country
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10308
||      Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.address.type
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82694
||   Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82695
||      Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82696
||         Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82697
||         TelecomType
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82698
||         NummerSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82699
||      EmailAdressen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82700
||         EmailAdres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.value
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82701
||         EmailSoort
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Woman|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Woman}}
||Patient.telecom.use
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80649
||   Betrokken zorgverlener/zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner/nl-core-organization}}
||Practitioner/Organization
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82022
||      Huisarts
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82027
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82028
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82029
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82023
||      Apotheek
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82030
||         Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82031
||         Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name.text
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82024
||      Specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82039
||         Zorgverlener UZI-nummer
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:UZI
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82032
||         Zorgverlener AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.identifier:AGB
||
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82033
||         Naam zorgverlener
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitioner}}
||Practitioner.name.text
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82038
||         Type specialist
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-practitionerrole}}
||PractitionerRole.specialty.text
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82035
||         Zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization
||
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82036
||            Zorginstelling AGB-ID
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.identifier:AGB
||
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82037
||            Naam zorginstelling
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-organization}}
||Organization.name
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10801
||   Medicatiegebruik?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-150 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80749
||   Medicatiegebruik
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10802
||      Soort medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|zib-Product|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse|zib-Product}}
||MedicationStatement.medicationReference|Medication.code.text
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80751
||      Begindatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.start
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80752
||      Einddatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.end
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80750
||      Dosering medicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.dosage.doseQuantity
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80753
||      Bijzonderheden
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-MedicationUse}}
||MedicationStatement.effectivePeriod.note
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80688
||   BMI
||0 .. 1
||
||
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80689
||      Datum bepaling
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10806
||      BMI vrouw
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-120 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80675
||   Vrouwelijke genitale verminking?
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-177 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80676
||   Type vrouwelijke genitale verminking
||0 .. 1
||[[Gebz:FHIR_bc-MaternalObservation|bc-MaternalObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-172 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10807
||   Actuele bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10808
||      Actuele bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10809
||      Actuele bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-184 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10810
||   Bloedgroep vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-79 example]
||
* GET [base]/Observation?code=883-9{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10811
||   Rhesus D Factor vrouw
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
* GET [base]/Observation?code=1305-2{&subject=[vrouwid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10816
||   Rhesus c Factor
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-82 example]
||
* GET [base]/Observation?code=1159-3{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80633
||   Partner
||0 .. 1
||{{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=nl-core-RelatedPerson}}
||RelatedPerson
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80638
||      Persoonsnaam
||0 .. 1
||
||
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80639
||         Voornamen
||0 .. 1
||
||
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80640
||         Voorvoegsel
||0 .. 1
||
||
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80641
||         Achternamen
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80636
||      Etniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||17
||Obstetrische anamnese gegroepeerd per voorgaande zwangerschap
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy}}
||Condition
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||18
||   Eerdere bevalling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||19
||      Vorige uitkomst (per kind)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80709
||         Vorige baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80710
||            Werkelijke plaats baring (type locatie)
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||21
||            Kindspecifieke gegevens vorige uitkomsten
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80624
||               Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||3
||Zwangerschap
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy}}
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-10 example]
||
* GET [base]/Condition/[zwangerschapid]
* GET [base]/Condition?clinicalstatus=active
* GET [base]/Condition?clinicalstatus=inactive&_sort=_-id&_count=1
* GET [base]/Condition?subject=[patientid]&_revinclude=Observation:focus
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80664
||   Casemanager naam
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-MaternalRecord|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-MaternalRecord}}
||EpisodeOfCare.careManager.display
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20010
||   Graviditeit
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Gravidity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Gravidity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-84 example]
||
* GET [base]/Observation?code=11996-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20150
||   Pariteit (vóór deze zwangerschap)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-Parity|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-Parity}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-88 example]
||
* GET [base]/Observation?code=11977-6{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80617
||   Aantal levende kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-112 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80678
||   Fetal Loss
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20029
||   A terme datum (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20030
||      A terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-83 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20040
||      Datum bepaling à terme datum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20050
||      A terme datum o.b.v.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-pregnancy-TermDate|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-pregnancy-TermDate}}
||Observation.method
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-188 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82160
||   Definitieve à terme datum
||0 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-263 example]
||
* GET [base]/Observation?code=11778-8{&subject=[vrouwid]&context=[dossierid]&focus=[zwangerschapid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80819
||   Foliumzuur gebruik
||0 .. 1
||
||
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20020
||   Hoeveelling
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20130
||   Amnioniciteit
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20140
||   Chorioniciteit
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80732
||   Prenatale controle
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80737
||      Datum controle
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||Encounter.period.start
||[https://simplifier.net/geboortezorg-stu3/encounter-example-duplicate-2 example]
||
|-
|[[Bestand:ANY.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80736
||      Naam zorgverlener
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.display | Practitioner.name
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82067
||      Zorgverlenertype
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Encounter|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Encounter}}
||EpisodeOfCare.participant.individual.extension:practitionerRole.specialty | PractitionerRole.specialty
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80738
||      Zwangerschapsduur
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80746
||      Leven voelen
||1 .. *
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-144 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80810
||      Rookgedrag
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TobaccoUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-TobaccoUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-191 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80747
||      Alcoholgebruik
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AlcoholUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-AlcoholUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-189 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82102
||      Drugsgebruik?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-190 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82103
||      Soort drugs
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-DrugUse}}
||Observation.component:DrugOrMedicationType.valueCodeableConcept
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80832
||      Bloeddruk
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80833
||         Bloeddruk systolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:SystolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80834
||         Bloeddruk diastolisch
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BloodPressure}}
||Observation.component:DiastolicBP.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20211
||      Gewicht (gemeten)
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyWeight}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-187 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80621
||      Uitwendig onderzoek
||1 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82105
||         Hartactie
||1 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82106
||            Regelmaat hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82107
||            Frequentie hartslag
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80745
||         Hartactie op basis van
||1 .. 1
||[[Gebz:FHIR_bc-FetusObservation|bc-FetusObservation]]
||Observation.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82268
||   Diagnose
||0 .. *
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82272
||      Datum
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-21 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82285
||      Zwangerschapsduur
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82269
||      Gynaecologische aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-26 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82270
||      Bloedverlies?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-17 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82286
||      Partiële mola?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-35 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82271
||      Cervixinsufficiëntie?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-18 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82273
||      Infectie
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-29 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82274
||      Hyperemesis gravidarum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-27 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82275
||      Hypertensieve aandoening
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-28 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82276
||      Zwangerschapscholestase?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-14 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82277
||      Diabetes gravidarum met insuline?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-22 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82278
||      Afwijkende groei foetus
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-16 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82279
||      Dreigende partus immaturus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-23 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82280
||      Dreigende partus prematurus?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-24 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82289
||      Abruptio placentae?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-15 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82452
||      Navelstrengprolaps?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-32 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82380
||      Liggingsafwijking
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfPregnancy|bc-DisorderOfPregnancy]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-31 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||83405
||      Meerlingzwangerschap?
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||84193
||      Serotiniteit?
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80613
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82435
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82377
||   Interventie
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82376
||      Interventie
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82230
||   Intra-uteriene behandeling
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-9 example]
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||6
||Bevalling
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example example]
||
* GET [base]/Procedure?code=236973005{&subject=[vrouwid]&context=[dossierid]&reasonReference=[zwangerschapid]}
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20500
||   Partusnummer
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-DeliveryProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-DeliveryProcedure}}
||Procedure.identifier
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82291
||   Diagnose bevalling
||1 .. *
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82381
||      Datum
||1 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.assertedDate
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82382
||      Zwangerschapsduur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Pregnancy-PregnancyDuration}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82338
||      PPROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-37 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82290
||      PROM?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-39 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82292
||      Koorts?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-30 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82293
||      Niet vorderende ontsluiting?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-33 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82294
||      Niet vorderende uitdrijving?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-34 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82296
||      Verdenking foetale nood?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-43 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82443
||      Intra-uteriene vruchtdood
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82444
||         Vermoeden intra-uteriene vruchtdood?
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-254 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82295
||      Vastzittende placenta?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-42 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82398
||      Fluxus postpartum?
||0 .. 1
||[[Gebz:FHIR_bc-DisorderOfLaborAndDelivery|bc-DisorderOfLaborAndDelivery]]
||Condition.code
||[https://simplifier.net/geboortezorg-stu3/condition-example-duplicate-25 example]
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20505
||   Aantal geboren kinderen
||0 .. 1
||[[Gebz:FHIR_bc-PregnancyObservation|bc-PregnancyObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-111 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20555
||   Interventies begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20560
||      Interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20570
||      Indicatie interventie begin baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-10 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20550
||   Wijze waarop de baring begon
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-178 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20590
||   Tijdstip begin actieve ontsluiting
||0 .. 1
||[[Gebz:FHIR_bc-DeliveryObservation|bc-DeliveryObservation]]
||Observation.valueDateTime
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-63 example]
||
* GET [base]/Observation?code=249120008{&subject=[vrouwid]&context=[dossierid]&focus=[bevallingid]}
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||7
||Uitkomst (per kind)
||0 .. *
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40002
||   Baring
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Birth|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Birth}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-4 example]
||
* GET [base]/Procedure?code=3950001{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]&focus=[kindid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40003
||      Werkelijke plaats baring (type locatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ChildBirthAssistance|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ChildBirthAssistance}}
||Encounter.class:werkelijkePlaatsBaring
||[https://simplifier.net/geboortezorg-stu3/encounter-example example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40006
||      Demografische gegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient
||
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40007
||         Identificaties kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40010
||            BSN kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier:BSN
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:II.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40011
||            Lokale identificatie kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40015
||            Identificatie kind PRN formaat
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.identifier
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82051
||         Naamgegevens kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82353
||            Voornamen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82354
||            Initialen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82052
||            Roepnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.given
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82053
||            Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82054
||               Voorvoegsel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannamePrefix
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82055
||               Achternaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.name.family.humannameOwnName
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82364
||         Contactgegevens
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82365
||            Telefoonnummers
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82366
||               Soort telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.use
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82367
||               Telefoonnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.telecom.value
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40032
||         Adres t.b.v. hielprik
||0 .. 1
||
||
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82133
||            Straatnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:streetName
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82134
||            Huisnummer
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:houseNumber
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82135
||            Huisletter/huisnummertoevoeging
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.line.extension:buildingNumbersuffix
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82136
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82137
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patientaddress.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82138
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.country
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82139
||            Adrestype
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.extension:AddressType
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40033
||         Adres
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40034
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.address.postalCode
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40040
||         Geslacht (administratief)
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40041
||         Geslacht (medische observatie)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.gender.Extension
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40050
||         Geboortedatum
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.birthdate & patient.birthtime (extension)
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
* GET [base]/Patient/[kindid]
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40004
||         Geboorteplaats
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80629
||            Postcode
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.postalCode
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80630
||            Plaatsnaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.city
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80631
||            Gemeentenaam
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension:birthPlace.district
||
||
|-
|[[Bestand:ST.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80632
||            Land
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.extension.birthPlace.country
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82087
||         Meerlingindicatie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthBoolean
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40025
||         Rangnummer kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-Child|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-Child}}
||Patient.multipleBirthInteger
||[https://simplifier.net/geboortezorg-stu3/patient-example-duplicate-5 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||71
||      Kindspecifieke maternale gegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20616
||         Bijstimulatie toegediend?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-6 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20579
||         Amniotomie (groep)
||0 .. 1
||
||
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||20580
||            Amniotomie?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80794
||         Indicatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||30055
||         Locatie episiotomie
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.bodySite.extension
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-8 example]
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82090
||         Pijnbestrijding?
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82091
||         Pijnbestrijding
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.category
||
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82394
||            Datum/tijd
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.effectiveDateTime
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82093
||            Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82092
||               Methode
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.method
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82094
||               Overig middel
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.dosage.route
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82095
||                  Middel
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PainRelief|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PainRelief}}
||MedicationAdministration.medicationCodeableConcept
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||72
||      Kindspecifieke uitkomstgegevens
||0 .. 1
||
||
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80626
||         Type partus
||0 .. 1
||[[Gebz:FHIR_bc-BirthObservation|bc-BirthObservation]]
||Observation.valueCode
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-67 example]
||
* GET [base]/Observation?code=364336006{&subject=[vrouwid]&context=[dossierid]&focus=[geboorteid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40189
||         Vaginale kunstverlossing (groep)
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40190
||            Vaginale kunstverlossing
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-3 example]
||
* GET [base]/Procedure?code=3311000146109{&subject=[vrouwid]&context=[dossierid]&partof=[bevallingid,uitdrijvingsfaseid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40210
||            Indicatie vaginale kunstverlossing
||0 .. 1
||
||
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40219
||         Sectio caesarea (group)
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.code
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82546
||            Indicatie primaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||82547
||            Indicatie secundaire sectio
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-ObstetricProcedure|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-ObstetricProcedure}}
||Procedure.reasonCode
||[https://simplifier.net/geboortezorg-stu3/procedure-example-duplicate-11 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80766
||         Lichamelijk onderzoek kind
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PhysicalExamination|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PhysicalExamination}}
||DiagnosticReport
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40070
||            Apgarscore na 1 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40071
||            Apgarscore na 5 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-77 example]
||
* GET [base]/Observation?code=9274-2{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:INT.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80757
||            Apgarscore na 10 min.
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-ApgarScore}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40060
||            Geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-180 example]
||
* GET [base]/Observation?code=8339-4{&subject=[kindid]&context=[dossierid]}
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80670
||            Percentiel van het geboortegewicht
||0 .. 1
||[[Gebz:FHIR_bc-ChildObservation|bc-ChildObservation]]
||Observation.interpretation.extension:percentile
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-185 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80759
||            Lengte
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-BodyHeight}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80760
||            Schedelomtrek
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HeadCircumference|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-HeadCircumference}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E8D7BE;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||14
||Medisch onderzoek
||0 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-
|[[Bestand:TS.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||50020
||   Datum onderzoek
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/bc-PregnancyUltraSound|nictiz.fhir.nl.stu3.geboortezorg|pkgVersion=1.0.0|title=bc-PregnancyUltraSound}}
||DiagnosticReport.effectiveDateTime
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-2 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||142
||   Maternale onderzoeksgegevens
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80959
||      Urine-, bloed- en aanvullende onderzoeken
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80949
||         PSIE
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-DiagnosticReport}}
||DiagnosticReport
||[https://simplifier.net/geboortezorg-stu3/diagnosticreport-example-duplicate-3 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80952
||            Bloedgroep vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80953
||            Rhesus D Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80954
||            Rhesus c Factor vrouw
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80955
||            HBsAg
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80956
||            HIV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80957
||            Lues
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||
||
|-
|[[Bestand:BL.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10812
||            Irregulaire antistoffen?
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueBoolean
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-181 example]
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10813
||            Welke irregulaire antistoffen vrouw aanwezig.
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-260 example]
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||10814
||         Hb
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-80 example]
||
* GET [base]/Observation?code=718-7{&subject=[vrouwid]&context=[dossierid]}
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80991
||         Anemie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80951
||            MCV
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80992
||            Hb-pathie
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-Problem}}
||Condition.code
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80993
||            Vit. B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80994
||            Actief-B12
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80995
||            Ferritine
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80996
||            Foliumzuur
||1 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80963
||         Schildklier diagnostiek
||0 .. 1
||
||
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80962
||            TSH receptor antistoffen
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80964
||            Vrij T4
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80965
||            TSH
||0 .. 1
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-style="vertical-align:top; background-color: #E3E3E3;"
|[[Bestand:Container.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80966
||         TORCH
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80967
||            Toxoplasmose IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80968
||            Toxoplasmose IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80969
||            Rubella IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:PQ.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80970
||            Rubella IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80971
||            CMV IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80972
||            CMV IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80973
||            Herpes IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80974
||            Herpes IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80975
||            Parvovirus IgG
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||80976
||            Parvovirus IgM
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueQuantity
||
||
|-
|[[Bestand:CD.png|16px|link=Beschrijving_en_gebruik_datatypes]]
||40051
||         Rhesus D Factor foetus
||1 .. *
||{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation|nictiz.fhir.nl.stu3.zib2017|pkgVersion=2.0.0|title=zib-LaboratoryTestResult-Observation}}
||Observation.valueCodeableConcept
||[https://simplifier.net/geboortezorg-stu3/observation-example-duplicate-81 example]
||
|}
<section end=transaction />

vpk:V3.1 FHIR eOverdracht

2021-01-25T12:20:28Z

Stephan Opdenberg: Added the Comfortscore, FLACCPijnscore and ChecklijstPijnscore elements to the Child (0-1) overdrachtsbericht table

{{DISPLAYTITLE:eOverdracht FHIR Implementation Guide}}
{{IssueBox|Work in progress - See [[vpk:V3.1_FHIR_eOverdracht_Proeftuin|official publication]] here.}}
=Introduction=

This page details the HL7 FHIR requirements for exchanging the data in the eOverdracht described in [[vpk:V3.1_Ontwerp_eOverdracht|the functional design]].

Implementation of these transactions is spread over multiple phases. In the first phase of the Proeftuin a simplified version of both the Aanmeldbericht en Overdrachtsbericht are being used. Both messages exist of four HCIMs listed in the table below. The Aanmeldbericht is send to the recieving organisation, which after confirmation of recieving the aanmeldberricht, gets send the Overdrachtbericht.
Phase two consists of the complete Aanmeldbericht as well as an incomplete Overdrachtsbericht. The Overdrachtsbericht is a subset of 11 HCIM's (complete set used in Aanmeldbericht) and an unstructured PDF containing the remaining data which are not part of the HCIM's.
Phase three is the complete dataset of the Aanmeldbericht, Overdrachtsbericht Volwassenen, Overdrachtsbericht Kinderen 0-1 jaar, Overdrachtsbericht Kinderen 1-18 jaar as PUSH messages.

This implementation guide assumes that the reader is familiar with [https://www.hl7.org/fhir/stu3/ FHIR(STU3)].

==Overarching FHIR principles==
* This implementation guide does not provide information on finding the right XIS, nor does it provide information about security. It is assumed that the sending XIS is able to make a connection with the receiving XIS.
* All FHIR resources used within eOverdracht SHALL conform to the profiles listed in this implementation guide and SHALL include the profile canonical URL in their <code>meta.profile</code> element.

==Package and dependencies==
eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{VersieInfo|package|release=V2019.01}}].
==Example instances==
Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Composition Composition examples]
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Bundle Bundle examples]

=Use case 1A: Send Overdrachtsbericht volwassenen (PUSH)=
'''NB:''' The use cases as publiced here are with reservation. Depending on the outcome of a discussion about the scenario's with third parties implementing this standard, the use cases might differ. However the cotnent of the uses cases will remain the same as stated below.
==Introduction==
The Send Overdrachtsbericht scenario is used by the sending XIS to send the relevant data for the patient care to the receiving XIS. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_volwassenen|Opbouw Overdrachtsbericht Volwassenen]].
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Overdrachtbericht (PUSH)
|style="background-color: white;" rowspan="2"|Send Overdrachtsbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Overdrachtsbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Overdrachtsbericht
|}
==Invocation==
The Send Overdrachtsbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Overdrachtsbericht (complete)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.
==Structure of the Overdrachtsbericht (complete)==
The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

The table below lists the FHIR profiles<ref name="nopackage">Please note that the direct links to the various conformance resources below will take you to the latest version, which might not match the package version. At time of writing, there is no way to render the conformance resource as found in the package. This is on the roadmap for Simplifier.</ref> that are applicable for the pilot implementation of the Overdrachtsbericht transaction.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Administratieve gegevens
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|title=eOverdracht aanmeldbericht}}
| Composition
| -
| -
| Declaration of the Send Aanmeldbericht transaction.
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|title=eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="4"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|title=nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|title=zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|title=nl-core-relatedperson}}
| RelatedPerson
| rowspan="2"|Contactpersoon
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|title=nl-core-patient}}
| Patient
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|title=nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|title=nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| rowspan="2"| Zorgverlener sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|title=nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|title=nl-core-practitionerrole}}
| PractitionerRole
|-
| rowspan="2"| Zorgverlener ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|title=nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|title=nl-core-practitionerrole}}
| PractitionerRole
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Algemene patiënten context
|-
| Gezinssituatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FamilySituation|title=zib-FamilySituation}}
| FamilySituation
| Gezinssituatie
| v3.1(2017NL)
| -
|-
| Woonomgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LivingSituation|title=zib-LivingSituation}}
| Woonsituatie
| LivingSituation
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Levensovertuiging
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LifeStance|title=zib-LifeStance}}
| Levensovertuiging
| LifeStance
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AdvanceDirective|title=zib-AdvanceDirective}}
| Wilsverklaring
| AdvanceDirective
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Sociale omgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ParticipationInSociety|title=zib-ParticipationInSociety}}
| ParticipatieInMaatschappij
| ParticipationInSociety
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HelpFromOthers|title=zib-HelpFromOthers}}
| HulpVanAnderen
| HelpFromOthers
| v3.0 (2017NL)
| -
|-
| Communicatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/patient-proficiency|title=patient-proficiency}}
| Taalvaardigheid
| LanguageProfeciency
| v3.1(2017NL)
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Medische context
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|title=zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|title=zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| rowspan="7"| Meetwaarden
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|title=zib-BloodPressure}}
| Observation
| Bloeddruk
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PulseRate|title=zib-PulseRate}}
| Observation
| PolsFrequentie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyTemperature|title=zib-BodyTemperature}}
| Observation
| Lichaamstemperatuur
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Respiration|title=zib-Respiration}}
| Observation
| Ademhaling
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|title=zib-BodyWeight}}
| Observation
| Lichaamsgewicht
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|title=zib-BodyHeight}}
| Observation
| Lichaamslengte
| v3.1(2017NL)
| -
|-
| [https://zibs.nl/wiki/AlgemeneMeting-v3.0(2017NL) AlgemeneMeting]
| Observation
| AlgemeneMeting
| v3.0(2017NL)
| No FHIR profile is available yet for this HCIM.
|-
| Pijnscore
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PainScore|title=zib-PainScore}}
| Observation
| Pijnscore
| v3.1(2017NL)
| -
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: zorgplan
|-
| rowspan="3"| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TreatmentObjective|title=zib-TreatmentObjective}}
| Goal
| Behandeldoel
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NursingIntervention|title=zib-NursingIntervention}}
| Procedure
| VerpleegkundigeInterventie
| v3.2(2018NL)
| -
|-
| Zorgresultaat
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-OutcomeOfCare|title=zib-OutcomeOfCare}}
| DiagnisticReport
| UitkomstVanZorg
| v3.1(2017NL)
| -
|-
| rowspan="3"|Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|title=zib-ProcedureRequest}}
| ProcedureRequest
| rowspan="3"|OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eAfspraak-Appointment|title=eAfspraak-Appointment}}
| Appointment
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VaccinationRecommendation|title=zib-VaccinationRecommendation}}
| ImmunizationRecommendation
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|title=eOverdracht aanmeldbericht profile}}.
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: specificatie gezondheidstoestand
|-
| rowspan="12"| Zelfzorg
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToDrink|title=zib-AbilityToDrink}}
| Observation
| VermogenTotDrinken
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToEat|title=zib-AbilityToEat}}
| Observation
| VermogenTotEten
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities|title=zib-AbilityToPerformMouthcareActivities}}
| Observation
| rowspan="3"|VermogenTotMondverzorging
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities-MedicalDevice|title=zib-AbilityToPerformMouthcareActivities-MedicalDevice}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities-MedicalDeviceProduct|title=zib-AbilityToPerformMouthcareActivities-MedicalDeviceProduct}}
| Device
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToWashOneSelf|title=zib-AbilityToWashOneSelf}}
| Observation
| VermogenTotZichWassen
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToDressOneself|title=zib-AbilityToDressOneself}}
| Observation
| VermogenTotZichKleden
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToGroome|title=zib-AbilityToGroome}}
| Observation
| VermogenTotUiterlijkeVerzorging
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToUseToilet|title=zib-AbilityToUseToilet}}
| Observation
| VermogenTotToiletgang
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToManageMedication|title=zib-AbilityToManageMedication}}
| Observation
| VermogenTotZelfstandigMedicatiegebruik
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformNursingActivities|title=zib-AbilityToPerformNursingActivities}}
| Observation
| VermogenTotVerpleegtechnischeHandelingen
| v1.0(2017NL)
| -
|-
| toelichting zelfzorg
| -
| Explanation selfcare
| -
| Free text
|-
| Mobiliteit
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Mobility|title=zib-Mobility}}
| Observation
| Mobiliteit
| v3.1(2017NL)
| -
|-
| rowspan="7"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NutritionAdvice|title=zib-NutritionAdvice}}
| NutritionOrder
| Voedingsadvies
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SNAQScore|title=zib-SNAQScore}}
{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SNAQrcScore|title=zib-SNAQrcScore}}

{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SNAQrcScore|title=zib-SNAQ65+Score}}

{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MUSTScore|title=zib-MUSTScore}}
| Observation
| SNAQScore

SNAQrcScore

SNAQ65+Score

MUSTScore
|v3.1(2017NL)

v1.0(2017NL)

v1.0(2017NL)

v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FluidBalance|title=zib-FluidBalance}}
| Observation
| Vochtbalans
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|title=zib-FeedingTubeSystem}}
| DeviceUseStatement
| rowspan="2"|SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-Product|title=zib-FeedingTubeSystem-Product}}
| Device
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|title=zib-Infusion}}
| DeviceUseStatement
| rowspan="2"|Infuus
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion-Product|title=zib-Infusion-Product}}
| Device
| v3.2(2017NL)
| -
|-
| rowspan="3"|Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BladderFunction|title=zib-BladderFunction}}
| Observation
| Blaasfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BowelFunction|title=zib-BowelFunction}}
| Observation
| Darmfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|title=zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|-
| rowspan="4"| Huid
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BurnWound|title=zib-Burnwound}}
| Condition
| Brandwond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PressureUlcer|title=zib-PressureUlcer}}
| Condition
| DecubitusWond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SkinDisorder|title=zib-SkinDisorder}}
| Condition
| Huidaandoening
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Wound|title=zib-Wound}}
| Condition
| Wond
| v3.1(2017NL)
| -
|-
| rowspan="6"| Zintuigen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction|title=zib-HearingFunction}}
| Observation
| rowspan="3"| FunctieHoren
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid|title=zib-HearingFunction-HearingAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid-Product|title=zib-HearingFunction-HearingAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction|title=zib-VisualFunction}}
| Observation
| rowspan="3"|FunctieZien
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAid|title=zib-VisualAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAidProduct|title=zib-VisualAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| Ziektebeleving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-IllnessPerception|title=zib-IllnessPerception}}
| Observation
| Ziektebeleving
| v3.1(2017NL)
| -
|-
| Mentale status
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| rowspan="7"| Voortplanting
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy|title=zib-Pregnancy}}
| Condition
| Zwangerschap
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyStatus|title=zib-Pregnancy-PregnancyStatus}}
| Observation
| Zwanger
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-TermDate|title=zib-Pregnancy-TermDate}}
| Observation
| ATermDatum
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|title=zib-PregnancyDuration}}
| Observation
| Zwangerschapsduur
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-Parity|title=zib-Pregnancy-Parity}}
| Observation
| Pariteit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-Gravidity|title=zib-Pregnancy-Gravidity}}
| Observation
| Graviditeit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-DateLastMenstruation|title=zib-Pregnancy-DatelastMenstruation}}
| Observation
| DatumLaatsteMenstruatie
| v3.1(2017NL)
| -
|-
|}

=Use Case 2A: Send overdrachtsbericht kindzorg=
'''NB:''' The use cases as publiced here are with reservation. Depending on the outcome of a discussion about the scenario's with third parties implementing this standard, the use cases might differ. However the cotnent of the uses cases will remain the same as stated below.
==Introduction==
The Send Overdrachtsbericht scenario is used by the sending XIS to send the relevant data for the patient care to the receiving XIS.
For the use case "kindzorg" we distinquish between two age categories:
* Child between 0-1 years of age (zie ook [[vpk:v3.1_Opbouw_eOverdracht_kind_0_1|inhoudelijke opbouw van de verpleegkundige overdracht voor kinderen tussen 0-1 jaar]])
* Child between 1-18 years of age (zie ook [[vpk:v3.1_Opbouw_eOverdracht_kind_1_18|inhoudelijke opbouw van de verpleegkundige overdracht voor kinderen tussen 1-18 jaar]])
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Overdrachtbericht (PUSH)
|style="background-color: white;" rowspan="2"|Send Overdrachtsbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Overdrachtsbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Overdrachtsbericht
|}
==Invocation==
The Send Overdrachtsbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Overdrachtsbericht (Child 0-1)]] or [[#Structure of Overdrachtsbericht (Child 1-18)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.

==Structure of the Overdrachtsbericht (Child 0-1)==
The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

The table below lists the FHIR profiles<ref name="nopackage">Please note that the direct links to the various conformance resources below will take you to the latest version, which might not match the package version. At time of writing, there is no way to render the conformance resource as found in the package. This is on the roadmap for Simplifier.</ref> that are applicable for the implementation of the Overdrachtsbericht transaction.
{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Administratieve gegevens
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|title=eOverdracht aanmeldbericht}}
| Composition
| -
| -
| Declaration of the Send Aanmeldbericht transaction.
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|title=eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="4"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|title=nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|title=zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|title=nl-core-relatedperson}}
| RelatedPerson
| rowspan="2"|Contactpersoon
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|title=nl-core-patient}}
| Patient
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|title=nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|title=nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| rowspan="2"| Zorgverlener sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|title=nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|title=nl-core-practitionerrole}}
| PractitionerRole
|-
| rowspan="2"| Zorgverlener ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|title=nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|title=nl-core-practitionerrole}}
| PractitionerRole
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Algemene patiënten contact
|-
| Gezinssituatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FamilySituation|title=zib-FamilySituation}}
| FamilySituation
| Gezinssituatie
| v3.1(2017NL)
| -
|-
| Woonomgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LivingSituation|title=zib-LivingSituation}}
| Woonsituatie
| LivingSituation
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Levensovertuiging
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LifeStance|title=zib-LifeStance}}
| Levensovertuiging
| LifeStance
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AdvanceDirective|title=zib-AdvanceDirective}}
| Wilsverklaring
| AdvanceDirective
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Sociale omgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ParticipationInSociety|title=zib-ParticipationInSociety}}
| ParticipatieInMaatschappij
| ParticipationInSociety
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HelpFromOthers|title=zib-HelpFromOthers}}
| HulpVanAnderen
| HelpFromOthers
| v3.0 (2017NL)
| -
|-
| Communicatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/patient-proficiency|title=patient-proficiency}}
| Taalvaardigheid
| LanguageProfeciency
| v3.1(2017NL)
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Medische context
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|title=zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|title=zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| rowspan="9"| Meetwaarden
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|title=zib-BloodPressure}}
| Observation
| Bloeddruk
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PulseRate|title=zib-PulseRate}}
| Observation
| PolsFrequentie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyTemperature|title=zib-BodyTemperature}}
| Observation
| Lichaamstemperatuur
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Respiration|title=zib-Respiration}}
| Observation
| Ademhaling
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|title=zib-BodyWeight}}
| Observation
| Lichaamsgewicht
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|title=zib-BodyHeight}}
| Observation
| Lichaamslengte
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HeadCircumference|title=zib-HeadCircumference}}
| Observation
| Schedelomvang
| v1.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|title=zib-ApgarScore}}
| Observation
| ApgarScore
| v1.0(2017NL)
| -
|-
| [https://zibs.nl/wiki/AlgemeneMeting-v3.0(2017NL) AlgemeneMeting]
| Observation
| AlgemeneMeting
| v3.0(2017NL)
| No fhir profile is available yet for this HCIM.
|-
| rowspan="4"|Pijnscore
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PainScore|title=zib-PainScore}}
| Observation
| Pijnscore
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ComfortScale|title=zib-ComfortScale}}
| Observation
| ComfortScore
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FLACCPainScale|title=zib-FLACCPainScale}}
| Observation
| FLACCPijnScore
| v1.0(2017)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ChecklistPainBehaviour|title=zib-ChecklistPainBehaviour}}
| Observation
| ChecklijstPijnScore
| v1.0(2017NL)
| -
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: zorgplan
|-
| rowspan="3"| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TreatmentObjective|title=zib-TreatmentObjective}}
| Goal
| Behandeldoel
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NursingIntervention|title=zib-NursingIntervention}}
| Procedure
| VerpleegkundigeInterventie
| v3.2(2018NL)
| -
|-
| Zorgresultaat
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-OutcomeOfCare|title=zib-OutcomeOfCare}}
| DiagnisticReport
| UitkomstVanZorg
| v3.1(2017NL)
| -
|-
| rowspan="3"|Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|title=zib-ProcedureRequest}}
| ProcedureRequest
| rowspan="3"|OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eAfspraak-Appointment|title=eAfspraak-Appointment}}
| Appointment
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VaccinationRecommendation|title=zib-VaccinationRecommendation}}
| ImmunizationRecommendation
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|title=eOverdracht aanmeldbericht profile}}.
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: specificatie gezondheidstoestand
|-
| rowspan="2"| Zelfzorg
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformNursingActivities|title=zib-AbilityToPerformNursingActivities}}
| Observation
| VermogenTotVerpleegtechnischeHandelingen
| v1.0(2017NL)
| -
|-
| toelichting zelfzorg
| -
| Explanation selfcare
| -
| Free text
|-
| rowspan="8"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NutritionAdvice|title=zib-NutritionAdvice}}
| NutritionOrder
| Voedingsadvies
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingPatternInfant|title=zib-FeedingPatternInfant}}
| Observation
| VoedingspatroonZuigeling
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-StrongKidsScore|title=zib-StrongKidsScore}}
| Observation
| StrongKidsScore
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FluidBalance|title=zib-FluidBalance}}
| Observation
| Vochtbalans
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|title=zib-FeedingTubeSystem}}
| DeviceUseStatement
| rowspan="2"|SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-Product|title=zib-FeedingTubeSystem-Product}}
| Device
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|title=zib-Infusion}}
| DeviceUseStatement
| rowspan="2"|Infuus
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion-Product|title=zib-Infusion-Product}}
| Device
| v3.2(2017NL)
| -
|-
| rowspan="3"|Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BladderFunction|title=zib-BladderFunction}}
| Observation
| Blaasfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BowelFunction|title=zib-BowelFunction}}
| Observation
| Darmfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|title=zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|-
| rowspan="4"| Huid
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BurnWound|title=zib-Burnwound}}
| Condition
| Brandwond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PressureUlcer|title=zib-PressureUlcer}}
| Condition
| DecubitusWond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SkinDisorder|title=zib-SkinDisorder}}
| Condition
| Huidaandoening
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Wound|title=zib-Wound}}
| Condition
| Wond
| v3.1(2017NL)
| -
|-
| rowspan="6"| Zintuigen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction|title=zib-HearingFunction}}
| Observation
| rowspan="3"| FunctieHoren
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid|title=zib-HearingFunction-HearingAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid-Product|title=zib-HearingFunction-HearingAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction|title=zib-VisualFunction}}
| Observation
| rowspan="3"|FunctieZien
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAid|title=zib-VisualAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAid-Product|title=zib-VisualAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| Ziektebeleving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-IllnessPerception|title=zib-IllnessPerception}}
| Observation
| Ziektebeleving
| v3.1(2017NL)
| -
|-
| Mentale status
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| Ontwikkeling kind
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DevelopmentChild|title=zib-DevelopmentChild}}
| Observation
| Ontwikkeling kind
| v1.1(2017NL)
| -
|-
| Overige bijzonderheden kind
| -
| Free text
| -
| -
| Free text for particularities child
|-
|}

==Structure of Overdrachtsbericht (Child 1-18)==
The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

The table below lists the FHIR profiles<ref name="nopackage">Please note that the direct links to the various conformance resources below will take you to the latest version, which might not match the package version. At time of writing, there is no way to render the conformance resource as found in the package. This is on the roadmap for Simplifier.</ref> that are applicable for the implementation of the Overdrachtsbericht transaction.
{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Administratieve gegevens
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|title=eOverdracht aanmeldbericht}}
| Composition
| -
| -
| Declaration of the Send Aanmeldbericht transaction.
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|title=eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="4"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|title=nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|title=zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|title=nl-core-relatedperson}}
| RelatedPerson
| rowspan="2"|Contactpersoon
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|title=nl-core-patient}}
| Patient
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|title=nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|title=nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| rowspan="2"| Zorgverlener sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|title=nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|title=nl-core-practitionerrole}}
| PractitionerRole
|-
| rowspan="2"| Zorgverlener ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|title=nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|title=nl-core-practitionerrole}}
| PractitionerRole
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Algemene patiënten context
|-
| Gezinssituatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FamilySituation|title=zib-FamilySituation}}
| FamilySituation
| Gezinssituatie
| v3.1(2017NL)
| -
|-
| Woonomgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LivingSituation|title=zib-LivingSituation}}
| Woonsituatie
| LivingSituation
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Levensovertuiging
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LifeStance|title=zib-LifeStance}}
| Levensovertuiging
| LifeStance
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AdvanceDirective|title=zib-AdvanceDirective}}
| Wilsverklaring
| AdvanceDirective
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Sociale omgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ParticipationInSociety|title=zib-ParticipationInSociety}}
| ParticipatieInMaatschappij
| ParticipationInSociety
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HelpFromOthers|title=zib-HelpFromOthers}}
| HulpVanAnderen
| HelpFromOthers
| v3.0 (2017NL)
| -
|-
| Communicatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/patient-proficiency|title=patient-proficiency}}
| Taalvaardigheid
| LanguageProfeciency
| v3.1(2017NL)
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Medische context
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|title=zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|title=zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| rowspan="7"| Meetwaarden
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|title=zib-BloodPressure}}
| Observation
| Bloeddruk
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PulseRate|title=zib-PulseRate}}
| Observation
| PolsFrequentie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyTemperature|title=zib-BodyTemperature}}
| Observation
| Lichaamstemperatuur
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Respiration|title=zib-Respiration}}
| Observation
| Ademhaling
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|title=zib-BodyWeight}}
| Observation
| Lichaamsgewicht
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|title=zib-BodyHeight}}
| Observation
| Lichaamslengte
| v3.1(2017NL)
| -
|-
| [https://zibs.nl/wiki/AlgemeneMeting-v3.0(2017NL) AlgemeneMeting]
| Observation
| AlgemeneMeting
| v3.0(2017NL)
| No fhir profile is available yet for this HCIM.
|-
| rowspan="4"|Pijnscore
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PainScore|title=zib-PainScore}}
| Observation
| Pijnscore
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ComfortScale|title=zib-ComfortScale}}
| Observation
| ComfortScore
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FLACCPainScale|title=zib-FLACCPainScale}}
| Observation
| FLACCPijnScore
| v1.0(2017)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ChecklistPainBehaviour|title=zib-ChecklistPainBehaviour}}
| Observation
| ChecklijstPijnScore
| v1.0(2017NL)
| -
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: zorgplan
|-
| rowspan="3"| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TreatmentObjective|title=zib-TreatmentObjective}}
| Goal
| Behandeldoel
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NursingIntervention|title=zib-NursingIntervention}}
| Procedure
| VerpleegkundigeInterventie
| v3.2(2018NL)
| -
|-
| Zorgresultaat
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-OutcomeOfCare|title=zib-OutcomeOfCare}}
| DiagnisticReport
| UitkomstVanZorg
| v3.1(2017NL)
| -
|-
| rowspan="3"|Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|title=zib-ProcedureRequest}}
| ProcedureRequest
| rowspan="3"|OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eAfspraak-Appointment|title=eAfspraak-Appointment}}
| Appointment
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VaccinationRecommendation|title=zib-VaccinationRecommendation}}
| ImmunizationRecommendation
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|title=eOverdracht aanmeldbericht profile}}.
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: specificatie gezondheidstoestand
|-
| rowspan="12"| Zelfzorg
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToDrink|title=zib-AbilityToDrink}}
| Observation
| VermogenTotDrinken
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToEat|title=zib-AbilityToEat}}
| Observation
| VermogenTotEten
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities|title=zib-AbilityToPerformMouthcareActivities}}
| Observation
| rowspan="3"|VermogenTotMondverzorging
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities-MedicalDevice|title=zib-AbilityToPerformMouthcareActivities-MedicalDevice}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities-MedicalDeviceProduct|title=zib-AbilityToPerformMouthcareActivities-MedicalDeviceProduct}}
| Device
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToWashOneSelf|title=zib-AbilityToWashOneSelf}}
| Observation
| VermogenTotZichWassen
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToDressOneself|title=zib-AbilityToDressOneself}}
| Observation
| VermogenTotZichKleden
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToGroome|title=zib-AbilityToGroome}}
| Observation
| VermogenTotUiterlijkeVerzorging
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToUseToilet|title=zib-AbilityToUseToilet}}
| Observation
| VermogenTotToiletgang
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToManageMedication|title=zib-AbilityToManageMedication}}
| Observation
| VermogenTotZelfstandigMedicatiegebruik
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformNursingActivities|title=zib-AbilityToPerformNursingActivities}}
| Observation
| VermogenTotVerpleegtechnischeHandelingen
| v1.0(2017NL)
| -
|-
| toelichting zelfzorg
| -
| Explanation selfcare
| -
| Free text
|-
| Mobiliteit
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Mobility|title=zib-Mobility}}
| Observation
| Mobiliteit
| v3.1(2017NL)
| -
|-
| rowspan="7"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NutritionAdvice|title=zib-NutritionAdvice}}
| NutritionOrder
| Voedingsadvies
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-StrongKidsScore|title=zib-StrongKidsScore}}
| Observation
| StrongKidsScore
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FluidBalance|title=zib-FluidBalance}}
| Observation
| Vochtbalans
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|title=zib-FeedingTubeSystem}}
| DeviceUseStatement
| rowspan="2"|SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-Product|title=zib-FeedingTubeSystem-Product}}
| Device
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|title=zib-Infusion}}
| DeviceUseStatement
| rowspan="2"|Infuus
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion-Product|title=zib-Infusion-Product}}
| Device
| v3.2(2017NL)
| -
|-
| rowspan="3"|Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BladderFunction|title=zib-BladderFunction}}
| Observation
| Blaasfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BowelFunction|title=zib-BowelFunction}}
| Observation
| Darmfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|title=zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|-
| rowspan="4"| Huid
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BurnWound|title=zib-Burnwound}}
| Condition
| Brandwond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PressureUlcer|title=zib-PressureUlcer}}
| Condition
| DecubitusWond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SkinDisorder|title=zib-SkinDisorder}}
| Condition
| Huidaandoening
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Wound|title=zib-Wound}}
| Condition
| Wond
| v3.1(2017NL)
| -
|-
| rowspan="6"| Zintuigen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction|title=zib-HearingFunction}}
| Observation
| rowspan="3"| FunctieHoren
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid|title=zib-HearingFunction-HearingAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid-Product|title=zib-HearingFunction-HearingAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction|title=zib-VisualFunction}}
| Observation
| rowspan="3"|FunctieZien
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAid|title=zib-VisualAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAid-Product|title=zib-VisualAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| Ziektebeleving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-IllnessPerception|title=zib-IllnessPerception}}
| Observation
| Ziektebeleving
| v3.1(2017NL)
| -
|-
| Mentale status
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| Ontwikkeling kind
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DevelopmentChild|title=zib-DevelopmentChild}}
| Observation
| OntwikkelingKind
| v1.1(2017NL)
| -
|-
| rowspan="7"| Voortplanting
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy|title=zib-Pregnancy}}
| Condition
| Zwangerschap
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyStatus|title=zib-Pregnancy-PregnancyStatus}}
| Observation
| Zwanger
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-TermDate|title=zib-Pregnancy-TermDate}}
| Observation
| ATermDatum
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|title=zib-PregnancyDuration}}
| Observation
| Zwangerschapsduur
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-Parity|title=zib-Pregnancy-Parity}}
| Observation
| Pariteit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-Gravidity|title=zib-Pregnancy-Gravidity}}
| Observation
| Graviditeit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-DateLastMenstruation|title=zib-Pregnancy-DatelastMenstruation}}
| Observation
| DatumLaatsteMenstruatie
| v3.1(2017NL)
| -
|-
| Overige bijzonderheden kind
| -
| -
| free text
| -
| Free text for particularities of child
|-
|}

=Use case 3A: Send Aanmeldbericht (PUSH)=
'''NB:''' The use cases as publiced here are with reservation. Depending on the outcome of a discussion about the scenario's with third parties implementing this standard, the use cases might differ. However the cotnent of the uses cases will remain the same as stated below.
==Introduction==
The Send Aanmeldbericht scenario is used by the sending XIS to send the relevant data for the patient intake to the receiving XIS, and constitutes a subset of the Overdrachtsbericht. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_aanmelding|Opbouw Aanmeldbericht]]. For the pilot a limited subset is implemented.
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht(PUSH)
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Aanmeldbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Aanmeldbericht
|}
==Invocation==
The Send Aanmeldbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Aanmeldbericht]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.

==Structure of the Aanmeldbericht==
The Aanmeldbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

During phase 1, the Aanmeldbericht is based 4 HCIMs (Patient, Betaler, Contactpersoon en Zorgaanbieder) and uses a PDF to send the remaining data unstructured. The table below lists the FHIR profiles<ref name="nopackage"/> that are applicable for the pilot implementation of the Aanmeldbericht transaction. All resources SHALL conform to the profiles listed in this table and SHALL include the profile canonical URL in the <code>meta.profile</code> element.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|title=eOverdracht aanmeldbericht}}
| Composition
| -
| -
| Declaration of the Send Aanmeldbericht transaction.
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|title=eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="3"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|title=nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|title=zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|title=nl-core-relatedperson}}
| RelatedPerson
| Contactpersoon
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|title=nl-core-organization}}
| rowspan="2"| Organization
| rowspan="2"| Zorgaanbieder
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|title=nl-core-organization}}
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|title=zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|title=zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|title=zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|title=zib-ProcedureRequest}}
| ProcedureRequest
| OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|title=eOverdracht aanmeldbericht profile}}.
|-
| rowspan="2"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|title=zib-FeedingTubeSystem}}
| DeviceUseStatement
| SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|title=zib-Infusion}}
| DeviceUseStatement
| Infuus
| v3.2(2017NL)
| -
|-
| Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|title=zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|}

=FHIR Documents=
Both the Aanmeldbericht and the Overdrachtsbericht are sent as a [https://www.hl7.org/fhir/STU3/documents.html FHIR Document]. A document is a FHIR Bundle that assembles all relevant resources that need to be exchanged, together with a [https://www.hl7.org/fhir/STU3/composition.html Composition resource] that summarizes and references all these resources.

A FHIR document is immutable and considered to be attested by a healthcare professional.
==Creating documents==
To construct a document, a FHIR Composition resource is created that summarizes and references all the resources that need to be exchanged. This Composition resource is then placed together with all referenced resources in a Bundle with <code>Bundle.type</code> set to "document". The Composition resource SHALL be the first entry.

Profiles have been created for both the Composition and the document Bundle resources for each transaction within eOverdracht. All documents SHOULD adhere to these profiles, which are summarized in this implementation guide at the transaction level.
==Sending documents==
The document should be sent as an HTTP POST operation on the target XIS's base:
POST [base] {?_format=[mime-type]}
where the body of the POST request is the document.
==Processing documents==
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS and each <code>Bundle.entry</code> should be treated as a <code>create</code> interaction for the <code>Bundle.entry.resource</code>. When the receiving XIS cannot create a new resource because of incorrect data or business rules, it should perform a rollback of the creation of any previous entries.

On success, the target XIS SHALL respond:
* With the HTTP status code 201 Created.
* With the Location header containing the new logical id and version id of the created resource version.
* With a response body set to a Bundle of type "transaction-response", containing one entry for each entry in the request, in the same order, with the outcome of processing the entry. The sender may use the returned Bundle to track the outcomes of processing the entry, and the identities assigned to the resources by the server.

On failure, the target XIS SHALL respond:
* With an HTTP status code set appropriate to the processing outcome:
** When the resource syntax or data is incorrect or invalid, the status code should be 400 Bad Request.
** When the server rejects the content of the resource because of business rules, the status code should be 422 Unprocessable Entity.
** Additional HTTP status code may be used if more appropriate.
* With a response body set to a FHIR [http://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] resource with detailed error messages describing the reason for the error.

=FHIR CapabilityStatements=
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-servercapabilities-phase-one|title=CapabilityStatement server}}
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-clientcapabilities-phase-one|title=CapabilityStatement client}}

=Footnotes=
<references />

FHIR:V1.0 FHIR IG STU3

2021-01-22T09:41:05Z

Stephan Opdenberg: MM-1651 intergration. Change in subsection "Error handling". Changed the example response to an invalid authorization from an HTTP status code 401 to 403 as this is a more common response.

__NOINDEX__
__NUMBEREDHEADINGS__
{{DISPLAYTITLE:FHIR Implementation Guide}}

__TOC__

=Introduction=
This implementation guide describes the considerations for using '''HL7® FHIR®''' in context of information standards that are maintained by Nictiz. It applies specifically to HL7® FHIR® version 3 (STU3).

This implementation guide is aimed at software vendors and developers that need to implement FHIR based information standards maintained by Nictiz. Users of this guide are expected to be familiar with the [https://hl7.org/fhir/STU3 FHIR STU3 specification] and resource processing. Where relevant, links to the FHIR specification are provided. This implementation guide is not intended to be a tutorial on that subject.

<section begin=OverarchingPrinciples />
=Use case overarching principles=
==Content Types and encodings==
Unless stated otherwise, the information standards use the [https://hl7.org/fhir/http.html#mime-type FHIR RESTful framework]. This framework defines at least three content-types to send/retrieve information:
* XML: application/fhir+xml
* JSON: application/fhir+json
* RDF: text/turtle - Not supported in this context

Servers SHALL support both XML and JSON, while clients MAY use either format for the request and the response. For the response, servers SHALL support server-driven content negotiation as described in [https://www.hl7.org/fhir/stu3/http.html#mime-type the FHIR specification]. This means that clients can indicate the desired response format using the optional <code>_format=[mimetype]</code> URL parameter, or the acceptable response format(s) using the <code>Accept</code> header. The URL parameter takes precedence over the header. If a client does not request a specific content-type, then it is server discretion to respond using XML or JSON.

FHIR uses UTF-8 for all request and response bodies. Since the [https://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7.1 HTTP specification (section 3.7.1)] defines a default character encoding of ISO-8859-1, requests and responses SHALL explicitly set the character encoding to UTF-8 using the <code>charset</code> parameter of the MIME-type in the <code>Content-Type</code> header. Requests MAY also specify this <code>charset</code> parameter in the <code>Accept</code> header and/or use the <code>Accept-Charset</code> header.

==Use of coded concepts==
Coded information is extremely important for interoperability between systems. It enables systems to act on information rather than have humans read everything for interpretation - it enables medication related alerts, exercise encouragements because of weight increase, and many more things. In the HCIMs and profiles, we therefore strive for complete coverage of all possible situations.

However it is likely that unknown codes present themselves in the communication, for example because the sending system has updated its medication codes to a newer version than the receiving system, or because an older record item is coded in a way that now has been deprecated. It is therefore vital that, in addition to the code itself, the sender includes the semantics of the code. Therefore, systems SHOULD include [https://hl7.org/fhir/STU3/datatypes.html#coding {{fhir|(CodeableConcept).coding.display}}] and/or [https://hl7.org/fhir/STU3/datatypes.html#codeableconcept {{fhir|CodeableConcept.text}}] for coded data in FHIR instances. These fields may only be absent in rare circumstances, for example when dealing with historic data, or in data acquired without such info from a third party.

===Mapping of coded concepts===
Terminology from HCIMs or UCSDs (use case specific datasets) needs to be faithfully applied to the FHIR profiles, but this is not directly possible when the base FHIR resource defines required terminology that bears no direct relationship with the HCIM or UCSD. These cases include, but are not limited to, the FHIR resource elements of datatype {{datatype|code}} ({{fhir|Patient.gender}}, {{fhir|status}} elements, structural type elements, etc.). This datatype always describes FHIR specific terminology, which usually doesn't align with the HCIM/UCSD terminology.

In these cases, a mapping will be provided to explain the relationship between de HCIM/UCSD terminology and the FHIR terminology. This is normally done through a FHIR [https://hl7.org/fhir/STU3/conceptmap.html ConceptMap], which can translate between the terminology used in the HCIM/UCSD, and the terminology that FHIR instances need to adhere to. Usually, the original terminology from the HCIM/UCSD will be communicated as well by adding the extension [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/StructureDefinition/code-specification code-specification] on the same element. This allows unambiguous interpretation on the receiver end.

Example snippet from an {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance|title=AllergyIntolerance}} where both the FHIR terminology {{term|high}} and the SNOMED CT {{term|24484000}} terminology are communicated. The FHIR terminology is obtained from the HCIM terminology using ConceptMap {{Simplifier|http://nictiz.nl/fhir/ConceptMap/MateVanKritiekZijnCodelijst-to-allergy-intolerance-criticality|title=MateVanKritiekZijnCodelijst-to-allergy-intolerance-criticality}}:

<syntaxhighlight lang="xml">
<criticality value="high">
<extension url="http://nictiz.nl/fhir/StructureDefinition/code-specification">
<valueCodeableConcept>
<coding>
<system value="http://snomed.info/sct"/>
<code value="24484000"/>
<display value="Severe"/>
</coding>
</valueCodeableConcept>
</extension>
</criticality>
</syntaxhighlight>

'''Please note''': Unfortunately, FHIR doesn't have a core structured way for indicating which ConceptMaps to use. Instead, mappings are documented in the description of the element in the profile and/or specifically on the mapping description contained in the element.

To retrieve the indicated ConceptMap on Simplifier, the canonical url from the description needs to be used as search term. We are still examining ways to make this more user friendly, for example by using the [https://hl7.org/fhir/STU3/extension-11179-permitted-value-conceptmap.html extension for ConceptMaps], but that does not work unless various third party tooling is updated.

==Use of the reference datatype==
A key feature of FHIR is the ability of resources to reference each other. This is done using the [https://hl7.org/fhir/STU3/references.html#Reference {{datatype|Reference}} datatype]. This datatype supports two modes of referencing:
; [https://hl7.org/fhir/STU3/references.html#literal Literal references], using the {{fhir|.reference}} element: A relative or absolute REST endpoint containing {{fhir|.id}} of the referenced resource. In a Bundle context, this may also be a reference to a {{fhir|Bundle.resource.fullUrl}}.
; [https://hl7.org/fhir/references.html#logical Logical references], using the {{fhir|.identifier}} element: Meaning a match on the business identifier ({{fhir|.identifier}}) for the referenced resource, without specifying where to find the referenced resource. Note: confusingly, although this reference type is called "logical reference", it does ''not'' act on the "logical identifier" ({{fhir|.id}}) of resources.

The resource/profile will usually constrain which resources may be targeted from a given element. For example, {{fhir|Patient.generalPractitioner}} may point only to an Organization or Practitioner resource, and the nl-core-patient profile further restricts this to the nl-core-organization and nl-core-practitioner profiles{{ref|weakness-target-unavailable}}.

The basic requirements for using references in this context are:
* Either a literal or logical reference SHALL be specified, unless specified otherwise.
** Literal references are preferred over logical references when multiple target resource types/profiles may be used{{ref|weakness-unknown-type}}.
* Literal references SHALL be resolvable.
** External references SHALL be regarded in the same context as the resource itself. If the current security context is insufficient for retrieving the reference, then additional negotiation for appropriate privileges may be required.
** Relative references are preferred over absolute references.
* A short description of the target resource SHALL be included using the {{fhir|.display}} element.

''Note 1'': {{note|weakness-target-unavailable}}In some circumstances, the constraints om the target are too strict for the use case and the appropriate resource can't be referenced (examples are {{fhir|Encounter.participant}}, which cannot reference a PractitionerRole resource to provide context of the attending physician, and {{fhir|Media.operator}}, which cannot target Patient resources and thus doesn't recognize patient-generated Media). In such cases, the proper reference type is added using an extension within the element that is used to refer the other resource. Because some receiving systems may not be able to handle this extension, the {{fhir|.display}} on both the element itself and the extension SHOULD be populated with the same value.

''Note 2'': {{note|weakness-unknown-type}}There is a known weakness in the Reference datatype for FHIR STU3 which is fixed in FHIR R4: if the reference might have more than one type of resource as target, a receiving system cannot know what type is meant when only an identifier is provided.

==Relating FHIR profiles with their functional definitions==
All profiles have a traceable relationship with their functional counterpart(s) based on the element mapping mechanism in FHIR. This allows to:
# define one or more references from a FHIR profile to an external URL where the functional definition can be found
# define for each FHIR profile element to which concept ''within'' a functional definition it corresponds

The functional definition(s) underlying the profile can thus be resolved using the [https://hl7.org/fhir/STU3/structuredefinition-definitions.html#StructureDefinition.mapping {{fhir|StructureDefinition.mapping}}] metadata field of a profile. To relate a FHIR profile field to a concept from the functional description, the concept ID defined in the [https://hl7.org/fhir/STU3/dataelement-definitions.html#DataElement.mapping {{fhir|DataElement.mapping}}] can be used to look up the concept in the functional definition. It is possible that a single profile element refers concepts from multiple functional descriptions. Simplifier will show an overview of all the mappings for a FHIR profile on the dedicated 'mappings' tab, together with a clickable URL to the functional definition. In addition, on the 'overview' tab for each field the relevant mapping can be found.

For example, the profile nl-core-address defines a relationship with [https://simplifier.net/NictizSTU3-Zib2017/nl-core-address/~mappings with four functional definitions], one of which is [https://zibs.nl/wiki/AddressInformation-v1.0(2017EN) AddressInformation-v1.0(2017EN)]. This mapping is identified within the profile using 'hcim-addressinformation-v1.0-2017EN'. Looking at the {{fhir|Address.city}} element in this profile, one of the mappings is defined as 'hcim-addressinformation-v1.0-2017EN:NL-CM:20.5.3'. This reveals that this element implements (amongst others) the concept from the HCIM AddressInformation-v1.0(2017EN) described using ID 'NL-CM:20.5.3'.

==Profile use and declaration==
The implementation guides for the various information standards list the profiles to use for the FHIR resources. In the interest of interoperability it is important that, when using said information standard:
* Each resource SHALL be a valid instance of the applicable profile. Note that this applies not only to profiles listed directly in the IG, but also to profiles referred from/used by listed profiles.
* Each resource SHALL include the canonical URL of this profile in the {{fhir|meta.profile}} element. The canonical of compatible base or derived profiles MAY be included as well.

=={{fhir|Resource.text}} or "the narrative"==
The FHIR STU3 specification says instances SHOULD contain a human readable summary of the contained data, which can be used as fallback by the receiver. This human readable text is contained in the [https://hl7.org/fhir/STU3/domainresource-definitions.html#DomainResource.text {{fhir|.text}} element] with datatype [https://hl7.org/fhir/STU3/narrative.html {{datatype|Narrative}}]. This human readable text is often referred to as "the narrative".

This implementation guide has the following expectations regarding the use of narratives:
* Senders SHALL provide a "clinically safe" ([[#"Clinically safe" narratives|see below]]) narrative of status {{term|extensions}} (preferred) or {{term|generated}} ([[#Narrative status|see below]]), unless:
** The resource does not support narratives. This is the case for resources that do not derive from DomainResource, like Binary.
** The resource is contained in another resource.
** It is explicitly documented in the information standard to do otherwise.
* Receiver SHALL support the narrative. Ignoring the narrative is considered passive support. Support for the narrative SHALL be in accordance with the status and explicitly documented use in the relevant information standard.
* Receiver SHALL NOT generically depend on presence of a clinically safe narrative as their only means to present data to users when an explicitly documented use case for status empty or additional exists. Also, using just the narrative you would not expect to produce graphs, support for medication alerts and other functionality.

==="Clinically safe" narratives===
Regarding the contents of the narrative, the [https://hl7.org/fhir/STU3/domainresource-definitions.html#DomainResource.text FHIR STU3 spec states] that:
<blockquote>The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative.</blockquote>
And for the Narrative datatype:
<blockquote>Structured data SHOULD NOT generally contain information of importance to human readers that is omitted from the narrative. Creators of FHIR resources should not assume that systems will render (or that humans will see) data that is not in the narrative.</blockquote>

The decision to what entails "clinically safe" information, is somewhat arbitrary. Guidelines for "clinically safe" inspired by the [https://hl7.org/fhir/STU3/w5.html FHIR W5 report]:
* If you only had the narrative: the intention and context should be clear to you.
* Who. Patient/subject, performer, author and/or other primary actors. Is this about family history or the actual patient.
* What. The topic for the resource is clear.
* When. Is this past, present, or future information.
* Why. What led up to the event. E.g. Condition, Referral that caused Encounter or Procedure.
* Where. Location of the event/action in the resource.
* Context. Relevant context as present as presented in the resource. status, Encounter, EpisodeOfCare, Diagnosis, Condition, BodySite.
* Rendering every identifier and/or code detail may not be necessary. {{fhir|Resource.text}} is for human assessment of the situation so emphasis should be on display text, representing identifier/code/system as relevant in the context.

Informal note: Producing a "clinically safe" narrative can be cumbersome. Various reference frameworks like [https://hapifhir.io/hapi-fhir/docs/model/narrative_generation.html HAPI] include a Narrative Generator of some sort.

===Narrative status===

Datatype {{datatype|Narrative}} [https://hl7.org/fhir/STU3/valueset-narrative-status.html defines different status codes] to indicate the origin of the narrative text. This implementation guide expects the most common use case to be the status {{term|extensions}}, which means that the narrative is generated entirely from the structured data and the extensions used. The reason for this is that most resources can have extension content defined on them. This status can still be used if a particular instance doesn't contain any extensions.

Alternatively, status {{term|generated}} may be used if the sender did not anticipate inclusion of regular extension content in the narrative.

'''Note''': for both status {{term|extensions}} and {{term|generated}}, all modifier extensions SHOULD be included in the narrative as they always affect the semantics.

Senders SHOULD NOT use the other possible statuses unless it is explicitly documented why, e.g. in an information standard. Receivers MAY choose to support narratives with status {{term|additional}}, which means that it holds information not contained in the structured data. Receivers - upon rendering narrative with status {{term|additional}} - SHOULD make it clear to the user that the information is a fragment, and not the entire thing, in some suitable way.

==Search==

===Search URLs and search parameters===
Each use case of the various information standards lists the search parameters to use for a client to query the relevant information on a server. Usually, this is done in the form of (a number of) search URL(s), although individual use cases may use some other form if necessary (for example, listing optional parameters). Regarding the search parameters, the following guidelines apply:

* Unless explicitly marked as optional, the listed search parameters are considered the minimum for a request, meaning that:
** All stated parameters and modifiers SHALL be supported both by clients and servers.
** All stated parameters and modifiers SHALL be used for searching as specified in the information standard.
* A client MAY use additional search parameters in the search (such as date-range) not defined in the information standard. These may serve to further constrain the result set.
* A server MAY ignore and MAY support additional search parameters. A server SHALL report the applied parameters [https://www.hl7.org/fhir/stu3/search.html#conformance in the self link] of the response and SHOULD provide additional information about the search process using an OperationOutcome in the search result Bundle (as an entry with {{fhir|search.mode}} set to {{term|outcome}}). A client MAY use the self link and/or OperationOutcome to inform the user, independently apply these filters to the result set, or take some other action.
* A server SHALL reject any search request that contains parameters suffixed by a modifier that the server does '''not''' support for that parameter. For example, if the server supports the name search parameter, but not the :exact modifier on the name, it should reject a search with the parameter {{fhir|1=name:exact=Bill}}, using an HTTP 400 error with an OperationOutcome with a clear error message.
* A server SHALL NOT return information that is out of scope for the defined use case or authorization, even if the request by the client is wider than the use case.
* Repeating search parameters constitute a logical AND. Repeating search parameter values constitute a logical OR. Where applicable, this will be described further in the implementation guide.
* The order of the search parameters is always irrelevant.

General guidance on the use of search parameters can be found [https://www.hl7.org/fhir/stu3/search.html in the FHIR specification].

====Search on date, number or quantity====
When a search parameter has a type of date, number or quantity, the request [https://www.hl7.org/fhir/stu3/search.html#prefix uses prefixes] to control the search behavior. Unless explicitly stated otherwise, the minimum set of supported prefixes for these types is {{fhir|eq}}, {{fhir|gt}}, {{fhir|lt}}, {{fhir|ge}} and {{fhir|le}}. For example:
GET [base]/Observation?date=ge2019-01-01&date=le2020-01-01
Searches on all Observation resources that have an {{fhir|.effective[x]}} between January 1, 2019 and January 1, 2020.

====The {{fhir|_lastUpdated}} search parameter====
Retrieving information that was added, changed, deleted relative to a date may be done using the search parameter {{fhir|_lastUpdated}}, which is available for any resource. Using the parameter {{fhir|_lastUpdated}}, a system may query for data that is ''new'' since a specified date. Any FHIR server is expected to support this parameter. More information can be found in [https://hl7.org/fhir/STU3/search.html#lastUpdated the section on {{fhir|_lastUpdated}}] in the FHIR specification.

An example search request is shown below.

<pre>GET [base]/Consent?category=http://snomed.info/sct|11291000146105&_lastUpdated=gt2018-10-01</pre>

This search finds all Consent resources with a category SNOMED code 11291000146105 that have been modified since Oct 1, 2018.

===Search results===
====Including referenced resources====
Servers may not support read interactions, but all references from search results need to be resolvable (see [[#Use of the reference datatype]]). Therefore servers MAY choose to include the referenced resources in the ''searchset'' Bundle, even if the client didn't use any <code>_include</code> parameters. These resources SHALL have <code>Bundle.entry.mode</code> set to "''include''". Servers SHOULD NOT use contained resources for this purpose.

====Paging====
Servers MAY use [https://www.hl7.org/fhir/stu3/search.html#count paging] for performance reasons. Client SHALL support this mechanism to prevent loss of information.

== Usage of the {{fhir|.id}} and {{fhir|.fullUrl}} elements in FHIR instances ==

=== {{fhir|.id}} versus {{fhir|.identifier}} ===
FHIR recognizes two fields that are used as identifier for instances: {{fhir|.id}} and {{fhir|.identifier}}. Although these are both identifiers, they are unrelated and serve a completely different purpose:
* {{fhir|.id}} is the logical identifier, or technical identifier, akin to the id-field in a database. It is used as a unique handle for every instance on a particular server, and is needed to construct the URL to the instance. As such, it is used for referring between resources. The {{fhir|.id}} has no further meaning outside of the server.
* {{fhir|.identifier}} is a business identifier, which usually has a meaning ''outside'' of the server. Examples are a registration number of a healthcare provider, a BSN or social security number for citizens, ISBNs for books, etc. Any instance may have multiple kinds of identifiers.

This section is about the {{fhir|.id}} field and more general about the concept of a logical/technical id to identify instances on a server. The usage of the {{fhir|.identifier}} field, i.e. the business identifier, cannot be described in general terms and will be dictated one a use-case basis by the particular profiles.

=== When is {{fhir|.id}} expected? ===

As stated above, the logical id is meant to uniquely identify instances on a particular server; it is a vital component when using FHIR within a RESTful context. So as a rule of thumb, the {{fhir|.id}} element should always be present when dealing with instances that have a logical id, thus with instances on a server. This means:
* When a client reads, updates or otherwise addresses an existing resource on a server, the {{fhir|.id}} element SHALL be populated in the request and response, and it SHALL match the id in the request URL.
* When a client sends a ''new'' instance to a server using a create operation, the <code>id</code> element is ''not'' expected to be present -- these new instances don't exist yet on the server, so a logical id has no meaning. However, the server SHALL assign a logical id and populate the {{fhir|.id}} element in the response. ''Note'': It is not strictly prohibited to populate the {{fhir|.id}} field when sending a new instance, but the server SHOULD ignore it.
* When a client performs a search on a server, all instances in the returned searchset Bundle SHOULD have the {{fhir|.id}} field populated. ''Note'': A server SHOULD try its best to create stable ids for the resources it serves. Omitting {{fhir|.id}} elements is strongly discouraged as it breaks the assumptions about RESTful behavior. However, a server that omits {{fhir|.id}}s is still considered conformant when the conditions below are met:
*# The server does not natively support logical ids, for example when it is a stateless middleware server that gets its input from a non-FHIR XIS backend.
*# ''And'' the use case doesn't require read / update / delete / patch support for any of the returned of referenced resources, as stated by the CapabilityStatement for the information standard.
*# ''And'' the server includes all referenced resources in the searchset Bundle (regardless of whether the client asked to do so). These resources refer to each other based on the fullUrl mechanism as described below.

=== Logical ids, {{fhir|.fullUrl}}s and references in Bundles ===

There are several FHIR operations, like searching or batch create operations, where multiple instances are placed together in a Bundle. These instances will usually contain references to each other. These internal references cannot be resolved simply by inspecting the {{fhir|.id}} element of every instance; it is not guaranteed that all instances have a logical id. Instead, Bundles allow an {{fhir|entry.fullUrl}} element for each instance which may be used for references. This is an additional mechanism to the logical id, not a replacement:
* The [[#When_is_id_expected.3F|guidelines above]] for populating the {{fhir|.id}} field still apply.
* If {{fhir|.id}} is present, {{fhir|.fullUrl}} SHALL correspond with it (see below).

{{fhir|.fullUrl}}s may be RESTful URLs, UUIDs or even OIDs, based on the situation (which may be mixed within the same Bundle):
; Instances with a logical id: If an instance can be accessed on the server using RESTful operations, the {{fhir|.id}} of that instance in the Bundle will be populated. The corresponding {{fhir|.fullUrl}} in this case SHALL be the absolute URL to the instance on the server.Instances within the Bundle may use relative references to each other, like they are on the same server. The FHIR machinery specifies how to find the matching instance based on the {{fhir|.fullUrl}}.
; Instances without a logical id: When instances are to be created on a server or when the server doesn't support reading individual instances, they don't have a logical id. When these id-less instances need to be referenced from within a Bundle, there are two alternatives:
:* UUIDs can be used as single-use ids that will change each time the Bundle is generated. The {{fhir|.fullUrl}} for the instance will be the UUID prefixed with <code><nowiki>urn:uuid:</nowiki></code>. <ref name="id-ambiguous">Some implementations may choose to populate the {{fhir|.id}} element with the unprefixed UUID or OID in cases when the {{fhir|.id}} field is expected, for example in searchset Bundles. The FHIR specification is ambiguous on the requirements to do so. For a long discussion on the topic, see [https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Confused.20about.20URN.20fullUrl's.20and.20resource.2Eid's chat.fhir.org].</ref>
:* OIDs can be used if the instance has an OID-based ''business'' identifier (i.e. the {{fhir|.identifier}} field), like the UZI number of a healthcare provider. The {{fhir|.fullUrl}} will be the OID prefixed with <code><nowiki>urn:oid:</nowiki></code><ref name="id-ambiguous"/><ref>The use of OIDs as id has some limitations:
* The {{fhir|.id}} has a maximum length of 64 characters, so only OIDs that contain less than 64 characters can be used.
* OID based ids are expected to be stable, just like RESTful ids. Different Bundle instances SHALL always use the same OID based ids.
* Some ''objects'' may have multiple OID based identifiers, like AGB and UZI for practitioners. Which one do you choose? And what happens when the UZI number becomes available after you've already used the AGB as {{fhir|.id}}?
* Specifically for HL7 V3 based backends: an HL7 V3 II datatype normally consists of a <code>@root</code> (OID) and an <code>@extension</code> (string). Concatenation of <code>@root</code> and <code>@extension</code> only yields a new OID if <code>@extension</code> is numeric. Other combinations of <code>@root.@extension</code>, may yield a valid {{fhir|.id}} (pattern <code>[A-Za-z0-9\-\.]{1,64}</code>), but may not be a valid OID. In this case it is no longer possible to create a {{fhir|.fullUrl}} consistent with the {{fhir|.id}} based the <nowiki>urn:oid:</nowiki> scheme.</ref>.
: Instances within the Bundle should use the prefixed version of the UUID/OID for referencing.

==== Example ====
Consider a client that wants to send a new Observation instance to a server and simultaneously link it to an existing Task instance. This can be done using a transaction Bundle:
<syntaxhighlight lang="xml" highlight="7-8,11,23-24,27-28,33-34,41-42" style="max-height:400px; overflow: auto;">
<Bundle xmlns="http://hl7.org/fhir">

<type value="transaction"/>


<entry>

<fullUrl value="urn:uuid:0e855422-b8ef-4247-9443-f3747e78747e"/>
<resource>
<Observation>

...
</Observation>
</resource>
</entry>
<request>
<method value="POST"/>
<url value="Observation"/>
</request>


<entry>

<fullUrl value="http://example-xis.com/Task/1234"/>
<resource>
<Task>

<id value="1234"/>
...
<output>
...
<valueReference>

<reference value="urn:uuid:0e855422-b8ef-4247-9443-f3747e78747e"/>
</valueReference>
</output>
</Task>
</resource>
<request>
<method value="PUT"/>

<url value="Task/1234"/>
</request>
</entry>
</Bundle>
</syntaxhighlight>

The server response should then look like:
<syntaxhighlight lang="xml" highlight="5-6,9-10,28-29" style="max-height:400px; overflow: auto;">
<Bundle xmlns="http://hl7.org/fhir">
<type value="transaction-response"/>

<entry>

<fullUrl value="http://example-xis.com/QuestionnaireResponse/5678"/>
<resource>
<Observation>

<id value="5678"/>
...
</Observation>
</resource>
</entry>
<response>
....
</request>

<entry>
<fullUrl value="http://example-xis.com/Task/1234"/>
<resource>
<Task>
<id value="1234"/>
...
<output>
...
<valueReference>

<reference value="Observation/5678"/>
</valueReference>
</output>
</Task>
</resource>
<response>
....
</response>
</entry>
</Bundle>
</syntaxhighlight>

== Handling errors==
Errors in FHIR interactions are usually communicated using the combination of an appropriate HTTP status code in the 4xx-5xx range, and an [https://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] resource providing more details regarding the error. The OperationOutcome resource contains mandatory elements to indicate the overall type and severity of the error (respectively {{fhir|.code}} and {{fhir|.severity}}) and MAY express the location (using {{fhir|.location}} or {{fhir|.expression}}) and a free-form or coded description of the error (using the {{fhir|.diagnostics}} or {{fhir|.detail}} element). Although these latter elements are not required, their usage is strongly encouraged.

For the most common errors, the expected handling is listed in table [xxx] below. This should be interpreted as a guideline, as the nature of an error is not always unambiguous and various FHIR reference implementations will make different choices. The FHIR specification provides more detail [https://www.hl7.org/fhir/stu3/http.html on error handling in general], [https://www.hl7.org/fhir/stu3/security.html#AccessDenied access denied responses] and [https://www.hl7.org/fhir/stu3/search.html#errors for search operations specifically].

In general, most FHIR-related errors (in addition to normal HTTP errors related to security, header and content type negotiation issues) will result in one of these HTTP status codes:
* 400 Bad Request - resource could not be parsed, search could not be processed or basic FHIR validation rules failed
* 403 Forbidden - the server was unable to execute the search, due to an authorization failure
* 404 Not Found - resource type not supported, or not an FHIR endpoint
* 422 Unprocessable Entity - the proposed resource violated applicable FHIR profiles or server business rules

{| class="wikitable"
|-
! Interaction
! Error
! Expected action
! Example
|-
| rowspan=2 |All
| Invalid authorization
|
* HTTP 403 Forbidden
* OperationOutcome with <code>code</code> set to "''security''"
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Invalid_authorization Example]
|-
| Resource is not supported
|
* HTTP 404 Not Found
* OperationOutcome with {{fhir|.code}} set to {{term|not-supported}}
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Resource_is_not_supported Example]
|-
| rowspan=4 |search
| No match for the given search parameters
| colspan="2" |''This is not considered an error, but a normal search without results.''
|-
| Unknown search parameter
| colspan="2" | ''This is not considered an error. See the [[#unknown_search_parameter_handling|guidance in the section on searching]].''
|-
| Syntactically incorrect parameter
|
* HTTP 400 Bad Request
* OperationOutcome. There are various issue type codes that could be used, depending on the nature of the error
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Syntactically_incorrect_parameter Example]
|-
| Known but unsupported value. This situation applies to non-supported HCIM profiles when the Resource endpoint itself is supported.
|
* HTTP 200 OK
* Empty Bundle of {{fhir|.type}} {{term|searchset}}
* OperationOutcome in Bundle as an entry marked with {{fhir|Bundle.entry.search.mode}} of {{term|outcome}}.
* OperationOutcome with {{fhir|.code}} set to {{term|not-found}} and {{fhir|.severity}} not set to {{term|fatal}} or {{term|error}}.
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Unkown_or_unsupported_search_parameter_value Example]
|-
| read
| Read request with unknown id
|
* HTTP 404 Not Found
* OperationOutcome with {{fhir|.code}} set to {{term|not-found}}
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Request_on_an_unknown_id Example]
|-
| update
| No or incorrect Resource id
|
* HTTP 400 Bad Request
* OperationOutcome with {{fhir|.code}} set to {{term|invalid}}
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#No_or_incorrect_Resource_id Example]
|-
| create/update
| Resource syntax or data is incorrect or invalid
|
* HTTP 400 Bad Request or HTTP 422 Unprocessable Entity
* OperationOutcome with {{fhir|.code}} set to {{term|invalid}} or preferably a more specific child code.
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Resource_syntax_or_data_is_incorrect_or_invalid Example]
|}
<section end=OverarchingPrinciples />
<section begin=FHIRPackages />

=FHIR Packages=
The information standards maintained by Nictiz adopt the FHIR Packaging mechanism to support consistent versioning of profiles and related conformance resources such as OperationDefinitions. FHIR Packaging is based on the NPM Packaging mechanism and offers developers a convenient way to include the conformance resources in their favorite IDE. The relevant package version is indicated and linked in the information standards technical design page.

Please note that every effort has been made to ensure that the examples contained in the packages are correct and useful, but they are not a normative part of any information standard.

For even more background information:
* [https://confluence.hl7.org/display/FHIR/NPM+Package+Specification The HL7 base specification for FHIR pacakges]
* [https://blog.fire.ly/2017/11/28/versioning-and-canonical-urls/ What is the problem that packaging could address]
* [https://simplifier.net/organization/firely/news/55 Introducing the Simplifier FHIR Package Server] (includes what problem packaging addresses)
* [https://simplifier.net/organization/firely/news/56 Firely Torinox introduction] (this is one of the tools that's useful for working with FHIR packages)

{{NoteBox|It is '''not''' required to implement FHIR based information standards using the packaging mechanism. It is still possible to download all or selected resources from Simplifier on as-needed basis. You are however encouraged to invest in dealing with packages.}}
<section end=FHIRPackages />

FHIR:Vprepub-1.0 FHIR IG STU3

2021-01-22T09:41:05Z

__NOINDEX__
__NUMBEREDHEADINGS__
{{DISPLAYTITLE:FHIR Implementation Guide}}

__TOC__

=Introduction=
This implementation guide describes the considerations for using '''HL7® FHIR®''' in context of information standards that are maintained by Nictiz. It applies specifically to HL7® FHIR® version 3 (STU3).

This implementation guide is aimed at software vendors and developers that need to implement FHIR based information standards maintained by Nictiz. Users of this guide are expected to be familiar with the [https://hl7.org/fhir/STU3 FHIR STU3 specification] and resource processing. Where relevant, links to the FHIR specification are provided. This implementation guide is not intended to be a tutorial on that subject.

<section begin=OverarchingPrinciples />
=Use case overarching principles=
==Content Types and encodings==
Unless stated otherwise, the information standards use the [https://hl7.org/fhir/http.html#mime-type FHIR RESTful framework]. This framework defines at least three content-types to send/retrieve information:
* XML: application/fhir+xml
* JSON: application/fhir+json
* RDF: text/turtle - Not supported in this context

Servers SHALL support both XML and JSON, while clients MAY use either format for the request and the response. For the response, servers SHALL support server-driven content negotiation as described in [https://www.hl7.org/fhir/stu3/http.html#mime-type the FHIR specification]. This means that clients can indicate the desired response format using the optional <code>_format=[mimetype]</code> URL parameter, or the acceptable response format(s) using the <code>Accept</code> header. The URL parameter takes precedence over the header. If a client does not request a specific content-type, then it is server discretion to respond using XML or JSON.

FHIR uses UTF-8 for all request and response bodies. Since the [https://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.7.1 HTTP specification (section 3.7.1)] defines a default character encoding of ISO-8859-1, requests and responses SHALL explicitly set the character encoding to UTF-8 using the <code>charset</code> parameter of the MIME-type in the <code>Content-Type</code> header. Requests MAY also specify this <code>charset</code> parameter in the <code>Accept</code> header and/or use the <code>Accept-Charset</code> header.

==Use of coded concepts==
Coded information is extremely important for interoperability between systems. It enables systems to act on information rather than have humans read everything for interpretation - it enables medication related alerts, exercise encouragements because of weight increase, and many more things. In the HCIMs and profiles, we therefore strive for complete coverage of all possible situations.

However it is likely that unknown codes present themselves in the communication, for example because the sending system has updated its medication codes to a newer version than the receiving system, or because an older record item is coded in a way that now has been deprecated. It is therefore vital that, in addition to the code itself, the sender includes the semantics of the code. Therefore, systems SHOULD include [https://hl7.org/fhir/STU3/datatypes.html#coding {{fhir|(CodeableConcept).coding.display}}] and/or [https://hl7.org/fhir/STU3/datatypes.html#codeableconcept {{fhir|CodeableConcept.text}}] for coded data in FHIR instances. These fields may only be absent in rare circumstances, for example when dealing with historic data, or in data acquired without such info from a third party.

===Mapping of coded concepts===
Terminology from HCIMs or UCSDs (use case specific datasets) needs to be faithfully applied to the FHIR profiles, but this is not directly possible when the base FHIR resource defines required terminology that bears no direct relationship with the HCIM or UCSD. These cases include, but are not limited to, the FHIR resource elements of datatype {{datatype|code}} ({{fhir|Patient.gender}}, {{fhir|status}} elements, structural type elements, etc.). This datatype always describes FHIR specific terminology, which usually doesn't align with the HCIM/UCSD terminology.

In these cases, a mapping will be provided to explain the relationship between de HCIM/UCSD terminology and the FHIR terminology. This is normally done through a FHIR [https://hl7.org/fhir/STU3/conceptmap.html ConceptMap], which can translate between the terminology used in the HCIM/UCSD, and the terminology that FHIR instances need to adhere to. Usually, the original terminology from the HCIM/UCSD will be communicated as well by adding the extension [https://simplifier.net/resolve?target=simplifier&canonical=http://nictiz.nl/fhir/StructureDefinition/code-specification code-specification] on the same element. This allows unambiguous interpretation on the receiver end.

Example snippet from an {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance|title=AllergyIntolerance}} where both the FHIR terminology {{term|high}} and the SNOMED CT {{term|24484000}} terminology are communicated. The FHIR terminology is obtained from the HCIM terminology using ConceptMap {{Simplifier|http://nictiz.nl/fhir/ConceptMap/MateVanKritiekZijnCodelijst-to-allergy-intolerance-criticality|title=MateVanKritiekZijnCodelijst-to-allergy-intolerance-criticality}}:

<syntaxhighlight lang="xml">
<criticality value="high">
<extension url="http://nictiz.nl/fhir/StructureDefinition/code-specification">
<valueCodeableConcept>
<coding>
<system value="http://snomed.info/sct"/>
<code value="24484000"/>
<display value="Severe"/>
</coding>
</valueCodeableConcept>
</extension>
</criticality>
</syntaxhighlight>

'''Please note''': Unfortunately, FHIR doesn't have a core structured way for indicating which ConceptMaps to use. Instead, mappings are documented in the description of the element in the profile and/or specifically on the mapping description contained in the element.

To retrieve the indicated ConceptMap on Simplifier, the canonical url from the description needs to be used as search term. We are still examining ways to make this more user friendly, for example by using the [https://hl7.org/fhir/STU3/extension-11179-permitted-value-conceptmap.html extension for ConceptMaps], but that does not work unless various third party tooling is updated.

==Use of the reference datatype==
A key feature of FHIR is the ability of resources to reference each other. This is done using the [https://hl7.org/fhir/STU3/references.html#Reference {{datatype|Reference}} datatype]. This datatype supports two modes of referencing:
; [https://hl7.org/fhir/STU3/references.html#literal Literal references], using the {{fhir|.reference}} element: A relative or absolute REST endpoint containing {{fhir|.id}} of the referenced resource. In a Bundle context, this may also be a reference to a {{fhir|Bundle.resource.fullUrl}}.
; [https://hl7.org/fhir/references.html#logical Logical references], using the {{fhir|.identifier}} element: Meaning a match on the business identifier ({{fhir|.identifier}}) for the referenced resource, without specifying where to find the referenced resource. Note: confusingly, although this reference type is called "logical reference", it does ''not'' act on the "logical identifier" ({{fhir|.id}}) of resources.

The resource/profile will usually constrain which resources may be targeted from a given element. For example, {{fhir|Patient.generalPractitioner}} may point only to an Organization or Practitioner resource, and the nl-core-patient profile further restricts this to the nl-core-organization and nl-core-practitioner profiles{{ref|weakness-target-unavailable}}.

The basic requirements for using references in this context are:
* Either a literal or logical reference SHALL be specified, unless specified otherwise.
** Literal references are preferred over logical references when multiple target resource types/profiles may be used{{ref|weakness-unknown-type}}.
* Literal references SHALL be resolvable.
** External references SHALL be regarded in the same context as the resource itself. If the current security context is insufficient for retrieving the reference, then additional negotiation for appropriate privileges may be required.
** Relative references are preferred over absolute references.
* A short description of the target resource SHALL be included using the {{fhir|.display}} element.

''Note 1'': {{note|weakness-target-unavailable}}In some circumstances, the constraints om the target are too strict for the use case and the appropriate resource can't be referenced (examples are {{fhir|Encounter.participant}}, which cannot reference a PractitionerRole resource to provide context of the attending physician, and {{fhir|Media.operator}}, which cannot target Patient resources and thus doesn't recognize patient-generated Media). In such cases, the proper reference type is added using an extension within the element that is used to refer the other resource. Because some receiving systems may not be able to handle this extension, the {{fhir|.display}} on both the element itself and the extension SHOULD be populated with the same value.

''Note 2'': {{note|weakness-unknown-type}}There is a known weakness in the Reference datatype for FHIR STU3 which is fixed in FHIR R4: if the reference might have more than one type of resource as target, a receiving system cannot know what type is meant when only an identifier is provided.

==Relating FHIR profiles with their functional definitions==
All profiles have a traceable relationship with their functional counterpart(s) based on the element mapping mechanism in FHIR. This allows to:
# define one or more references from a FHIR profile to an external URL where the functional definition can be found
# define for each FHIR profile element to which concept ''within'' a functional definition it corresponds

The functional definition(s) underlying the profile can thus be resolved using the [https://hl7.org/fhir/STU3/structuredefinition-definitions.html#StructureDefinition.mapping {{fhir|StructureDefinition.mapping}}] metadata field of a profile. To relate a FHIR profile field to a concept from the functional description, the concept ID defined in the [https://hl7.org/fhir/STU3/dataelement-definitions.html#DataElement.mapping {{fhir|DataElement.mapping}}] can be used to look up the concept in the functional definition. It is possible that a single profile element refers concepts from multiple functional descriptions. Simplifier will show an overview of all the mappings for a FHIR profile on the dedicated 'mappings' tab, together with a clickable URL to the functional definition. In addition, on the 'overview' tab for each field the relevant mapping can be found.

For example, the profile nl-core-address defines a relationship with [https://simplifier.net/NictizSTU3-Zib2017/nl-core-address/~mappings with four functional definitions], one of which is [https://zibs.nl/wiki/AddressInformation-v1.0(2017EN) AddressInformation-v1.0(2017EN)]. This mapping is identified within the profile using 'hcim-addressinformation-v1.0-2017EN'. Looking at the {{fhir|Address.city}} element in this profile, one of the mappings is defined as 'hcim-addressinformation-v1.0-2017EN:NL-CM:20.5.3'. This reveals that this element implements (amongst others) the concept from the HCIM AddressInformation-v1.0(2017EN) described using ID 'NL-CM:20.5.3'.

==Profile use and declaration==
The implementation guides for the various information standards list the profiles to use for the FHIR resources. In the interest of interoperability it is important that, when using said information standard:
* Each resource SHALL be a valid instance of the applicable profile. Note that this applies not only to profiles listed directly in the IG, but also to profiles referred from/used by listed profiles.
* Each resource SHALL include the canonical URL of this profile in the {{fhir|meta.profile}} element. The canonical of compatible base or derived profiles MAY be included as well.

=={{fhir|Resource.text}} or "the narrative"==
The FHIR STU3 specification says instances SHOULD contain a human readable summary of the contained data, which can be used as fallback by the receiver. This human readable text is contained in the [https://hl7.org/fhir/STU3/domainresource-definitions.html#DomainResource.text {{fhir|.text}} element] with datatype [https://hl7.org/fhir/STU3/narrative.html {{datatype|Narrative}}]. This human readable text is often referred to as "the narrative".

This implementation guide has the following expectations regarding the use of narratives:
* Senders SHALL provide a "clinically safe" ([[#"Clinically safe" narratives|see below]]) narrative of status {{term|extensions}} (preferred) or {{term|generated}} ([[#Narrative status|see below]]), unless:
** The resource does not support narratives. This is the case for resources that do not derive from DomainResource, like Binary.
** The resource is contained in another resource.
** It is explicitly documented in the information standard to do otherwise.
* Receiver SHALL support the narrative. Ignoring the narrative is considered passive support. Support for the narrative SHALL be in accordance with the status and explicitly documented use in the relevant information standard.
* Receiver SHALL NOT generically depend on presence of a clinically safe narrative as their only means to present data to users when an explicitly documented use case for status empty or additional exists. Also, using just the narrative you would not expect to produce graphs, support for medication alerts and other functionality.

==="Clinically safe" narratives===
Regarding the contents of the narrative, the [https://hl7.org/fhir/STU3/domainresource-definitions.html#DomainResource.text FHIR STU3 spec states] that:
<blockquote>The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative.</blockquote>
And for the Narrative datatype:
<blockquote>Structured data SHOULD NOT generally contain information of importance to human readers that is omitted from the narrative. Creators of FHIR resources should not assume that systems will render (or that humans will see) data that is not in the narrative.</blockquote>

The decision to what entails "clinically safe" information, is somewhat arbitrary. Guidelines for "clinically safe" inspired by the [https://hl7.org/fhir/STU3/w5.html FHIR W5 report]:
* If you only had the narrative: the intention and context should be clear to you.
* Who. Patient/subject, performer, author and/or other primary actors. Is this about family history or the actual patient.
* What. The topic for the resource is clear.
* When. Is this past, present, or future information.
* Why. What led up to the event. E.g. Condition, Referral that caused Encounter or Procedure.
* Where. Location of the event/action in the resource.
* Context. Relevant context as present as presented in the resource. status, Encounter, EpisodeOfCare, Diagnosis, Condition, BodySite.
* Rendering every identifier and/or code detail may not be necessary. {{fhir|Resource.text}} is for human assessment of the situation so emphasis should be on display text, representing identifier/code/system as relevant in the context.

Informal note: Producing a "clinically safe" narrative can be cumbersome. Various reference frameworks like [https://hapifhir.io/hapi-fhir/docs/model/narrative_generation.html HAPI] include a Narrative Generator of some sort.

===Narrative status===

Datatype {{datatype|Narrative}} [https://hl7.org/fhir/STU3/valueset-narrative-status.html defines different status codes] to indicate the origin of the narrative text. This implementation guide expects the most common use case to be the status {{term|extensions}}, which means that the narrative is generated entirely from the structured data and the extensions used. The reason for this is that most resources can have extension content defined on them. This status can still be used if a particular instance doesn't contain any extensions.

Alternatively, status {{term|generated}} may be used if the sender did not anticipate inclusion of regular extension content in the narrative.

'''Note''': for both status {{term|extensions}} and {{term|generated}}, all modifier extensions SHOULD be included in the narrative as they always affect the semantics.

Senders SHOULD NOT use the other possible statuses unless it is explicitly documented why, e.g. in an information standard. Receivers MAY choose to support narratives with status {{term|additional}}, which means that it holds information not contained in the structured data. Receivers - upon rendering narrative with status {{term|additional}} - SHOULD make it clear to the user that the information is a fragment, and not the entire thing, in some suitable way.

==Search==

===Search URLs and search parameters===
Each use case of the various information standards lists the search parameters to use for a client to query the relevant information on a server. Usually, this is done in the form of (a number of) search URL(s), although individual use cases may use some other form if necessary (for example, listing optional parameters). Regarding the search parameters, the following guidelines apply:

* Unless explicitly marked as optional, the listed search parameters are considered the minimum for a request, meaning that:
** All stated parameters and modifiers SHALL be supported both by clients and servers.
** All stated parameters and modifiers SHALL be used for searching as specified in the information standard.
* A client MAY use additional search parameters in the search (such as date-range) not defined in the information standard. These may serve to further constrain the result set.
* A server MAY ignore and MAY support additional search parameters. A server SHALL report the applied parameters [https://www.hl7.org/fhir/stu3/search.html#conformance in the self link] of the response and SHOULD provide additional information about the search process using an OperationOutcome in the search result Bundle (as an entry with {{fhir|search.mode}} set to {{term|outcome}}). A client MAY use the self link and/or OperationOutcome to inform the user, independently apply these filters to the result set, or take some other action.
* A server SHALL reject any search request that contains parameters suffixed by a modifier that the server does '''not''' support for that parameter. For example, if the server supports the name search parameter, but not the :exact modifier on the name, it should reject a search with the parameter {{fhir|1=name:exact=Bill}}, using an HTTP 400 error with an OperationOutcome with a clear error message.
* A server SHALL NOT return information that is out of scope for the defined use case or authorization, even if the request by the client is wider than the use case.
* Repeating search parameters constitute a logical AND. Repeating search parameter values constitute a logical OR. Where applicable, this will be described further in the implementation guide.
* The order of the search parameters is always irrelevant.

General guidance on the use of search parameters can be found [https://www.hl7.org/fhir/stu3/search.html in the FHIR specification].

====Search on date, number or quantity====
When a search parameter has a type of date, number or quantity, the request [https://www.hl7.org/fhir/stu3/search.html#prefix uses prefixes] to control the search behavior. Unless explicitly stated otherwise, the minimum set of supported prefixes for these types is {{fhir|eq}}, {{fhir|gt}}, {{fhir|lt}}, {{fhir|ge}} and {{fhir|le}}. For example:
GET [base]/Observation?date=ge2019-01-01&date=le2020-01-01
Searches on all Observation resources that have an {{fhir|.effective[x]}} between January 1, 2019 and January 1, 2020.

====The {{fhir|_lastUpdated}} search parameter====
Retrieving information that was added, changed, deleted relative to a date may be done using the search parameter {{fhir|_lastUpdated}}, which is available for any resource. Using the parameter {{fhir|_lastUpdated}}, a system may query for data that is ''new'' since a specified date. Any FHIR server is expected to support this parameter. More information can be found in [https://hl7.org/fhir/STU3/search.html#lastUpdated the section on {{fhir|_lastUpdated}}] in the FHIR specification.

An example search request is shown below.

<pre>GET [base]/Consent?category=http://snomed.info/sct|11291000146105&_lastUpdated=gt2018-10-01</pre>

This search finds all Consent resources with a category SNOMED code 11291000146105 that have been modified since Oct 1, 2018.

===Search results===
====Including referenced resources====
Servers may not support read interactions, but all references from search results need to be resolvable (see [[#Use of the reference datatype]]). Therefore servers MAY choose to include the referenced resources in the ''searchset'' Bundle, even if the client didn't use any <code>_include</code> parameters. These resources SHALL have <code>Bundle.entry.mode</code> set to "''include''". Servers SHOULD NOT use contained resources for this purpose.

====Paging====
Servers MAY use [https://www.hl7.org/fhir/stu3/search.html#count paging] for performance reasons. Client SHALL support this mechanism to prevent loss of information.

== Usage of the {{fhir|.id}} and {{fhir|.fullUrl}} elements in FHIR instances ==

=== {{fhir|.id}} versus {{fhir|.identifier}} ===
FHIR recognizes two fields that are used as identifier for instances: {{fhir|.id}} and {{fhir|.identifier}}. Although these are both identifiers, they are unrelated and serve a completely different purpose:
* {{fhir|.id}} is the logical identifier, or technical identifier, akin to the id-field in a database. It is used as a unique handle for every instance on a particular server, and is needed to construct the URL to the instance. As such, it is used for referring between resources. The {{fhir|.id}} has no further meaning outside of the server.
* {{fhir|.identifier}} is a business identifier, which usually has a meaning ''outside'' of the server. Examples are a registration number of a healthcare provider, a BSN or social security number for citizens, ISBNs for books, etc. Any instance may have multiple kinds of identifiers.

This section is about the {{fhir|.id}} field and more general about the concept of a logical/technical id to identify instances on a server. The usage of the {{fhir|.identifier}} field, i.e. the business identifier, cannot be described in general terms and will be dictated one a use-case basis by the particular profiles.

=== When is {{fhir|.id}} expected? ===

As stated above, the logical id is meant to uniquely identify instances on a particular server; it is a vital component when using FHIR within a RESTful context. So as a rule of thumb, the {{fhir|.id}} element should always be present when dealing with instances that have a logical id, thus with instances on a server. This means:
* When a client reads, updates or otherwise addresses an existing resource on a server, the {{fhir|.id}} element SHALL be populated in the request and response, and it SHALL match the id in the request URL.
* When a client sends a ''new'' instance to a server using a create operation, the <code>id</code> element is ''not'' expected to be present -- these new instances don't exist yet on the server, so a logical id has no meaning. However, the server SHALL assign a logical id and populate the {{fhir|.id}} element in the response. ''Note'': It is not strictly prohibited to populate the {{fhir|.id}} field when sending a new instance, but the server SHOULD ignore it.
* When a client performs a search on a server, all instances in the returned searchset Bundle SHOULD have the {{fhir|.id}} field populated. ''Note'': A server SHOULD try its best to create stable ids for the resources it serves. Omitting {{fhir|.id}} elements is strongly discouraged as it breaks the assumptions about RESTful behavior. However, a server that omits {{fhir|.id}}s is still considered conformant when the conditions below are met:
*# The server does not natively support logical ids, for example when it is a stateless middleware server that gets its input from a non-FHIR XIS backend.
*# ''And'' the use case doesn't require read / update / delete / patch support for any of the returned of referenced resources, as stated by the CapabilityStatement for the information standard.
*# ''And'' the server includes all referenced resources in the searchset Bundle (regardless of whether the client asked to do so). These resources refer to each other based on the fullUrl mechanism as described below.

=== Logical ids, {{fhir|.fullUrl}}s and references in Bundles ===

There are several FHIR operations, like searching or batch create operations, where multiple instances are placed together in a Bundle. These instances will usually contain references to each other. These internal references cannot be resolved simply by inspecting the {{fhir|.id}} element of every instance; it is not guaranteed that all instances have a logical id. Instead, Bundles allow an {{fhir|entry.fullUrl}} element for each instance which may be used for references. This is an additional mechanism to the logical id, not a replacement:
* The [[#When_is_id_expected.3F|guidelines above]] for populating the {{fhir|.id}} field still apply.
* If {{fhir|.id}} is present, {{fhir|.fullUrl}} SHALL correspond with it (see below).

{{fhir|.fullUrl}}s may be RESTful URLs, UUIDs or even OIDs, based on the situation (which may be mixed within the same Bundle):
; Instances with a logical id: If an instance can be accessed on the server using RESTful operations, the {{fhir|.id}} of that instance in the Bundle will be populated. The corresponding {{fhir|.fullUrl}} in this case SHALL be the absolute URL to the instance on the server.Instances within the Bundle may use relative references to each other, like they are on the same server. The FHIR machinery specifies how to find the matching instance based on the {{fhir|.fullUrl}}.
; Instances without a logical id: When instances are to be created on a server or when the server doesn't support reading individual instances, they don't have a logical id. When these id-less instances need to be referenced from within a Bundle, there are two alternatives:
:* UUIDs can be used as single-use ids that will change each time the Bundle is generated. The {{fhir|.fullUrl}} for the instance will be the UUID prefixed with <code><nowiki>urn:uuid:</nowiki></code>. <ref name="id-ambiguous">Some implementations may choose to populate the {{fhir|.id}} element with the unprefixed UUID or OID in cases when the {{fhir|.id}} field is expected, for example in searchset Bundles. The FHIR specification is ambiguous on the requirements to do so. For a long discussion on the topic, see [https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Confused.20about.20URN.20fullUrl's.20and.20resource.2Eid's chat.fhir.org].</ref>
:* OIDs can be used if the instance has an OID-based ''business'' identifier (i.e. the {{fhir|.identifier}} field), like the UZI number of a healthcare provider. The {{fhir|.fullUrl}} will be the OID prefixed with <code><nowiki>urn:oid:</nowiki></code><ref name="id-ambiguous"/><ref>The use of OIDs as id has some limitations:
* The {{fhir|.id}} has a maximum length of 64 characters, so only OIDs that contain less than 64 characters can be used.
* OID based ids are expected to be stable, just like RESTful ids. Different Bundle instances SHALL always use the same OID based ids.
* Some ''objects'' may have multiple OID based identifiers, like AGB and UZI for practitioners. Which one do you choose? And what happens when the UZI number becomes available after you've already used the AGB as {{fhir|.id}}?
* Specifically for HL7 V3 based backends: an HL7 V3 II datatype normally consists of a <code>@root</code> (OID) and an <code>@extension</code> (string). Concatenation of <code>@root</code> and <code>@extension</code> only yields a new OID if <code>@extension</code> is numeric. Other combinations of <code>@root.@extension</code>, may yield a valid {{fhir|.id}} (pattern <code>[A-Za-z0-9\-\.]{1,64}</code>), but may not be a valid OID. In this case it is no longer possible to create a {{fhir|.fullUrl}} consistent with the {{fhir|.id}} based the <nowiki>urn:oid:</nowiki> scheme.</ref>.
: Instances within the Bundle should use the prefixed version of the UUID/OID for referencing.

==== Example ====
Consider a client that wants to send a new Observation instance to a server and simultaneously link it to an existing Task instance. This can be done using a transaction Bundle:
<syntaxhighlight lang="xml" highlight="7-8,11,23-24,27-28,33-34,41-42" style="max-height:400px; overflow: auto;">
<Bundle xmlns="http://hl7.org/fhir">

<type value="transaction"/>


<entry>

<fullUrl value="urn:uuid:0e855422-b8ef-4247-9443-f3747e78747e"/>
<resource>
<Observation>

...
</Observation>
</resource>
</entry>
<request>
<method value="POST"/>
<url value="Observation"/>
</request>


<entry>

<fullUrl value="http://example-xis.com/Task/1234"/>
<resource>
<Task>

<id value="1234"/>
...
<output>
...
<valueReference>

<reference value="urn:uuid:0e855422-b8ef-4247-9443-f3747e78747e"/>
</valueReference>
</output>
</Task>
</resource>
<request>
<method value="PUT"/>

<url value="Task/1234"/>
</request>
</entry>
</Bundle>
</syntaxhighlight>

The server response should then look like:
<syntaxhighlight lang="xml" highlight="5-6,9-10,28-29" style="max-height:400px; overflow: auto;">
<Bundle xmlns="http://hl7.org/fhir">
<type value="transaction-response"/>

<entry>

<fullUrl value="http://example-xis.com/QuestionnaireResponse/5678"/>
<resource>
<Observation>

<id value="5678"/>
...
</Observation>
</resource>
</entry>
<response>
....
</request>

<entry>
<fullUrl value="http://example-xis.com/Task/1234"/>
<resource>
<Task>
<id value="1234"/>
...
<output>
...
<valueReference>

<reference value="Observation/5678"/>
</valueReference>
</output>
</Task>
</resource>
<response>
....
</response>
</entry>
</Bundle>
</syntaxhighlight>

== Handling errors==
Errors in FHIR interactions are usually communicated using the combination of an appropriate HTTP status code in the 4xx-5xx range, and an [https://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] resource providing more details regarding the error. The OperationOutcome resource contains mandatory elements to indicate the overall type and severity of the error (respectively {{fhir|.code}} and {{fhir|.severity}}) and MAY express the location (using {{fhir|.location}} or {{fhir|.expression}}) and a free-form or coded description of the error (using the {{fhir|.diagnostics}} or {{fhir|.detail}} element). Although these latter elements are not required, their usage is strongly encouraged.

For the most common errors, the expected handling is listed in table [xxx] below. This should be interpreted as a guideline, as the nature of an error is not always unambiguous and various FHIR reference implementations will make different choices. The FHIR specification provides more detail [https://www.hl7.org/fhir/stu3/http.html on error handling in general], [https://www.hl7.org/fhir/stu3/security.html#AccessDenied access denied responses] and [https://www.hl7.org/fhir/stu3/search.html#errors for search operations specifically].

In general, most FHIR-related errors (in addition to normal HTTP errors related to security, header and content type negotiation issues) will result in one of these HTTP status codes:
* 400 Bad Request - resource could not be parsed, search could not be processed or basic FHIR validation rules failed
* 403 Forbidden - the server was unable to execute the search, due to an authorization failure
* 404 Not Found - resource type not supported, or not an FHIR endpoint
* 422 Unprocessable Entity - the proposed resource violated applicable FHIR profiles or server business rules

{| class="wikitable"
|-
! Interaction
! Error
! Expected action
! Example
|-
| rowspan=2 |All
| Invalid authorization
|
* HTTP 403 Forbidden
* OperationOutcome with <code>code</code> set to "''security''"
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Invalid_authorization Example]
|-
| Resource is not supported
|
* HTTP 404 Not Found
* OperationOutcome with {{fhir|.code}} set to {{term|not-supported}}
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Resource_is_not_supported Example]
|-
| rowspan=4 |search
| No match for the given search parameters
| colspan="2" |''This is not considered an error, but a normal search without results.''
|-
| Unknown search parameter
| colspan="2" | ''This is not considered an error. See the [[#unknown_search_parameter_handling|guidance in the section on searching]].''
|-
| Syntactically incorrect parameter
|
* HTTP 400 Bad Request
* OperationOutcome. There are various issue type codes that could be used, depending on the nature of the error
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Syntactically_incorrect_parameter Example]
|-
| Known but unsupported value. This situation applies to non-supported HCIM profiles when the Resource endpoint itself is supported.
|
* HTTP 200 OK
* Empty Bundle of {{fhir|.type}} {{term|searchset}}
* OperationOutcome in Bundle as an entry marked with {{fhir|Bundle.entry.search.mode}} of {{term|outcome}}.
* OperationOutcome with {{fhir|.code}} set to {{term|not-found}} and {{fhir|.severity}} not set to {{term|fatal}} or {{term|error}}.
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Unkown_or_unsupported_search_parameter_value Example]
|-
| read
| Read request with unknown id
|
* HTTP 404 Not Found
* OperationOutcome with {{fhir|.code}} set to {{term|not-found}}
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Request_on_an_unknown_id Example]
|-
| update
| No or incorrect Resource id
|
* HTTP 400 Bad Request
* OperationOutcome with {{fhir|.code}} set to {{term|invalid}}
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#No_or_incorrect_Resource_id Example]
|-
| create/update
| Resource syntax or data is incorrect or invalid
|
* HTTP 400 Bad Request or HTTP 422 Unprocessable Entity
* OperationOutcome with {{fhir|.code}} set to {{term|invalid}} or preferably a more specific child code.
| [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2020.01/FHIR_Error_handling_examples#Resource_syntax_or_data_is_incorrect_or_invalid Example]
|}
<section end=OverarchingPrinciples />
<section begin=FHIRPackages />

=FHIR Packages=
The information standards maintained by Nictiz adopt the FHIR Packaging mechanism to support consistent versioning of profiles and related conformance resources such as OperationDefinitions. FHIR Packaging is based on the NPM Packaging mechanism and offers developers a convenient way to include the conformance resources in their favorite IDE. The relevant package version is indicated and linked in the information standards technical design page.

Please note that every effort has been made to ensure that the examples contained in the packages are correct and useful, but they are not a normative part of any information standard.

For even more background information:
* [https://confluence.hl7.org/display/FHIR/NPM+Package+Specification The HL7 base specification for FHIR pacakges]
* [https://blog.fire.ly/2017/11/28/versioning-and-canonical-urls/ What is the problem that packaging could address]
* [https://simplifier.net/organization/firely/news/55 Introducing the Simplifier FHIR Package Server] (includes what problem packaging addresses)
* [https://simplifier.net/organization/firely/news/56 Firely Torinox introduction] (this is one of the tools that's useful for working with FHIR packages)

{{NoteBox|It is '''not''' required to implement FHIR based information standards using the packaging mechanism. It is still possible to download all or selected resources from Simplifier on as-needed basis. You are however encouraged to invest in dealing with packages.}}
<section end=FHIRPackages />

MedMij:Landingspagina MedMij

2020-10-21T07:10:18Z

Stephan Opdenberg: /* Kwalificatie */

__NUMBEREDHEADINGS__
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]

<imagemap>Bestand:Afsprakenstelsel-functioneel-technisch-banner_00_alle.png|center|500px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:Vcurrent_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:Vcurrent_FHIR_IG|Technisch]]
desc none
</imagemap>

==MedMij wiki structuuroverzicht==
<imagemap>Bestand:MedMij_wiki_structuur_overzicht.png||750px|alt=MedMij Wiki-structuuroverzicht
circle 344 894 333 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
rect 1017 1260 1517 1407 [[Landingspagina_MedMij#Mappings|Mappings]]
rect 2123 3 2740 847 [[MedMij:Vcurrent_Ontwerpen|Functioneel (huidige versie)]]
rect 2123 945 2740 1789 [[MedMij:Vcurrent_FHIR_IG|Technisch (huidige versie)]]
desc none
</imagemap>

==Functionele ontwerpen==
*'''2020'''
**[[MedMij:V2020.01/Ontwerpen|Publicatie 2020.01 - MedMij]]

*'''2019'''
**[[MedMij:V2019.01_Ontwerpen|Publicatie 2019.01 - MedMij]]

==Technische ontwerpen==
*'''2020'''
**[[MedMij:V2020.01/FHIR_IG|Publicatie 2020.01 - MedMij]]

*'''2019'''
**[[MedMij:V2019.01_FHIR_IG|Publicatie 2019.01 - MedMij]]

==Kwalificatie==
Op MedMij-informatiestandaarden zijn Nictiz-kwalificaties van toepassing. Kwalificatie vindt plaats per systeemrol.

Kwalificatiescripts en meer informatie over de kwalificatie is te vinden op de kwalificatiepagina:
*'''2020'''
**[[MedMij:V2020.01/Kwalificatie|Publicatie 2020.01]]

*'''2019'''
**[[MedMij:V2019.01_Kwalificatie|Publicatie 2019.01]]

==Mappings==
De standaarden die zijn opgenomen in het MedMij-afsprakenstelsel baseren zich over het algemeen op [http://hl7.org/fhir/STU3 HL7 FHIR]. Voor zorgaanbiedersystemen die deze wijze van uitwisseling nog niet ondersteunen is mapping een optie. Ook voor leveranciers van systemen die HL7 FHIR willen gaan ondersteunen en zich afvragen hoe HL7 FHIR zich verhoudt tot hun huidige wijze van uitwisseling is de mapping-informatie een bruikbare bron van informatie.

*[[Mappingarchitectuur]]
*[[:Categorie:Mappings|Gedefinieerde mappings]]

==Archief==
*'''2018'''
*Functionele ontwerpen
**[[MedMij:V2018.06_Ontwerpen|Publicatie 2018.06 - MedMij]]
**[[MedMij:V2018.05_Ontwerpen|Publicatie 2018.05 - MedMij]]
**[[MedMij:V2018.04_Ontwerpen|Publicatie 2018.04 - MedMij]]
**[[MedMij:V2018.03_Ontwerpen|Publicatie 2018.03 - MedMij]]
**[[MedMij:V2018.02_Ontwerpen|Publicatie 2018.02 - MedMij]]
**[[MedMij:V2018.01_Ontwerpen|Publicatie 2018.01 - MedMij]]
*Technische ontwerpen
**[[MedMij:V2018.06_FHIR_IG|Publicatie 2018.06 - MedMij]]
**[[MedMij:V2018.05_FHIR_IG|Publicatie 2018.05 - MedMij]]
**[[MedMij:V2018.04_FHIR_IG|Publicatie 2018.04 - MedMij]]
**[[MedMij:V2018.03_FHIR_IG|Publicatie 2018.03 - MedMij]]
**[[MedMij:V2018.02_FHIR_IG|Publicatie 2018.02 - MedMij]]
**[[MedMij:V2018.01_FHIR_IG|Publicatie 2018.01 - MedMij]]
 
*'''2017'''
*Functionele ontwerpen
**[[MedMij:V2017.04_Ontwerpen|Publicatie 2017.04 - MedMij]]
**[[MedMij:V2017.03_Ontwerpen|Publicatie 2017.03 - MedMij]]
**[[MedMij:V2017.02_Ontwerpen|Publicatie 2017.02 - MedMij]]
**[[MedMij:V2017.01_Ontwerpen|Publicatie 2017.01 - MedMij]]
*Technische ontwerpen
**[[MedMij:v2017.04_FHIR_IG|Publicatie 2017.04 - MedMij]]
**[[MedMij:v2017.03_FHIR_IG|Publicatie 2017.03 - MedMij]]
** Publicatie 2017.02 - MedMij (zonder FHIR gedeelte)
**[[MedMij:v2017.01_FHIR_IG|Publicatie 2017.01 - MedMij]]
*Overig
**[[MedMij:V1.0_FHIR_Training|V1.0 FHIR Training]]
**[[MedMij:V1.0_FHIR_Connectathon_DevDays2017|Connectathon FHIR DevDays 2017]]
 
*'''2016'''
**[[MedMij:V1.0_Standards|MedMij Information Standards]]

**[https://www.nictiz.nl/Paginas/Medicatieveiligheid.aspx Medicatieveiligheid (waaronder ICA) 6.12.x en Medicatieproces 9.0.x] (HL7v3)
**[https://www.nictiz.nl/Paginas/Laboratoria.aspx Laboratorium - e-Lab/Lab2Lab] (HL7v3 en HL7v2)
**[https://www.nictiz.nl/publicaties/overige-publicaties/edifact-implementatiehandleiding-diverse-berichten MEDLAB 1.0] (Edifact)
''ICA = Intoleranties Co-morbiditeiten en Allergieën''

Vissue-MM-1446 Landingspagina MedMij

2020-10-16T11:12:55Z

Stephan Opdenberg: /* Kwalificatie */

Vissue-MM-1446 Landingspagina MedMij

2020-10-07T13:23:24Z

Stephan Opdenberg: /* Kwalificatie */

__NUMBEREDHEADINGS__
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]

<imagemap>Bestand:Afsprakenstelsel-functioneel-technisch-banner_00_alle.png|center|500px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:Vcurrent_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:Vcurrent_FHIR_IG|Technisch]]
desc none
</imagemap>

==MedMij wiki structuuroverzicht==
<imagemap>Bestand:MedMij_wiki_structuur_overzicht.png||750px|alt=MedMij Wiki-structuuroverzicht
circle 344 894 333 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
rect 1017 1260 1517 1407 [[Landingspagina_MedMij#Mappings|Mappings]]
rect 2123 3 2740 847 [[MedMij:Vcurrent_Ontwerpen|Functioneel (huidige versie)]]
rect 2123 945 2740 1789 [[MedMij:Vcurrent_FHIR_IG|Technisch (huidige versie)]]
desc none
</imagemap>

==Functionele ontwerpen==
*'''2020'''
**[[MedMij:V2020.01/Ontwerpen|Publicatie 2020.01 - MedMij]]

*'''2019'''
**[[MedMij:V2019.01_Ontwerpen|Publicatie 2019.01 - MedMij]]

==Technische ontwerpen==
*'''2020'''
**[[MedMij:V2020.01/FHIR_IG|Publicatie 2020.01 - MedMij]]

*'''2019'''
**[[MedMij:V2019.01_FHIR_IG|Publicatie 2019.01 - MedMij]]

==Kwalificatie==
Op deze informatiestandaarden zijn Nictiz kwalificaties van toepassing. Kwalificatie vindt plaats per systeemrol
*'''2020'''
**[[MedMij:V2020.01/Kwalificatie|Publicatie 2020.01]]

*'''2019'''
**[[MedMij:V2019.01_Kwalificatie|Publicatie 2019.01]]

==Mappings==
De standaarden die zijn opgenomen in het MedMij-afsprakenstelsel baseren zich over het algemeen op [http://hl7.org/fhir/STU3 HL7 FHIR]. Voor zorgaanbiedersystemen die deze wijze van uitwisseling nog niet ondersteunen is mapping een optie. Ook voor leveranciers van systemen die HL7 FHIR willen gaan ondersteunen en zich afvragen hoe HL7 FHIR zich verhoudt tot hun huidige wijze van uitwisseling is de mapping-informatie een bruikbare bron van informatie.

*[[Mappingarchitectuur]]
*[[:Categorie:Mappings|Gedefinieerde mappings]]

==Archief==
*'''2018'''
*Functionele ontwerpen
**[[MedMij:V2018.06_Ontwerpen|Publicatie 2018.06 - MedMij]]
**[[MedMij:V2018.05_Ontwerpen|Publicatie 2018.05 - MedMij]]
**[[MedMij:V2018.04_Ontwerpen|Publicatie 2018.04 - MedMij]]
**[[MedMij:V2018.03_Ontwerpen|Publicatie 2018.03 - MedMij]]
**[[MedMij:V2018.02_Ontwerpen|Publicatie 2018.02 - MedMij]]
**[[MedMij:V2018.01_Ontwerpen|Publicatie 2018.01 - MedMij]]
*Technische ontwerpen
**[[MedMij:V2018.06_FHIR_IG|Publicatie 2018.06 - MedMij]]
**[[MedMij:V2018.05_FHIR_IG|Publicatie 2018.05 - MedMij]]
**[[MedMij:V2018.04_FHIR_IG|Publicatie 2018.04 - MedMij]]
**[[MedMij:V2018.03_FHIR_IG|Publicatie 2018.03 - MedMij]]
**[[MedMij:V2018.02_FHIR_IG|Publicatie 2018.02 - MedMij]]
**[[MedMij:V2018.01_FHIR_IG|Publicatie 2018.01 - MedMij]]
 
*'''2017'''
*Functionele ontwerpen
**[[MedMij:V2017.04_Ontwerpen|Publicatie 2017.04 - MedMij]]
**[[MedMij:V2017.03_Ontwerpen|Publicatie 2017.03 - MedMij]]
**[[MedMij:V2017.02_Ontwerpen|Publicatie 2017.02 - MedMij]]
**[[MedMij:V2017.01_Ontwerpen|Publicatie 2017.01 - MedMij]]
*Technische ontwerpen
**[[MedMij:v2017.04_FHIR_IG|Publicatie 2017.04 - MedMij]]
**[[MedMij:v2017.03_FHIR_IG|Publicatie 2017.03 - MedMij]]
** Publicatie 2017.02 - MedMij (zonder FHIR gedeelte)
**[[MedMij:v2017.01_FHIR_IG|Publicatie 2017.01 - MedMij]]
*Overig
**[[MedMij:V1.0_FHIR_Training|V1.0 FHIR Training]]
**[[MedMij:V1.0_FHIR_Connectathon_DevDays2017|Connectathon FHIR DevDays 2017]]
 
*'''2016'''
**[[MedMij:V1.0_Standards|MedMij Information Standards]]

**[https://www.nictiz.nl/Paginas/Medicatieveiligheid.aspx Medicatieveiligheid (waaronder ICA) 6.12.x en Medicatieproces 9.0.x] (HL7v3)
**[https://www.nictiz.nl/Paginas/Laboratoria.aspx Laboratorium - e-Lab/Lab2Lab] (HL7v3 en HL7v2)
**[https://www.nictiz.nl/publicaties/overige-publicaties/edifact-implementatiehandleiding-diverse-berichten MEDLAB 1.0] (Edifact)
''ICA = Intoleranties Co-morbiditeiten en Allergieën''

Vissue-MM-1446 Landingspagina MedMij

2020-10-07T13:22:25Z

Stephan Opdenberg: /* Introductie */

__NUMBEREDHEADINGS__
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]

<imagemap>Bestand:Afsprakenstelsel-functioneel-technisch-banner_00_alle.png|center|500px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:Vcurrent_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:Vcurrent_FHIR_IG|Technisch]]
desc none
</imagemap>

==MedMij wiki structuuroverzicht==
<imagemap>Bestand:MedMij_wiki_structuur_overzicht.png||750px|alt=MedMij Wiki-structuuroverzicht
circle 344 894 333 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
rect 1017 1260 1517 1407 [[Landingspagina_MedMij#Mappings|Mappings]]
rect 2123 3 2740 847 [[MedMij:Vcurrent_Ontwerpen|Functioneel (huidige versie)]]
rect 2123 945 2740 1789 [[MedMij:Vcurrent_FHIR_IG|Technisch (huidige versie)]]
desc none
</imagemap>

==Functionele ontwerpen==
*'''2020'''
**[[MedMij:V2020.01/Ontwerpen|Publicatie 2020.01 - MedMij]]

*'''2019'''
**[[MedMij:V2019.01_Ontwerpen|Publicatie 2019.01 - MedMij]]

==Technische ontwerpen==
*'''2020'''
**[[MedMij:V2020.01/FHIR_IG|Publicatie 2020.01 - MedMij]]

*'''2019'''
**[[MedMij:V2019.01_FHIR_IG|Publicatie 2019.01 - MedMij]]

==Kwalificatie==
Op deze informatiestandaarden zijn Nictiz kwalificaties van toepassing. Kwalificatie vindt plaats per systeemrol
*'''2020'''
**[[#lst:MedMij:V2020.01/Kwalificatie|Publicatie 2020.01]]

*'''2019'''
**[[MedMij:V2019.01_Kwalificatie|Publicatie 2019.01]]

==Mappings==
De standaarden die zijn opgenomen in het MedMij-afsprakenstelsel baseren zich over het algemeen op [http://hl7.org/fhir/STU3 HL7 FHIR]. Voor zorgaanbiedersystemen die deze wijze van uitwisseling nog niet ondersteunen is mapping een optie. Ook voor leveranciers van systemen die HL7 FHIR willen gaan ondersteunen en zich afvragen hoe HL7 FHIR zich verhoudt tot hun huidige wijze van uitwisseling is de mapping-informatie een bruikbare bron van informatie.

*[[Mappingarchitectuur]]
*[[:Categorie:Mappings|Gedefinieerde mappings]]

==Archief==
*'''2018'''
*Functionele ontwerpen
**[[MedMij:V2018.06_Ontwerpen|Publicatie 2018.06 - MedMij]]
**[[MedMij:V2018.05_Ontwerpen|Publicatie 2018.05 - MedMij]]
**[[MedMij:V2018.04_Ontwerpen|Publicatie 2018.04 - MedMij]]
**[[MedMij:V2018.03_Ontwerpen|Publicatie 2018.03 - MedMij]]
**[[MedMij:V2018.02_Ontwerpen|Publicatie 2018.02 - MedMij]]
**[[MedMij:V2018.01_Ontwerpen|Publicatie 2018.01 - MedMij]]
*Technische ontwerpen
**[[MedMij:V2018.06_FHIR_IG|Publicatie 2018.06 - MedMij]]
**[[MedMij:V2018.05_FHIR_IG|Publicatie 2018.05 - MedMij]]
**[[MedMij:V2018.04_FHIR_IG|Publicatie 2018.04 - MedMij]]
**[[MedMij:V2018.03_FHIR_IG|Publicatie 2018.03 - MedMij]]
**[[MedMij:V2018.02_FHIR_IG|Publicatie 2018.02 - MedMij]]
**[[MedMij:V2018.01_FHIR_IG|Publicatie 2018.01 - MedMij]]
 
*'''2017'''
*Functionele ontwerpen
**[[MedMij:V2017.04_Ontwerpen|Publicatie 2017.04 - MedMij]]
**[[MedMij:V2017.03_Ontwerpen|Publicatie 2017.03 - MedMij]]
**[[MedMij:V2017.02_Ontwerpen|Publicatie 2017.02 - MedMij]]
**[[MedMij:V2017.01_Ontwerpen|Publicatie 2017.01 - MedMij]]
*Technische ontwerpen
**[[MedMij:v2017.04_FHIR_IG|Publicatie 2017.04 - MedMij]]
**[[MedMij:v2017.03_FHIR_IG|Publicatie 2017.03 - MedMij]]
** Publicatie 2017.02 - MedMij (zonder FHIR gedeelte)
**[[MedMij:v2017.01_FHIR_IG|Publicatie 2017.01 - MedMij]]
*Overig
**[[MedMij:V1.0_FHIR_Training|V1.0 FHIR Training]]
**[[MedMij:V1.0_FHIR_Connectathon_DevDays2017|Connectathon FHIR DevDays 2017]]
 
*'''2016'''
**[[MedMij:V1.0_Standards|MedMij Information Standards]]

**[https://www.nictiz.nl/Paginas/Medicatieveiligheid.aspx Medicatieveiligheid (waaronder ICA) 6.12.x en Medicatieproces 9.0.x] (HL7v3)
**[https://www.nictiz.nl/Paginas/Laboratoria.aspx Laboratorium - e-Lab/Lab2Lab] (HL7v3 en HL7v2)
**[https://www.nictiz.nl/publicaties/overige-publicaties/edifact-implementatiehandleiding-diverse-berichten MEDLAB 1.0] (Edifact)
''ICA = Intoleranties Co-morbiditeiten en Allergieën''

Vissue-MM-1446 Landingspagina MedMij

2020-10-07T13:11:29Z

Stephan Opdenberg: Nieuwe pagina aangemaakt met '__NUMBEREDHEADINGS__ Naar medmij.nl <imagemap>Bestand:Afsprakenstelsel-functioneel-technisch-banner_00_...'

__NUMBEREDHEADINGS__
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]

<imagemap>Bestand:Afsprakenstelsel-functioneel-technisch-banner_00_alle.png|center|500px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:Vcurrent_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:Vcurrent_FHIR_IG|Technisch]]
desc none
</imagemap>

==MedMij wiki structuuroverzicht==
<imagemap>Bestand:MedMij_wiki_structuur_overzicht.png||750px|alt=MedMij Wiki-structuuroverzicht
circle 344 894 333 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
rect 1017 1260 1517 1407 [[Landingspagina_MedMij#Mappings|Mappings]]
rect 2123 3 2740 847 [[MedMij:Vcurrent_Ontwerpen|Functioneel (huidige versie)]]
rect 2123 945 2740 1789 [[MedMij:Vcurrent_FHIR_IG|Technisch (huidige versie)]]
desc none
</imagemap>

==Functionele ontwerpen==
*'''2020'''
**[[MedMij:V2020.01/Ontwerpen|Publicatie 2020.01 - MedMij]]

*'''2019'''
**[[MedMij:V2019.01_Ontwerpen|Publicatie 2019.01 - MedMij]]

==Technische ontwerpen==
*'''2020'''
**[[MedMij:V2020.01/FHIR_IG|Publicatie 2020.01 - MedMij]]

*'''2019'''
**[[MedMij:V2019.01_FHIR_IG|Publicatie 2019.01 - MedMij]]

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2020.01/Ontwerpen|medmij_kwalificatie_introductie}}

==Mappings==
De standaarden die zijn opgenomen in het MedMij-afsprakenstelsel baseren zich over het algemeen op [http://hl7.org/fhir/STU3 HL7 FHIR]. Voor zorgaanbiedersystemen die deze wijze van uitwisseling nog niet ondersteunen is mapping een optie. Ook voor leveranciers van systemen die HL7 FHIR willen gaan ondersteunen en zich afvragen hoe HL7 FHIR zich verhoudt tot hun huidige wijze van uitwisseling is de mapping-informatie een bruikbare bron van informatie.

*[[Mappingarchitectuur]]
*[[:Categorie:Mappings|Gedefinieerde mappings]]

==Archief==
*'''2018'''
*Functionele ontwerpen
**[[MedMij:V2018.06_Ontwerpen|Publicatie 2018.06 - MedMij]]
**[[MedMij:V2018.05_Ontwerpen|Publicatie 2018.05 - MedMij]]
**[[MedMij:V2018.04_Ontwerpen|Publicatie 2018.04 - MedMij]]
**[[MedMij:V2018.03_Ontwerpen|Publicatie 2018.03 - MedMij]]
**[[MedMij:V2018.02_Ontwerpen|Publicatie 2018.02 - MedMij]]
**[[MedMij:V2018.01_Ontwerpen|Publicatie 2018.01 - MedMij]]
*Technische ontwerpen
**[[MedMij:V2018.06_FHIR_IG|Publicatie 2018.06 - MedMij]]
**[[MedMij:V2018.05_FHIR_IG|Publicatie 2018.05 - MedMij]]
**[[MedMij:V2018.04_FHIR_IG|Publicatie 2018.04 - MedMij]]
**[[MedMij:V2018.03_FHIR_IG|Publicatie 2018.03 - MedMij]]
**[[MedMij:V2018.02_FHIR_IG|Publicatie 2018.02 - MedMij]]
**[[MedMij:V2018.01_FHIR_IG|Publicatie 2018.01 - MedMij]]
 
*'''2017'''
*Functionele ontwerpen
**[[MedMij:V2017.04_Ontwerpen|Publicatie 2017.04 - MedMij]]
**[[MedMij:V2017.03_Ontwerpen|Publicatie 2017.03 - MedMij]]
**[[MedMij:V2017.02_Ontwerpen|Publicatie 2017.02 - MedMij]]
**[[MedMij:V2017.01_Ontwerpen|Publicatie 2017.01 - MedMij]]
*Technische ontwerpen
**[[MedMij:v2017.04_FHIR_IG|Publicatie 2017.04 - MedMij]]
**[[MedMij:v2017.03_FHIR_IG|Publicatie 2017.03 - MedMij]]
** Publicatie 2017.02 - MedMij (zonder FHIR gedeelte)
**[[MedMij:v2017.01_FHIR_IG|Publicatie 2017.01 - MedMij]]
*Overig
**[[MedMij:V1.0_FHIR_Training|V1.0 FHIR Training]]
**[[MedMij:V1.0_FHIR_Connectathon_DevDays2017|Connectathon FHIR DevDays 2017]]
 
*'''2016'''
**[[MedMij:V1.0_Standards|MedMij Information Standards]]

**[https://www.nictiz.nl/Paginas/Medicatieveiligheid.aspx Medicatieveiligheid (waaronder ICA) 6.12.x en Medicatieproces 9.0.x] (HL7v3)
**[https://www.nictiz.nl/Paginas/Laboratoria.aspx Laboratorium - e-Lab/Lab2Lab] (HL7v3 en HL7v2)
**[https://www.nictiz.nl/publicaties/overige-publicaties/edifact-implementatiehandleiding-diverse-berichten MEDLAB 1.0] (Edifact)
''ICA = Intoleranties Co-morbiditeiten en Allergieën''

vpk:Draft FHIR eOverdracht

2020-05-14T10:44:47Z

Stephan Opdenberg: added a link to the overarching principles of MedMij for the

{{#customtitle:eOverdracht FHIR Implementation Guide}}
{{IssueBox|Work in progress - See [[vpk:V3.1_FHIR_eOverdracht_Proeftuin|official publication]] here.}}
=Introduction=

This page details the HL7 FHIR requirements for exchanging the data in the eOverdracht described in [[vpk:V3.1_Ontwerp_eOverdracht|the functional design]].

Implementation of these transactions is spread over multiple phases. In the first phase of the Proeftuin a simplified version of both the Aanmeldbericht en Overdrachtsbericht are being used. Both messages exist of four HCIMs listed in the table below. The Aanmeldbericht is send to the recieving organisation, which after confirmation of recieving the aanmeldberricht, gets send the Overdrachtbericht.
Phase two consists of the complete Aanmeldbericht as well as an incomplete Overdrachtsbericht. The Overdrachtsbericht is a subset of 11 HCIM's (complete set used in Aanmeldbericht) and an unstructured PDF containing the remaining data which are not part of the HCIM's.
Phase three is the complete dataset of the Aanmeldbericht, Overdrachtsbericht Volwassenen, Overdrachtsbericht Kinderen 0-1 jaar, Overdrachtsbericht Kinderen 1-18 jaar as PUSH messages.

This implementation guide assumes that the reader is familiar with [https://www.hl7.org/fhir/stu3/ FHIR(STU3)].

==Overarching FHIR principles==
* This implementation guide does not provide information on finding the right XIS, nor does it provide information about security. It is assumed that the sending XIS is able to make a connection with the receiving XIS.
* All FHIR resources used within eOverdracht SHALL conform to the profiles listed in this implementation guide and SHALL include the profile canonical URL in their <code>meta.profile</code> element.
* For overarching principles of the implementation of FHIR for eOverdracht, the FHIR implementation guide of [[MedMij:V2019.01_FHIR_IG#Use_case_overarching_principles|MedMij FHIR Implementation Guide, overarching principles]] should be advised startin from chapter 5.

==Package and dependencies==
eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{VersieInfo|V2019.01|package}}].
==Example instances==
Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Composition Composition examples]
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Bundle Bundle examples]

=Use case 1A: Send Overdrachtsbericht volwassenen (PUSH)=
'''NB:''' The use cases as publiced here are with reservation. Depending on the outcome of a discussion about the scenario's with third parties implementing this standard, the use cases might differ. However the cotnent of the uses cases will remain the same as stated below.
==Introduction==
The Send Overdrachtsbericht scenario is used by the sending XIS to send the relevant data for the patient care to the receiving XIS. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_volwassenen|Opbouw Overdrachtsbericht Volwassenen]].
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Overdrachtbericht (PUSH)
|style="background-color: white;" rowspan="2"|Send Overdrachtsbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Overdrachtsbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Overdrachtsbericht
|}
==Invocation==
The Send Overdrachtsbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Overdrachtsbericht (complete)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.
==Structure of the Overdrachtsbericht (complete)==
The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

The table below lists the FHIR profiles<ref name="nopackage">Please note that the direct links to the various conformance resources below will take you to the latest version, which might not match the package version. At time of writing, there is no way to render the conformance resource as found in the package. This is on the roadmap for Simplifier.</ref> that are applicable for the pilot implementation of the Overdrachtsbericht transaction.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Administratieve gegevens
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht}}
| Composition
| -
| -
| Declaration of the Send Aanmeldbericht transaction.
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="4"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nl-core-relatedperson}}
| RelatedPerson
| rowspan="2"|Contactpersoon
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| rowspan="2"| Zorgverlener sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| rowspan="2"| Zorgverlener ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Algemene patiënten context
|-
| Gezinssituatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FamilySituation|zib-FamilySituation}}
| FamilySituation
| Gezinssituatie
| v3.1(2017NL)
| -
|-
| Woonomgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LivingSituation|zib-LivingSituation}}
| Woonsituatie
| LivingSituation
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Levensovertuiging
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LifeStance|zib-LifeStance}}
| Levensovertuiging
| LifeStance
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AdvanceDirective|zib-AdvanceDirective}}
| Wilsverklaring
| AdvanceDirective
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Sociale omgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ParticipationInSociety|zib-ParticipationInSociety}}
| ParticipatieInMaatschappij
| ParticipationInSociety
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HelpFromOthers|zib-HelpFromOthers}}
| HulpVanAnderen
| HelpFromOthers
| v3.0 (2017NL)
| -
|-
| Communicatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/patient-proficiency|patient-proficiency}}
| Taalvaardigheid
| LanguageProfeciency
| v3.1(2017NL)
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Medische context
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| rowspan="7"| Meetwaarden
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|zib-BloodPressure}}
| Observation
| Bloeddruk
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PulseRate|zib-PulseRate}}
| Observation
| PolsFrequentie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyTemperature|zib-BodyTemperature}}
| Observation
| Lichaamstemperatuur
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Respiration|zib-Respiration}}
| Observation
| Ademhaling
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|zib-BodyWeight}}
| Observation
| Lichaamsgewicht
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|zib-BodyHeight}}
| Observation
| Lichaamslengte
| v3.1(2017NL)
| -
|-
| [https://zibs.nl/wiki/AlgemeneMeting-v3.0(2017NL) AlgemeneMeting]
| Observation
| AlgemeneMeting
| v3.0(2017NL)
| No FHIR profile is available yet for this HCIM.
|-
| Pijnscore
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PainScore|zib-PainScore}}
| Observation
| Pijnscore
| v3.1(2017NL)
| -
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: zorgplan
|-
| rowspan="3"| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TreatmentObjective|zib-TreatmentObjective}}
| Goal
| Behandeldoel
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NursingIntervention|zib-NursingIntervention}}
| Procedure
| VerpleegkundigeInterventie
| v3.2(2018NL)
| -
|-
| Zorgresultaat
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-OutcomeOfCare|zib-OutcomeOfCare}}
| DiagnisticReport
| UitkomstVanZorg
| v3.1(2017NL)
| -
|-
| rowspan="3"|Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|zib-ProcedureRequest}}
| ProcedureRequest
| rowspan="3"|OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eAfspraak-Appointment|eAfspraak-Appointment}}
| Appointment
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VaccinationRecommendation|zib-VaccinationRecommendation}}
| ImmunizationRecommendation
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht profile}}.
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: specificatie gezondheidstoestand
|-
| rowspan="12"| Zelfzorg
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToDrink|zib-AbilityToDrink}}
| Observation
| VermogenTotDrinken
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToEat|zib-AbilityToEat}}
| Observation
| VermogenTotEten
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities|zib-AbilityToPerformMouthcareActivities}}
| Observation
| rowspan="3"|VermogenTotMondverzorging
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities-MedicalDevice|zib-AbilityToPerformMouthcareActivities-MedicalDevice}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities-MedicalDeviceProduct|zib-AbilityToPerformMouthcareActivities-MedicalDeviceProduct}}
| Device
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToWashOneSelf|zib-AbilityToWashOneSelf}}
| Observation
| VermogenTotZichWassen
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToDressOneself|zib-AbilityToDressOneself}}
| Observation
| VermogenTotZichKleden
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToGroome|zib-AbilityToGroome}}
| Observation
| VermogenTotUiterlijkeVerzorging
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToUseToilet|zib-AbilityToUseToilet}}
| Observation
| VermogenTotToiletgang
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToManageMedication|zib-AbilityToManageMedication}}
| Observation
| VermogenTotZelfstandigMedicatiegebruik
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformNursingActivities|zib-AbilityToPerformNursingActivities}}
| Observation
| VermogenTotVerpleegtechnischeHandelingen
| v1.0(2017NL)
| -
|-
| toelichting zelfzorg
| -
| Explanation selfcare
| -
| Free text
|-
| Mobiliteit
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Mobility|zib-Mobility}}
| Observation
| Mobiliteit
| v3.1(2017NL)
| -
|-
| rowspan="7"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NutritionAdvice|zib-NutritionAdvice}}
| NutritionOrder
| Voedingsadvies
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SNAQScore|zib-SNAQScore}}
{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SNAQrcScore|zib-SNAQrcScore}}

{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SNAQrcScore|zib-SNAQ65+Score}}

{{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MUSTScore|zib-MUSTScore}}
| Observation
| SNAQScore

SNAQrcScore

SNAQ65+Score

MUSTScore
|v3.1(2017NL)

v1.0(2017NL)

v1.0(2017NL)

v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FluidBalance|zib-FluidBalance}}
| Observation
| Vochtbalans
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|zib-FeedingTubeSystem}}
| DeviceUseStatement
| rowspan="2"|SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-Product|zib-FeedingTubeSystem-Product}}
| Device
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|zib-Infusion}}
| DeviceUseStatement
| rowspan="2"|Infuus
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion-Product|zib-Infusion-Product}}
| Device
| v3.2(2017NL)
| -
|-
| rowspan="3"|Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BladderFunction|zib-BladderFunction}}
| Observation
| Blaasfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BowelFunction|zib-BowelFunction}}
| Observation
| Darmfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|-
| rowspan="4"| Huid
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BurnWound|zib-Burnwound}}
| Condition
| Brandwond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PressureUlcer|zib-PressureUlcer}}
| Condition
| DecubitusWond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SkinDisorder|zib-SkinDisorder}}
| Condition
| Huidaandoening
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Wound|zib-Wound}}
| Condition
| Wond
| v3.1(2017NL)
| -
|-
| rowspan="6"| Zintuigen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction|zib-HearingFunction}}
| Observation
| rowspan="3"| FunctieHoren
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid|zib-HearingFunction-HearingAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid-Product|zib-HearingFunction-HearingAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction|zib-VisualFunction}}
| Observation
| rowspan="3"|FunctieZien
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAid|zib-VisualAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAidProduct|zib-VisualAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| Ziektebeleving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-IllnessPerception|zib-IllnessPerception}}
| Observation
| Ziektebeleving
| v3.1(2017NL)
| -
|-
| Mentale status
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| rowspan="7"| Voortplanting
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy|zib-Pregnancy}}
| Condition
| Zwangerschap
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyStatus|zib-Pregnancy-PregnancyStatus}}
| Observation
| Zwanger
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-TermDate|zib-Pregnancy-TermDate}}
| Observation
| ATermDatum
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|zib-PregnancyDuration}}
| Observation
| Zwangerschapsduur
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-Parity|zib-Pregnancy-Parity}}
| Observation
| Pariteit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-Gravidity|zib-Pregnancy-Gravidity}}
| Observation
| Graviditeit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-DateLastMenstruation|zib-Pregnancy-DatelastMenstruation}}
| Observation
| DatumLaatsteMenstruatie
| v3.1(2017NL)
| -
|-
|}

=Use Case 2A: Send overdrachtsbericht kindzorg=
'''NB:''' The use cases as publiced here are with reservation. Depending on the outcome of a discussion about the scenario's with third parties implementing this standard, the use cases might differ. However the cotnent of the uses cases will remain the same as stated below.
==Introduction==
The Send Overdrachtsbericht scenario is used by the sending XIS to send the relevant data for the patient care to the receiving XIS.
For the use case "kindzorg" we distinquish between two age categories:
* Child between 0-1 years of age (zie ook [[vpk:v3.1_Opbouw_eOverdracht_kind_0_1|inhoudelijke opbouw van de verpleegkundige overdracht voor kinderen tussen 0-1 jaar]])
* Child between 1-18 years of age (zie ook [[vpk:v3.1_Opbouw_eOverdracht_kind_1_18|inhoudelijke opbouw van de verpleegkundige overdracht voor kinderen tussen 1-18 jaar]])
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Overdrachtbericht (PUSH)
|style="background-color: white;" rowspan="2"|Send Overdrachtsbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Overdrachtsbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Overdrachtsbericht
|}
==Invocation==
The Send Overdrachtsbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Overdrachtsbericht (Child 0-1)]] or [[#Structure of Overdrachtsbericht (Child 1-18)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.

==Structure of the Overdrachtsbericht (Child 0-1)==
The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

The table below lists the FHIR profiles<ref name="nopackage">Please note that the direct links to the various conformance resources below will take you to the latest version, which might not match the package version. At time of writing, there is no way to render the conformance resource as found in the package. This is on the roadmap for Simplifier.</ref> that are applicable for the implementation of the Overdrachtsbericht transaction.
{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Administratieve gegevens
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht}}
| Composition
| -
| -
| Declaration of the Send Aanmeldbericht transaction.
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="4"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nl-core-relatedperson}}
| RelatedPerson
| rowspan="2"|Contactpersoon
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| rowspan="2"| Zorgverlener sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| rowspan="2"| Zorgverlener ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Algemene patiënten contact
|-
| Gezinssituatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FamilySituation|zib-FamilySituation}}
| FamilySituation
| Gezinssituatie
| v3.1(2017NL)
| -
|-
| Woonomgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LivingSituation|zib-LivingSituation}}
| Woonsituatie
| LivingSituation
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Levensovertuiging
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LifeStance|zib-LifeStance}}
| Levensovertuiging
| LifeStance
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AdvanceDirective|zib-AdvanceDirective}}
| Wilsverklaring
| AdvanceDirective
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Sociale omgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ParticipationInSociety|zib-ParticipationInSociety}}
| ParticipatieInMaatschappij
| ParticipationInSociety
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HelpFromOthers|zib-HelpFromOthers}}
| HulpVanAnderen
| HelpFromOthers
| v3.0 (2017NL)
| -
|-
| Communicatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/patient-proficiency|patient-proficiency}}
| Taalvaardigheid
| LanguageProfeciency
| v3.1(2017NL)
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Medische context
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| rowspan="9"| Meetwaarden
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|zib-BloodPressure}}
| Observation
| Bloeddruk
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PulseRate|zib-PulseRate}}
| Observation
| PolsFrequentie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyTemperature|zib-BodyTemperature}}
| Observation
| Lichaamstemperatuur
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Respiration|zib-Respiration}}
| Observation
| Ademhaling
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|zib-BodyWeight}}
| Observation
| Lichaamsgewicht
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|zib-BodyHeight}}
| Observation
| Lichaamslengte
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HeadCircumference|zib-HeadCircumference}}
| Observation
| Schedelomvang
| v1.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ApgarScore|zib-ApgarScore}}
| Observation
| ApgarScore
| v1.0(2017NL)
| -
|-
| [https://zibs.nl/wiki/AlgemeneMeting-v3.0(2017NL) AlgemeneMeting]
| Observation
| AlgemeneMeting
| v3.0(2017NL)
| No fhir profile is available yet for this HCIM.
|-
| Pijnscore
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PainScore|zib-PainScore}}
| Observation
| Pijnscore
| v3.1(2017NL)
| -
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: zorgplan
|-
| rowspan="3"| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TreatmentObjective|zib-TreatmentObjective}}
| Goal
| Behandeldoel
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NursingIntervention|zib-NursingIntervention}}
| Procedure
| VerpleegkundigeInterventie
| v3.2(2018NL)
| -
|-
| Zorgresultaat
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-OutcomeOfCare|zib-OutcomeOfCare}}
| DiagnisticReport
| UitkomstVanZorg
| v3.1(2017NL)
| -
|-
| rowspan="3"|Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|zib-ProcedureRequest}}
| ProcedureRequest
| rowspan="3"|OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eAfspraak-Appointment|eAfspraak-Appointment}}
| Appointment
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VaccinationRecommendation|zib-VaccinationRecommendation}}
| ImmunizationRecommendation
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht profile}}.
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: specificatie gezondheidstoestand
|-
| rowspan="2"| Zelfzorg
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformNursingActivities|zib-AbilityToPerformNursingActivities}}
| Observation
| VermogenTotVerpleegtechnischeHandelingen
| v1.0(2017NL)
| -
|-
| toelichting zelfzorg
| -
| Explanation selfcare
| -
| Free text
|-
| rowspan="8"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NutritionAdvice|zib-NutritionAdvice}}
| NutritionOrder
| Voedingsadvies
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingPatternInfant|zib-FeedingPatternInfant}}
| Observation
| VoedingspatroonZuigeling
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-StrongKidsScore|zib-StrongKidsScore}}
| Observation
| StrongKidsScore
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FluidBalance|zib-FluidBalance}}
| Observation
| Vochtbalans
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|zib-FeedingTubeSystem}}
| DeviceUseStatement
| rowspan="2"|SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-Product|zib-FeedingTubeSystem-Product}}
| Device
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|zib-Infusion}}
| DeviceUseStatement
| rowspan="2"|Infuus
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion-Product|zib-Infusion-Product}}
| Device
| v3.2(2017NL)
| -
|-
| rowspan="3"|Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BladderFunction|zib-BladderFunction}}
| Observation
| Blaasfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BowelFunction|zib-BowelFunction}}
| Observation
| Darmfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|-
| rowspan="4"| Huid
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BurnWound|zib-Burnwound}}
| Condition
| Brandwond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PressureUlcer|zib-PressureUlcer}}
| Condition
| DecubitusWond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SkinDisorder|zib-SkinDisorder}}
| Condition
| Huidaandoening
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Wound|zib-Wound}}
| Condition
| Wond
| v3.1(2017NL)
| -
|-
| rowspan="6"| Zintuigen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction|zib-HearingFunction}}
| Observation
| rowspan="3"| FunctieHoren
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid|zib-HearingFunction-HearingAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid-Product|zib-HearingFunction-HearingAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction|zib-VisualFunction}}
| Observation
| rowspan="3"|FunctieZien
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAid|zib-VisualAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAid-Product|zib-VisualAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| Ziektebeleving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-IllnessPerception|zib-IllnessPerception}}
| Observation
| Ziektebeleving
| v3.1(2017NL)
| -
|-
| Mentale status
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| Ontwikkeling kind
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DevelopmentChild|zib-DevelopmentChild}}
| Observation
| Ontwikkeling kind
| v1.1(2017NL)
| -
|-
| Overige bijzonderheden kind
| -
| Free text
| -
| -
| Free text for particularities child
|-
|}

==Structure of Overdrachtsbericht (Child 1-18)==
The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

The table below lists the FHIR profiles<ref name="nopackage">Please note that the direct links to the various conformance resources below will take you to the latest version, which might not match the package version. At time of writing, there is no way to render the conformance resource as found in the package. This is on the roadmap for Simplifier.</ref> that are applicable for the implementation of the Overdrachtsbericht transaction.
{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Administratieve gegevens
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht}}
| Composition
| -
| -
| Declaration of the Send Aanmeldbericht transaction.
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="4"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nl-core-relatedperson}}
| RelatedPerson
| rowspan="2"|Contactpersoon
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| rowspan="2"| Zorgverlener sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| rowspan="2"| Zorgverlener ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2"| Zorgverlener
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Algemene patiënten context
|-
| Gezinssituatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FamilySituation|zib-FamilySituation}}
| FamilySituation
| Gezinssituatie
| v3.1(2017NL)
| -
|-
| Woonomgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LivingSituation|zib-LivingSituation}}
| Woonsituatie
| LivingSituation
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Levensovertuiging
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LifeStance|zib-LifeStance}}
| Levensovertuiging
| LifeStance
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AdvanceDirective|zib-AdvanceDirective}}
| Wilsverklaring
| AdvanceDirective
| v3.1 (2017NL)
| -
|-
| rowspan="2"| Sociale omgeving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ParticipationInSociety|zib-ParticipationInSociety}}
| ParticipatieInMaatschappij
| ParticipationInSociety
| v3.1 (2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HelpFromOthers|zib-HelpFromOthers}}
| HulpVanAnderen
| HelpFromOthers
| v3.0 (2017NL)
| -
|-
| Communicatie
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/patient-proficiency|patient-proficiency}}
| Taalvaardigheid
| LanguageProfeciency
| v3.1(2017NL)
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Medische context
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| rowspan="7"| Meetwaarden
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure|zib-BloodPressure}}
| Observation
| Bloeddruk
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PulseRate|zib-PulseRate}}
| Observation
| PolsFrequentie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyTemperature|zib-BodyTemperature}}
| Observation
| Lichaamstemperatuur
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Respiration|zib-Respiration}}
| Observation
| Ademhaling
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight|zib-BodyWeight}}
| Observation
| Lichaamsgewicht
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight|zib-BodyHeight}}
| Observation
| Lichaamslengte
| v3.1(2017NL)
| -
|-
| [https://zibs.nl/wiki/AlgemeneMeting-v3.0(2017NL) AlgemeneMeting]
| Observation
| AlgemeneMeting
| v3.0(2017NL)
| No fhir profile is available yet for this HCIM.
|-
| rowspan="4"|Pijnscore
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PainScore|zib-PainScore}}
| Observation
| Pijnscore
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ComfortScale|zib-ComfortScale}}
| Observation
| ComfortScore
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FLACCPainScale|zib-FLACCPainScale}}
| Observation
| FLACCPijnScore
| v1.0(2017)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ChecklistPainBehaviour|zib-ChecklistPainBehaviour}}
| Observation
| ChecklijstPijnScore
| v1.0(2017NL)
| -
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: zorgplan
|-
| rowspan="3"| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TreatmentObjective|zib-TreatmentObjective}}
| Goal
| Behandeldoel
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NursingIntervention|zib-NursingIntervention}}
| Procedure
| VerpleegkundigeInterventie
| v3.2(2018NL)
| -
|-
| Zorgresultaat
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-OutcomeOfCare|zib-OutcomeOfCare}}
| DiagnisticReport
| UitkomstVanZorg
| v3.1(2017NL)
| -
|-
| rowspan="3"|Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|zib-ProcedureRequest}}
| ProcedureRequest
| rowspan="3"|OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eAfspraak-Appointment|eAfspraak-Appointment}}
| Appointment
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VaccinationRecommendation|zib-VaccinationRecommendation}}
| ImmunizationRecommendation
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht profile}}.
|-
| colspan="6" style="text-align: center; background-color: #4AB8A7; color: white" | Verpleegkundige context: specificatie gezondheidstoestand
|-
| rowspan="12"| Zelfzorg
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToDrink|zib-AbilityToDrink}}
| Observation
| VermogenTotDrinken
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToEat|zib-AbilityToEat}}
| Observation
| VermogenTotEten
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities|zib-AbilityToPerformMouthcareActivities}}
| Observation
| rowspan="3"|VermogenTotMondverzorging
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities-MedicalDevice|zib-AbilityToPerformMouthcareActivities-MedicalDevice}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformMouthcareActivities-MedicalDeviceProduct|zib-AbilityToPerformMouthcareActivities-MedicalDeviceProduct}}
| Device
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToWashOneSelf|zib-AbilityToWashOneSelf}}
| Observation
| VermogenTotZichWassen
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToDressOneself|zib-AbilityToDressOneself}}
| Observation
| VermogenTotZichKleden
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToGroome|zib-AbilityToGroome}}
| Observation
| VermogenTotUiterlijkeVerzorging
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToUseToilet|zib-AbilityToUseToilet}}
| Observation
| VermogenTotToiletgang
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToManageMedication|zib-AbilityToManageMedication}}
| Observation
| VermogenTotZelfstandigMedicatiegebruik
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AbilityToPerformNursingActivities|zib-AbilityToPerformNursingActivities}}
| Observation
| VermogenTotVerpleegtechnischeHandelingen
| v1.0(2017NL)
| -
|-
| toelichting zelfzorg
| -
| Explanation selfcare
| -
| Free text
|-
| Mobiliteit
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Mobility|zib-Mobility}}
| Observation
| Mobiliteit
| v3.1(2017NL)
| -
|-
| rowspan="7"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NutritionAdvice|zib-NutritionAdvice}}
| NutritionOrder
| Voedingsadvies
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-StrongKidsScore|zib-StrongKidsScore}}
| Observation
| StrongKidsScore
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FluidBalance|zib-FluidBalance}}
| Observation
| Vochtbalans
| v1.0(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|zib-FeedingTubeSystem}}
| DeviceUseStatement
| rowspan="2"|SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem-Product|zib-FeedingTubeSystem-Product}}
| Device
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|zib-Infusion}}
| DeviceUseStatement
| rowspan="2"|Infuus
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion-Product|zib-Infusion-Product}}
| Device
| v3.2(2017NL)
| -
|-
| rowspan="3"|Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BladderFunction|zib-BladderFunction}}
| Observation
| Blaasfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BowelFunction|zib-BowelFunction}}
| Observation
| Darmfunctie
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|-
| rowspan="4"| Huid
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BurnWound|zib-Burnwound}}
| Condition
| Brandwond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-PressureUlcer|zib-PressureUlcer}}
| Condition
| DecubitusWond
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-SkinDisorder|zib-SkinDisorder}}
| Condition
| Huidaandoening
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Wound|zib-Wound}}
| Condition
| Wond
| v3.1(2017NL)
| -
|-
| rowspan="6"| Zintuigen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction|zib-HearingFunction}}
| Observation
| rowspan="3"| FunctieHoren
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid|zib-HearingFunction-HearingAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-HearingFunction-HearingAid-Product|zib-HearingFunction-HearingAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction|zib-VisualFunction}}
| Observation
| rowspan="3"|FunctieZien
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAid|zib-VisualAid}}
| DeviceUseStatement
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VisualFunction-VisualAid-Product|zib-VisualAid-Product}}
| Device
| v3.1(2017NL)
| -
|-
| Ziektebeleving
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-IllnessPerception|zib-IllnessPerception}}
| Observation
| Ziektebeleving
| v3.1(2017NL)
| -
|-
| Mentale status
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| Ontwikkeling kind
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DevelopmentChild|zib-DevelopmentChild}}
| Observation
| OntwikkelingKind
| v1.1(2017NL)
| -
|-
| rowspan="7"| Voortplanting
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy|zib-Pregnancy}}
| Condition
| Zwangerschap
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyStatus|zib-Pregnancy-PregnancyStatus}}
| Observation
| Zwanger
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-TermDate|zib-Pregnancy-TermDate}}
| Observation
| ATermDatum
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-PregnancyDuration|zib-PregnancyDuration}}
| Observation
| Zwangerschapsduur
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-Parity|zib-Pregnancy-Parity}}
| Observation
| Pariteit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-Gravidity|zib-Pregnancy-Gravidity}}
| Observation
| Graviditeit
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Pregnancy-DateLastMenstruation|zib-Pregnancy-DatelastMenstruation}}
| Observation
| DatumLaatsteMenstruatie
| v3.1(2017NL)
| -
|-
| Overige bijzonderheden kind
| -
| -
| free text
| -
| Free text for particularities of child
|-
|}

=Use case 3A: Send Aanmeldbericht (PUSH)=
'''NB:''' The use cases as publiced here are with reservation. Depending on the outcome of a discussion about the scenario's with third parties implementing this standard, the use cases might differ. However the cotnent of the uses cases will remain the same as stated below.
==Introduction==
The Send Aanmeldbericht scenario is used by the sending XIS to send the relevant data for the patient intake to the receiving XIS, and constitutes a subset of the Overdrachtsbericht. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_aanmelding|Opbouw Aanmeldbericht]]. For the pilot a limited subset is implemented.
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht(PUSH)
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Aanmeldbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Aanmeldbericht
|}
==Invocation==
The Send Aanmeldbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Aanmeldbericht]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.

==Structure of the Aanmeldbericht==
The Aanmeldbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

During phase 1, the Aanmeldbericht is based 4 HCIMs (Patient, Betaler, Contactpersoon en Zorgaanbieder) and uses a PDF to send the remaining data unstructured. The table below lists the FHIR profiles<ref name="nopackage"/> that are applicable for the pilot implementation of the Aanmeldbericht transaction. All resources SHALL conform to the profiles listed in this table and SHALL include the profile canonical URL in the <code>meta.profile</code> element.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht}}
| Composition
| -
| -
| Declaration of the Send Aanmeldbericht transaction.
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="3"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nl-core-relatedperson}}
| RelatedPerson
| Contactpersoon
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| rowspan="2"| Organization
| rowspan="2"| Zorgaanbieder
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|zib-ProcedureRequest}}
| ProcedureRequest
| OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht profile}}.
|-
| rowspan="2"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|zib-FeedingTubeSystem}}
| DeviceUseStatement
| SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|zib-Infusion}}
| DeviceUseStatement
| Infuus
| v3.2(2017NL)
| -
|-
| Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|}

=FHIR Documents=
Both the Aanmeldbericht and the Overdrachtsbericht are sent as a [https://www.hl7.org/fhir/STU3/documents.html FHIR Document]. A document is a FHIR Bundle that assembles all relevant resources that need to be exchanged, together with a [https://www.hl7.org/fhir/STU3/composition.html Composition resource] that summarizes and references all these resources.

A FHIR document is immutable and considered to be attested by a healthcare professional.
==Creating documents==
To construct a document, a FHIR Composition resource is created that summarizes and references all the resources that need to be exchanged. This Composition resource is then placed together with all referenced resources in a Bundle with <code>Bundle.type</code> set to "document". The Composition resource SHALL be the first entry.

Profiles have been created for both the Composition and the document Bundle resources for each transaction within eOverdracht. All documents SHOULD adhere to these profiles, which are summarized in this implementation guide at the transaction level.
==Sending documents==
The document should be sent as an HTTP POST operation on the target XIS's base:
POST [base] {?_format=[mime-type]}
where the body of the POST request is the document.
==Processing documents==
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS and each <code>Bundle.entry</code> should be treated as a <code>create</code> interaction for the <code>Bundle.entry.resource</code>. When the receiving XIS cannot create a new resource because of incorrect data or business rules, it should perform a rollback of the creation of any previous entries.

On success, the target XIS SHALL respond:
* With the HTTP status code 201 Created.
* With the Location header containing the new logical id and version id of the created resource version.
* With a response body set to a Bundle of type "transaction-response", containing one entry for each entry in the request, in the same order, with the outcome of processing the entry. The sender may use the returned Bundle to track the outcomes of processing the entry, and the identities assigned to the resources by the server.

On failure, the target XIS SHALL respond:
* With an HTTP status code set appropriate to the processing outcome:
** When the resource syntax or data is incorrect or invalid, the status code should be 400 Bad Request.
** When the server rejects the content of the resource because of business rules, the status code should be 422 Unprocessable Entity.
** Additional HTTP status code may be used if more appropriate.
* With a response body set to a FHIR [http://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] resource with detailed error messages describing the reason for the error.

=FHIR CapabilityStatements=
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-servercapabilities-phase-one|CapabilityStatement server}}
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-clientcapabilities-phase-one|CapabilityStatement server}}

=Footnotes=
<references />

Landingspagina Verpleegkundige Zorg

2020-05-08T11:19:03Z

Stephan Opdenberg: toevoeging van de link naar de pagina van fase 2 van de proeftuin

__NUMBEREDHEADINGS__
=eOverdracht (Verpleegkundige overdracht)=
De informatiestandaard eOverdracht is gericht op informatie-uitwisseling tussen verpleegkundige en verzorgende zorgprofessionals bij overdracht van een patiënt/cliënt tussen zorginstellingen.

De informatiestandaard eOverdracht is gebaseerd op [https://zibs.nl zorginformatiebouwstenen (zibs)], publicatie 2017. De daadwerkelijke uitwisseling vindt plaats door middel van [https://www.hl7.org/fhir/ HL7 FHIR (STU3)].

==Functioneel en technisch ontwerp==
===Actuele versie===
De actuele versie van eOverdracht is 3.1 ([http://decor.nictiz.nl/pub/eoverdracht/e-overdracht-html-20190617T145353/project.html zie de release notes op ART-DECOR]). ''Deze versie bevindt zich nog in de ontwerpfase.''
* [[vpk:V3.1_Ontwerp_eOverdracht|Functioneel ontwerp eOverdracht 3.1]]
* [[vpk:V3.1_FHIR_eOverdracht|Technisch ontwerp (FHIR implementation guide) eOverdracht 3.1]]

===Proeftuinen Regeling InZicht===
Een vereenvoudigde versie van eOverdracht wordt beproefd in het kader van de [https://www.tenderned.nl/tenderned-tap/aankondigingen/164165 Proeftuinen Regeling InZicht]. Voor deze vereenvoudigde versie wordt slechts een beperkte set zibs gebruikt, aangevuld met een PDF-document om de overige gegevens ongestructureerd uit te wisselen. In de eerste fase worden slechts de administratieve gegevens uitgewisseld, later worden er geleidelijk meer zibs gebruikt.
* [[vpk:V3.1_eOverdracht_Proeftuin|Functioneel ontwerp eOverdracht Proeftuinen]]
* Technisch ontwerp (FHIR implementation guide) eOverdracht Proeftuinen
** [[vpk:V3.1_FHIR_eOverdracht_Proeftuin|Technisch ontwerp fase 1]]
** [[vpk:V3.1_FHIR_eOverdracht_Proeftuin_phase_2|Technisch ontwerp fase 2]]

==Mappings==
In eOverdracht wordt gebruik gemaakt van de zib Probleem, die de [https://www.nictiz.nl/standaardisatie/terminologiecentrum/referentielijsten/nationale-kernset/ Nationale Kernset Patiëntproblemen (SNOMED CT referentieset)] gebruikt. Voor het gebruik van andere classificaties zijn [https://www.nictiz.nl/standaardisatie/terminologiecentrum/referentielijsten/inbouwen-snomed-referentieset/ mapping referentiesets] beschikbaar van SNOMED CT naar deze classificaties (NANDA I - diagnoses, Omaha System, ICF). Voor meer achtergrondinformatie over de totstandkoming van de mapping<ref>Kieft, R. A. M. M., Vreeke, E. M., de Groot, E. M., de Graaf-Waar, H. I., van Gool, C. H., Koster, N., (..) Delnoij, D. M. J., ''Mapping the Dutch SNOMED CT subset to Omaha System, NANDA International and International Classification of Functioning, Disability and Health.'' [https://doi.org/10.1016/j.ijmedinf.2017.12.025 International Journal of Medical Informatics, 111(December 2017), 77–82]</ref><ref>Kieft, R. A. M. M., Vreeke, E. M., De Groot, E. M., Volkert, P. A., Francke, A. L., & Delnoij, D. M. J., ''The development of a nursing subset of patient problems to support interoperability.'' [https://doi.org/10.1186/s12911-017-0567-5 BMC Medical Informatics and Decision Making, 17(1), 1–12]</ref>.

==Overige informatie==
===Totstandkoming===
De informatiestandaard eOverdracht versies 3.x worden stapsgewijs ontwikkeld met een brede groep belanghebbenden. Dit proces is in detail beschreven [[vpk:V3.x_Methode_ontwikkeling_eOverdracht|op deze pagina]].

===Beheerstructuur===
* [https://www.nictiz.nl/wp-content/uploads/Beheer-informatiestandaard-eOverdacht.pdf Beheerdocument eOverdracht v3.1]: voor beheer van de specifieke informatiestandaard eOverdracht.
* [https://www.nictiz.nl/standaardisatie/zib-centrum/ Zib-centrum]: voor overkoepelend beheer van de zorginformatiebouwstenen (zibs) waaruit de informatiestandaard eOverdracht is opgebouwd.

===Eerdere versies===
* [[vpk:V3.0_Ontwerp_eOverdracht|eOverdracht 3.0 (obsoleet)]]

=Thema-specifieke standaarden=
Thema-specifieke standaarden zijn ontwikkeld in het kader van [https://www.nictiz.nl/nieuws/betere-pijnbehandeling-dankzij-beslisboom/ verpleegkundige beslissingsondersteuning] met een tweeledig doel:
#Ondersteuning klinisch redeneren: verpleegkundigen helpen met het stapsgewijs analyseren van observaties tot een patiëntprobleem waarvoor bepaalde verpleegkundige interventies nodig zijn, volgens de zorginhoudelijke richtlijnen (kwaliteitsstandaarden)
#Bevorderen gestandaardiseerde verslaglegging: het vastleggen van de observaties, patiëntproblemen en interventies die nodig zijn voor en de uitkomst zijn van deze beslissingsondersteuning volgens de bredere standaarden m.n. zorginformatiebouwstenen (zibs) die veelal ook in eOverdracht (zie boven) voorkomen.
Deze thema-specifieke standaarden worden gebruikt voor verslaglegging bij de primaire zorg. Deze vastgelegde gegevens kunnen vervolgens gebruikt worden als voorinvulling van bijv. overdrachtsbericht volgens eOverdracht, omdat deze gebruikmaken van dezelfde zibs.

De volgende thema-specifieke standaarden zijn beschikbaar:
* [[vpk:v1.0_Ontwerp_Delier|Functioneel ontwerp Delier v1.0]]
* [[vpk:V1.0_Ontwerp_Pijn|Functioneel ontwerp Pijn v1.0]]
* [[vpk:V1.0_Ontwerp_PsychosocialeZorg|Functioneel ontwerp Psychosociale zorg v1.0]]
* [[vpk:Vdraft_Ontwerp_RisicoSuicide|Functioneel ontwerp Risico op suïcide (draft)]]
* [[vpk:v1.0_Ontwerp_Valrisico|Functioneel ontwerp Valrisico v1.0]]
* [[vpk:Vdraft_Ontwerp_Wondzorg|Functioneel ontwerp Wondzorg (draft v0.1)]]

=Referenties=
<references />

vpk:V3.1 FHIR eOverdracht Proeftuin phase 2

2020-05-08T11:17:37Z

Stephan Opdenberg: Changed links to live pages instead of draft pages

{{#customtitle:eOverdracht Proeftuin phase 2 FHIR Implementation Guide}}
{{IssueBox|Work in progress - See [[vpk:V3.1_FHIR_eOverdracht_Proeftuin|official publication]] here.}}
=Introduction=

This page will detail the HL7 requirments for exhcanging the data in the eOverdracht Proeftuin phase 2 as described in [[vpk:V3.1 eOverdracht Proeftuin|the functional design]].Imnplementation of the eOverdracht Proeftuin is spread over 3 different phases. Phase 1 and 3 can be found by navigated the following links in the table listed below.

{| class="wikitable"
! colspan="2" | Phase 1 and Phase 3 of the eOverdracht Proeftuin
|-
| style="text-align: center;" | Phase 1
| style="text-align: center;" | Phase 3
|-
| [[vpk:V3.1_FHIR_eOverdracht_Proeftuin|Proeftuin Phase 1 page]]
| [[vpk:V3.1_FHIR_eOverdracht|eOverdracht FHIR implementation guide]]
|-
|}
* For the implementation of Phase 3, which is the complete message we recommend visitting [[vpk:Draft_FHIR_eOverdracht|eOverdracht FHIR implementation guide]]
Phase two consists of the complete Aanmeldbericht as well as an incomplete Overdrachtsbericht. The Overdrachtsbericht is a subset of 11 HCIM's (complete set used in Aanmeldbericht) and an unstructured PDF containing the remaining data which are not part of the HCIM's.

This implementation guide assumes that the reader is familiar with [https://www.hl7.org/fhir/stu3/ FHIR(STU3)].

==Overarching FHIR principles==
* This implementation guide does not provide information on finding the right XIS, nor does it provide information about security. It is assumed that the sending XIS is able to make a connection with the receiving XIS.
* All FHIR resources used within eOverdracht SHALL conform to the profiles listed in this implementation guide and SHALL include the profile canonical URL in their <code>meta.profile</code> element.

==Package and dependencies==
eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{VersieInfo|V2019.01|package}}].
==Example instances==
Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Composition Composition examples]
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Bundle Bundle examples]

=Use case 1A: Send Overdrachtsbericht volwassenen (PUSH)=
==Introduction==
The Send Overdrachtsbericht scenario is used by the sending XIS to send the relevant data for the patient care to the receiving XIS. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_volwassenen|Opbouw Overdrachtsbericht Volwassenen]]. For the pilot a limited subset is implemented.
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Overdrachtbericht (PUSH)
|style="background-color: white;" rowspan="2"|Send Overdrachtsbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Overdrachtsbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Overdrachtsbericht
|}
==Invocation==
The Send Overdrachtsbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Overdrachtsbericht (4 HCIMs + PDF)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.
==Structure of the Overdrachtsbericht (11 HCIMs + PDF)==
The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

During phase 2, the Overdrachtsbericht is based on 11 HCIMs which expand on the HCIMs from the Aanmeldbericht. The table below lists the FHIR profiles<ref name="nopackage">Please note that the direct links to the various conformance resources below will take you to the latest version, which might not match the package version. At time of writing, there is no way to render the conformance resource as found in the package. This is on the roadmap for Simplifier.</ref> that are applicable for the pilot implementation of the Overdrachtsbericht transaction.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
|
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-overdrachtsbericht-volwassenen-phase-two|eOverdracht Overdrachtsbericht volwassenen phase two}}
| Composition
| -
| -
| Declaration of the Send Overdrachtsbericht volwassenen phase two transaction.
|-
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="3"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nl-core-relatedperson}}
| RelatedPerson
| Contactpersoon
| v3.1(2017NL)
| -
|-
| rowspan="3"|Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2" |Zorgverlener
| rowspan="2" |v3.2(2017NL)
| rowspan="2" | -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| rowspan="3"|Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2" |Zorgverlener
| rowspan="2" |v3.2(2017NL)
| rowspan="2" | -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|zib-ProcedureRequest}}
| ProcedureRequest
| OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-overdrachtsbericht-volwassenen-phase-two|Overdrachtsbericht Volwassenen phase two composition profile}}.
|-
| rowspan="2"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|zib-FeedingTubeSystem}}
| DeviceUseStatement
| SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|zib-Infusion}}
| DeviceUseStatement
| Infuus
| v3.2(2017NL)
| -
|-
| Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|-
| PDF
| [https://www.hl7.org/fhir/binary.html Binary]
| Binary
| -
| -
| Should be used to send unstructured PDF data.
|}

=Use case 3A: Send Aanmeldbericht (PUSH)=
==Introduction==
The Send Aanmeldbericht scenario is used by the sending XIS to send the relevant data for the patient intake to the receiving XIS, and constitutes a subset of the Overdrachtsbericht. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_aanmelding|Opbouw Aanmeldbericht]]. The Phase Two aanmeldbericht implements the complete aanmeldbericht as described in the functional design.
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht(PUSH)
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Aanmeldbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Aanmeldbericht
|}
==Invocation==
The Send Aanmeldbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Aanmeldbericht (4 HCIMs + PDF)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.
==Structure of the Aanmeldbericht phase 2 (complete)==
The Aanmeldbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

During phase 2, the Aanmeldbericht is based 4 HCIMs (Patient, Betaler, Contactpersoon en Zorgaanbieder) and uses a PDF to send the remaining data unstructured. The table below lists the FHIR profiles<ref name="nopackage"/> that are applicable for the pilot implementation of the Aanmeldbericht transaction. All resources SHALL conform to the profiles listed in this table and SHALL include the profile canonical URL in the <code>meta.profile</code> element.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht}}
| Composition
| -
| -
| Declaration of the Send Aanmeldbericht transaction.
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="3"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nl-core-relatedperson}}
| RelatedPerson
| Contactpersoon
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| rowspan="2"| Organization
| rowspan="2"| Zorgaanbieder
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|zib-ProcedureRequest}}
| ProcedureRequest
| OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht profile}}.
|-
| rowspan="2"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|zib-FeedingTubeSystem}}
| DeviceUseStatement
| SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|zib-Infusion}}
| DeviceUseStatement
| Infuus
| v3.2(2017NL)
| -
|-
| Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|}

=FHIR Documents=
Both the Aanmeldbericht and the Overdrachtsbericht are sent as a [https://www.hl7.org/fhir/STU3/documents.html FHIR Document]. A document is a FHIR Bundle that assembles all relevant resources that need to be exchanged, together with a [https://www.hl7.org/fhir/STU3/composition.html Composition resource] that summarizes and references all these resources.

A FHIR document is immutable and considered to be attested by a healthcare professional.
==Creating documents==
To construct a document, a FHIR Composition resource is created that summarizes and references all the resources that need to be exchanged. This Composition resource is then placed together with all referenced resources in a Bundle with <code>Bundle.type</code> set to "document". The Composition resource SHALL be the first entry.

Profiles have been created for both the Composition and the document Bundle resources for each transaction within eOverdracht. All documents SHOULD adhere to these profiles, which are summarized in this implementation guide at the transaction level.
==Sending documents==
The document should be sent as an HTTP POST operation on the target XIS's base:
POST [base] {?_format=[mime-type]}
where the body of the POST request is the document.
==Processing documents==
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS and each <code>Bundle.entry</code> should be treated as a <code>create</code> interaction for the <code>Bundle.entry.resource</code>. When the receiving XIS cannot create a new resource because of incorrect data or business rules, it should perform a rollback of the creation of any previous entries.

On success, the target XIS SHALL respond:
* With the HTTP status code 201 Created.
* With the Location header containing the new logical id and version id of the created resource version.
* With a response body set to a Bundle of type "transaction-response", containing one entry for each entry in the request, in the same order, with the outcome of processing the entry. The sender may use the returned Bundle to track the outcomes of processing the entry, and the identities assigned to the resources by the server.

On failure, the target XIS SHALL respond:
* With an HTTP status code set appropriate to the processing outcome:
** When the resource syntax or data is incorrect or invalid, the status code should be 400 Bad Request.
** When the server rejects the content of the resource because of business rules, the status code should be 422 Unprocessable Entity.
** Additional HTTP status code may be used if more appropriate.
* With a response body set to a FHIR [http://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] resource with detailed error messages describing the reason for the error.

=FHIR CapabilityStatements=
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-servercapabilities-phase-one|CapabilityStatement server}}
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-clientcapabilities-phase-one|CapabilityStatement server}}

=Footnotes=
<references />

vpk:V3.1 FHIR eOverdracht Proeftuin

2020-05-08T11:16:53Z

Stephan Opdenberg: changes links to live pages instead of draft pages

{{#customtitle:eOverdracht Proeftuin phase 1 FHIR Implementation Guide}}
{{IssueBox|Work in progress - See [[vpk:V3.1_FHIR_eOverdracht_Proeftuin|official publication]] here.}}
=Introduction=

This page will detail the HL7 requirments for exhcanging the data in the eOverdracht Proeftuin phase 1 as described in [[vpk:V3.1 eOverdracht Proeftuin|the functional design]].
Imnplementation of the eOverdracht Proeftuin is spread over 3 different phases. Phase 2 and 3 can be found by navigating the following links in the table listed below.
{| class="wikitable"
! colspan="2" | Phase 2 and Phase 3 of the eOverdracht Proeftuin
|-
| style="text-align: center;" | Phase 2
| style="text-align: center;" | Phase 3
|-
| [[vpk:V3.1_FHIR_eOverdracht_Proeftuin_phase_2|Proeftuin Phase 2 ]]
| [[vpk:V3.1_FHIR_eOverdracht|eOverdracht FHIR implementation guide]]
|-
|}
* Phase 3 of the eOverdracht proeftuin consists of the total eOverdracht message, therefore you will be directed to the eOverdracht FHIR implementation guide.

In the first phase of the Proeftuin a simplified version of both the Aanmeldbericht en Overdrachtsbericht are being used. Both messages exist of four HCIMs listed in the table below. The Aanmeldbericht is send to the recieving organisation, which after confirmation of recieving the aanmeldberricht, gets send the Overdrachtbericht.

This implementation guide assumes that the reader is familiar with [https://www.hl7.org/fhir/stu3/ FHIR(STU3)].

==Overarching FHIR principles==
* This implementation guide does not provide information on finding the right XIS, nor does it provide information about security. It is assumed that the sending XIS is able to make a connection with the receiving XIS.
* All FHIR resources used within eOverdracht SHALL conform to the profiles listed in this implementation guide and SHALL include the profile canonical URL in their <code>meta.profile</code> element.

==Package and dependencies==
eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{VersieInfo|V2019.01|package}}].
==Example instances==
Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Composition Composition examples]
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Bundle Bundle examples]

=Use case 1A: Send Overdrachtsbericht volwassenen (PUSH)=
==Introduction==
The Send Overdrachtsbericht scenario is used by the sending XIS to send the relevant data for the patient care to the receiving XIS. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_volwassenen|Opbouw Overdrachtsbericht Volwassenen]]. For the pilot a limited subset is implemented.
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Overdrachtbericht (PUSH)
|style="background-color: white;" rowspan="2"|Send Overdrachtsbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Overdrachtsbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Overdrachtsbericht
|}
==Invocation==
The Send Overdrachtsbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Overdrachtsbericht (4 HCIMs + PDF)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.
==Structure of the Overdrachtsbericht (4 HCIMs + PDF)==
The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

During phase 1, the Overdrachtsbericht is based on the same 4 HCIMs as the Aanmeldbericht (Patient, Betaler, Contactpersoon en Zorgaanbieder). The table below lists the FHIR profiles<ref name="nopackage">Please note that the direct links to the various conformance resources below will take you to the latest version, which might not match the package version. At time of writing, there is no way to render the conformance resource as found in the package. This is on the roadmap for Simplifier.</ref> that are applicable for the pilot implementation of the Overdrachtsbericht transaction.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | Remarks
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-Overdrachtsbericht-volwassenen-phase-one|Overdrachtsbericht phase 1}}
| Composition
| -
| -
| The Composition resource used to assemble the document
|-
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| ''extension''
| -
| -
| extension in the Composition resource
|-
| rowspan="2"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| rowspan="3"|Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2" |Zorgverlener
| rowspan="2" |v3.2(2017NL)
| rowspan="2" | -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| rowspan="3"|Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2" |Zorgverlener
| rowspan="2" |v3.2(2017NL)
| rowspan="2" | -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| PDF
| [https://www.hl7.org/fhir/binary.html Binary]
| Binary
| -
| -
| Used to send unstructured PDF data
|}

=Use case 3A: Send Aanmeldbericht (PUSH)=
==Introduction==
The Send Aanmeldbericht scenario is used by the sending XIS to send the relevant data for the patient intake to the receiving XIS, and constitutes a subset of the Overdrachtsbericht. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_aanmelding|Opbouw Aanmeldbericht]]. For the pilot a limited subset is implemented.
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht(PUSH)
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Aanmeldbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Aanmeldbericht
|}
==Invocation==
The Send Aanmeldbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Aanmeldbericht (4 HCIMs + PDF)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.
==Structure of the Aanmeldbericht (4 HCIMs + PDF)==
The Aanmeldbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

During phase 1, the Aanmeldbericht is based 4 HCIMs (Patient, Betaler, Contactpersoon en Zorgaanbieder) and uses a PDF to send the remaining data unstructured. The table below lists the FHIR profiles<ref name="nopackage"/> that are applicable for the pilot implementation of the Aanmeldbericht transaction. All resources SHALL conform to the profiles listed in this table and SHALL include the profile canonical URL in the <code>meta.profile</code> element.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | Remarks
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht-phase-one|Aanmeldbericht phase 1}}
| Composition
| -
| -
| The Composition resource used to assemble the document
|-
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| ''extension''
| -
| -
| extension in the Composition resource
|-
| rowspan="2"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
|-
| PDF
| [https://www.hl7.org/fhir/binary.html Binary]
| Binary
| -
| -
| Used to send unstructured PDF data
|}
=FHIR Documents=
Both the Aanmeldbericht and the Overdrachtsbericht are sent as a [https://www.hl7.org/fhir/STU3/documents.html FHIR Document]. A document is a FHIR Bundle that assembles all relevant resources that need to be exchanged, together with a [https://www.hl7.org/fhir/STU3/composition.html Composition resource] that summarizes and references all these resources.

A FHIR document is immutable and considered to be attested by a healthcare professional.
==Creating documents==
To construct a document, a FHIR Composition resource is created that summarizes and references all the resources that need to be exchanged. This Composition resource is then placed together with all referenced resources in a Bundle with <code>Bundle.type</code> set to "document". The Composition resource SHALL be the first entry.

Profiles have been created for both the Composition and the document Bundle resources for each transaction within eOverdracht. All documents SHOULD adhere to these profiles, which are summarized in this implementation guide at the transaction level.
==Sending documents==
The document should be sent as an HTTP POST operation on the target XIS's base:
POST [base] {?_format=[mime-type]}
where the body of the POST request is the document.
==Processing documents==
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS and each <code>Bundle.entry</code> should be treated as a <code>create</code> interaction for the <code>Bundle.entry.resource</code>. When the receiving XIS cannot create a new resource because of incorrect data or business rules, it should perform a rollback of the creation of any previous entries.

On success, the target XIS SHALL respond:
* With the HTTP status code 201 Created.
* With the Location header containing the new logical id and version id of the created resource version.
* With a response body set to a Bundle of type "transaction-response", containing one entry for each entry in the request, in the same order, with the outcome of processing the entry. The sender may use the returned Bundle to track the outcomes of processing the entry, and the identities assigned to the resources by the server.

On failure, the target XIS SHALL respond:
* With an HTTP status code set appropriate to the processing outcome:
** When the resource syntax or data is incorrect or invalid, the status code should be 400 Bad Request.
** When the server rejects the content of the resource because of business rules, the status code should be 422 Unprocessable Entity.
** Additional HTTP status code may be used if more appropriate.
* With a response body set to a FHIR [http://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] resource with detailed error messages describing the reason for the error.

=FHIR CapabilityStatements=
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-servercapabilities-phase-one|CapabilityStatement server}}
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-clientcapabilities-phase-one|CapabilityStatement server}}

=Footnotes=
<references />

vpk:V3.1 FHIR eOverdracht Proeftuin phase 2

2020-05-08T11:08:26Z

Stephan Opdenberg: Added Phase 2 page of eOverdracht proeftuin

{{#customtitle:eOverdracht Proeftuin phase 2 FHIR Implementation Guide}}
{{IssueBox|Work in progress - See [[vpk:V3.1_FHIR_eOverdracht_Proeftuin|official publication]] here.}}
=Introduction=

This page will detail the HL7 requirments for exhcanging the data in the eOverdracht Proeftuin phase 2 as described in [[vpk:V3.1 eOverdracht Proeftuin|the functional design]].Imnplementation of the eOverdracht Proeftuin is spread over 3 different phases. Phase 1 and 3 can be found by navigated the following links in the table listed below.

{| class="wikitable"
! colspan="2" | Phase 1 and Phase 3 of the eOverdracht Proeftuin
|-
| style="text-align: center;" | Phase 1
| style="text-align: center;" | Phase 3
|-
| [[vpk:Vdraft_FHIR_eOverdracht_Proeftuin|Proeftuin Phase 1 page]]
| [[vpk:Draft_FHIR_eOverdracht|eOverdracht FHIR implementation guide]]
|-
|}
* For the implementation of Phase 3, which is the complete message we recommend visitting [[vpk:Draft_FHIR_eOverdracht|eOverdracht FHIR implementation guide]]
Phase two consists of the complete Aanmeldbericht as well as an incomplete Overdrachtsbericht. The Overdrachtsbericht is a subset of 11 HCIM's (complete set used in Aanmeldbericht) and an unstructured PDF containing the remaining data which are not part of the HCIM's.

This implementation guide assumes that the reader is familiar with [https://www.hl7.org/fhir/stu3/ FHIR(STU3)].

==Overarching FHIR principles==
* This implementation guide does not provide information on finding the right XIS, nor does it provide information about security. It is assumed that the sending XIS is able to make a connection with the receiving XIS.
* All FHIR resources used within eOverdracht SHALL conform to the profiles listed in this implementation guide and SHALL include the profile canonical URL in their <code>meta.profile</code> element.

==Package and dependencies==
eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{VersieInfo|V2019.01|package}}].
==Example instances==
Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Composition Composition examples]
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Bundle Bundle examples]

=Use case 1A: Send Overdrachtsbericht volwassenen (PUSH)=
==Introduction==
The Send Overdrachtsbericht scenario is used by the sending XIS to send the relevant data for the patient care to the receiving XIS. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_volwassenen|Opbouw Overdrachtsbericht Volwassenen]]. For the pilot a limited subset is implemented.
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Overdrachtbericht (PUSH)
|style="background-color: white;" rowspan="2"|Send Overdrachtsbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Overdrachtsbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Overdrachtsbericht
|}
==Invocation==
The Send Overdrachtsbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Overdrachtsbericht (4 HCIMs + PDF)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.
==Structure of the Overdrachtsbericht (11 HCIMs + PDF)==
The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

During phase 2, the Overdrachtsbericht is based on 11 HCIMs which expand on the HCIMs from the Aanmeldbericht. The table below lists the FHIR profiles<ref name="nopackage">Please note that the direct links to the various conformance resources below will take you to the latest version, which might not match the package version. At time of writing, there is no way to render the conformance resource as found in the package. This is on the roadmap for Simplifier.</ref> that are applicable for the pilot implementation of the Overdrachtsbericht transaction.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
|
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-overdrachtsbericht-volwassenen-phase-two|eOverdracht Overdrachtsbericht volwassenen phase two}}
| Composition
| -
| -
| Declaration of the Send Overdrachtsbericht volwassenen phase two transaction.
|-
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="3"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nl-core-relatedperson}}
| RelatedPerson
| Contactpersoon
| v3.1(2017NL)
| -
|-
| rowspan="3"|Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2" |Zorgverlener
| rowspan="2" |v3.2(2017NL)
| rowspan="2" | -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| rowspan="3"|Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2" |Zorgverlener
| rowspan="2" |v3.2(2017NL)
| rowspan="2" | -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|zib-ProcedureRequest}}
| ProcedureRequest
| OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-overdrachtsbericht-volwassenen-phase-two|Overdrachtsbericht Volwassenen phase two composition profile}}.
|-
| rowspan="2"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|zib-FeedingTubeSystem}}
| DeviceUseStatement
| SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|zib-Infusion}}
| DeviceUseStatement
| Infuus
| v3.2(2017NL)
| -
|-
| Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|-
| PDF
| [https://www.hl7.org/fhir/binary.html Binary]
| Binary
| -
| -
| Should be used to send unstructured PDF data.
|}

=Use case 3A: Send Aanmeldbericht (PUSH)=
==Introduction==
The Send Aanmeldbericht scenario is used by the sending XIS to send the relevant data for the patient intake to the receiving XIS, and constitutes a subset of the Overdrachtsbericht. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_aanmelding|Opbouw Aanmeldbericht]]. The Phase Two aanmeldbericht implements the complete aanmeldbericht as described in the functional design.
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht(PUSH)
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Aanmeldbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Aanmeldbericht
|}
==Invocation==
The Send Aanmeldbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Aanmeldbericht (4 HCIMs + PDF)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.
==Structure of the Aanmeldbericht phase 2 (complete)==
The Aanmeldbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

During phase 2, the Aanmeldbericht is based 4 HCIMs (Patient, Betaler, Contactpersoon en Zorgaanbieder) and uses a PDF to send the remaining data unstructured. The table below lists the FHIR profiles<ref name="nopackage"/> that are applicable for the pilot implementation of the Aanmeldbericht transaction. All resources SHALL conform to the profiles listed in this table and SHALL include the profile canonical URL in the <code>meta.profile</code> element.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:50px" | Remarks
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht}}
| Composition
| -
| -
| Declaration of the Send Aanmeldbericht transaction.
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| -
| -
| -
| DateTime extension used in eOverdracht composition profiles
|-
| rowspan="3"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson|nl-core-relatedperson}}
| RelatedPerson
| Contactpersoon
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| rowspan="2"| Organization
| rowspan="2"| Zorgaanbieder
| rowspan="2"| v3.1.1(2017NL)
| rowspan="2"| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
|-
| Medische diagnose
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
|-
| Voorgeschiedenis
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL
| -
|-
| Let op
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert|zib-Alert}}
| Flag
| Alert
| v3.2(2017NL)
| -
|-
| Vrijheidsbeperking
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FreedomRestrictingMeasures|zib-FreedomRestrictingMeasures}}
| Procedure
| VrijheidsBeperkendeMaatregelen
| v3.1(2017NL)
| -
|-
| Actuele patiëntenproblemen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem|zib-Problem}}
| Condition
| Probleem
| v4.1(2017NL)
| -
|-
| Afspraken patiënt
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest|zib-ProcedureRequest}}
| ProcedureRequest
| OverdrachtGeplandeZorgActiviteit
| v3.1(2017NL)
| -
|-
| Wensen en behoeften patiënt en/of naasten
| -
| -
| -
| -
| Declared as a text section. See {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht|eOverdracht aanmeldbericht profile}}.
|-
| rowspan="2"| Voeding/vocht
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FeedingTubeSystem|zib-FeedingTubeSystem}}
| DeviceUseStatement
| SondeSysteem
| v3.2(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Infusion|zib-Infusion}}
| DeviceUseStatement
| Infuus
| v3.2(2017NL)
| -
|-
| Uitscheiding
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Stoma|zib-Stoma}}
| Observation
| Stoma
| v3.2(2017NL)
| -
|}

=FHIR Documents=
Both the Aanmeldbericht and the Overdrachtsbericht are sent as a [https://www.hl7.org/fhir/STU3/documents.html FHIR Document]. A document is a FHIR Bundle that assembles all relevant resources that need to be exchanged, together with a [https://www.hl7.org/fhir/STU3/composition.html Composition resource] that summarizes and references all these resources.

A FHIR document is immutable and considered to be attested by a healthcare professional.
==Creating documents==
To construct a document, a FHIR Composition resource is created that summarizes and references all the resources that need to be exchanged. This Composition resource is then placed together with all referenced resources in a Bundle with <code>Bundle.type</code> set to "document". The Composition resource SHALL be the first entry.

Profiles have been created for both the Composition and the document Bundle resources for each transaction within eOverdracht. All documents SHOULD adhere to these profiles, which are summarized in this implementation guide at the transaction level.
==Sending documents==
The document should be sent as an HTTP POST operation on the target XIS's base:
POST [base] {?_format=[mime-type]}
where the body of the POST request is the document.
==Processing documents==
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS and each <code>Bundle.entry</code> should be treated as a <code>create</code> interaction for the <code>Bundle.entry.resource</code>. When the receiving XIS cannot create a new resource because of incorrect data or business rules, it should perform a rollback of the creation of any previous entries.

On success, the target XIS SHALL respond:
* With the HTTP status code 201 Created.
* With the Location header containing the new logical id and version id of the created resource version.
* With a response body set to a Bundle of type "transaction-response", containing one entry for each entry in the request, in the same order, with the outcome of processing the entry. The sender may use the returned Bundle to track the outcomes of processing the entry, and the identities assigned to the resources by the server.

On failure, the target XIS SHALL respond:
* With an HTTP status code set appropriate to the processing outcome:
** When the resource syntax or data is incorrect or invalid, the status code should be 400 Bad Request.
** When the server rejects the content of the resource because of business rules, the status code should be 422 Unprocessable Entity.
** Additional HTTP status code may be used if more appropriate.
* With a response body set to a FHIR [http://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] resource with detailed error messages describing the reason for the error.

=FHIR CapabilityStatements=
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-servercapabilities-phase-one|CapabilityStatement server}}
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-clientcapabilities-phase-one|CapabilityStatement server}}

=Footnotes=
<references />

vpk:V3.1 FHIR eOverdracht Proeftuin

2020-05-08T11:07:19Z

Stephan Opdenberg: Changed the format of the previous page, and updated information and navigation to other pages

{{#customtitle:eOverdracht Proeftuin phase 1 FHIR Implementation Guide}}
{{IssueBox|Work in progress - See [[vpk:V3.1_FHIR_eOverdracht_Proeftuin|official publication]] here.}}
=Introduction=

This page will detail the HL7 requirments for exhcanging the data in the eOverdracht Proeftuin phase 1 as described in [[vpk:V3.1 eOverdracht Proeftuin|the functional design]].
Imnplementation of the eOverdracht Proeftuin is spread over 3 different phases. Phase 2 and 3 can be found by navigating the following links in the table listed below.
{| class="wikitable"
! colspan="2" | Phase 2 and Phase 3 of the eOverdracht Proeftuin
|-
| style="text-align: center;" | Phase 2
| style="text-align: center;" | Phase 3
|-
| [[vpk:Vdraft_FHIR_eOverdracht_Proeftuin_phase_2|Proeftuin Phase 2 ]]
| [[vpk:Draft_FHIR_eOverdracht|eOverdracht FHIR implementation guide]]
|-
|}
* Phase 3 of the eOverdracht proeftuin consists of the total eOverdracht message, therefore you will be directed to the eOverdracht FHIR implementation guide.

In the first phase of the Proeftuin a simplified version of both the Aanmeldbericht en Overdrachtsbericht are being used. Both messages exist of four HCIMs listed in the table below. The Aanmeldbericht is send to the recieving organisation, which after confirmation of recieving the aanmeldberricht, gets send the Overdrachtbericht.

This implementation guide assumes that the reader is familiar with [https://www.hl7.org/fhir/stu3/ FHIR(STU3)].

==Overarching FHIR principles==
* This implementation guide does not provide information on finding the right XIS, nor does it provide information about security. It is assumed that the sending XIS is able to make a connection with the receiving XIS.
* All FHIR resources used within eOverdracht SHALL conform to the profiles listed in this implementation guide and SHALL include the profile canonical URL in their <code>meta.profile</code> element.

==Package and dependencies==
eOverdracht uses the FHIR Packaging mechanism to conveniently bundle all examples, profiles and other conformance resources you need into a single download. The eOverdracht package has a dependency on the [https://simplifier.net/NictizSTU3-Zib2017/~packages Nictiz Zib2017 package {{VersieInfo|V2019.01|package}}].
==Example instances==
Example instances of the FHIR messages can be found on [https://simplifier.net/nictiz-stu3-eoverdracht Simplifier]:
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Composition Composition examples]
* [https://simplifier.net/nictiz-stu3-eoverdracht/~resources?category=Example&exampletype=Bundle Bundle examples]

=Use case 1A: Send Overdrachtsbericht volwassenen (PUSH)=
==Introduction==
The Send Overdrachtsbericht scenario is used by the sending XIS to send the relevant data for the patient care to the receiving XIS. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_volwassenen|Opbouw Overdrachtsbericht Volwassenen]]. For the pilot a limited subset is implemented.
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Overdrachtbericht (PUSH)
|style="background-color: white;" rowspan="2"|Send Overdrachtsbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Overdrachtsbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Overdrachtsbericht
|}
==Invocation==
The Send Overdrachtsbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Overdrachtsbericht (4 HCIMs + PDF)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.
==Structure of the Overdrachtsbericht (4 HCIMs + PDF)==
The Overdrachtsbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

During phase 1, the Overdrachtsbericht is based on the same 4 HCIMs as the Aanmeldbericht (Patient, Betaler, Contactpersoon en Zorgaanbieder). The table below lists the FHIR profiles<ref name="nopackage">Please note that the direct links to the various conformance resources below will take you to the latest version, which might not match the package version. At time of writing, there is no way to render the conformance resource as found in the package. This is on the roadmap for Simplifier.</ref> that are applicable for the pilot implementation of the Overdrachtsbericht transaction.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | Remarks
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-Overdrachtsbericht-volwassenen-phase-one|Overdrachtsbericht phase 1}}
| Composition
| -
| -
| The Composition resource used to assemble the document
|-
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| ''extension''
| -
| -
| extension in the Composition resource
|-
| rowspan="2"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| rowspan="3"|Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2" |Zorgverlener
| rowspan="2" |v3.2(2017NL)
| rowspan="2" | -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| rowspan="3"|Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner|nl-core-practitioner}}
| Practitioner
| rowspan="2" |Zorgverlener
| rowspan="2" |v3.2(2017NL)
| rowspan="2" | -
|-
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole|nl-core-practitionerrole}}
| PractitionerRole
|-
| PDF
| [https://www.hl7.org/fhir/binary.html Binary]
| Binary
| -
| -
| Used to send unstructured PDF data
|}

=Use case 3A: Send Aanmeldbericht (PUSH)=
==Introduction==
The Send Aanmeldbericht scenario is used by the sending XIS to send the relevant data for the patient intake to the receiving XIS, and constitutes a subset of the Overdrachtsbericht. The structure of the eventual scenario is described in the functional design and additionally in [[vpk:V3.1_Opbouw_eOverdracht_aanmelding|Opbouw Aanmeldbericht]]. For the pilot a limited subset is implemented.
==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht(PUSH)
|style="background-color: white;" rowspan="2"|Send Aanmeldbericht
|style="background-color: white;"|Healthcare professional at organization A (using a XIS)
|style="background-color: white;"|Sends Aanmeldbericht
|-
|style="background-color: white;"|Healthcare professional at organization B (using a XIS)
|style="background-color: white;"|Receives Aanmeldbericht
|}
==Invocation==
The Send Aanmeldbericht transaction is an HTTP POST method on the target XIS's base, where the body of the POST request is a FHIR document according to [[#Structure of the Aanmeldbericht (4 HCIMs + PDF)]]. See [[#Sending documents]] for more information.
===Trigger events===
This transaction is invoked when the sending XIS needs to send the Overdrachtsbericht to the receiving XIS.
===Expected response===
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS. See [[#Processing documents]] for more information.
==Structure of the Aanmeldbericht (4 HCIMs + PDF)==
The Aanmeldbericht consists of multiple FHIR resources, which are assembled into a FHIR document. See [[#Creating documents]] for information on how to assemble this document.

During phase 1, the Aanmeldbericht is based 4 HCIMs (Patient, Betaler, Contactpersoon en Zorgaanbieder) and uses a PDF to send the remaining data unstructured. The table below lists the FHIR profiles<ref name="nopackage"/> that are applicable for the pilot implementation of the Aanmeldbericht transaction. All resources SHALL conform to the profiles listed in this table and SHALL include the profile canonical URL in the <code>meta.profile</code> element.

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | FHIR profile
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | FHIR resource
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | HCIM name
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | HCIM version
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left;" | Remarks
|-
| -
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-aanmeldbericht-phase-one|Aanmeldbericht phase 1}}
| Composition
| -
| -
| The Composition resource used to assemble the document
|-
|-
| Datum overplaatsing
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eOverdracht-TransferDate|eOverdracht-TransferDate}}
| ''extension''
| -
| -
| extension in the Composition resource
|-
| rowspan="2"|Persoonsgegevens
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nl-core-patient}}
| Patient
| Patient
| v3.1(2017NL)
| -
|-
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer|zib-Payer}}
| Coverage
| Betaler
| v3.1(2017NL)
| -
|-
| Sturende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
| -
|-
| Ontvangende organisatie
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization|nl-core-organization}}
| Organization
| Zorgaanbieder
| v3.1.1(2017NL)
|-
| PDF
| [https://www.hl7.org/fhir/binary.html Binary]
| Binary
| -
| -
| Used to send unstructured PDF data
|}
=FHIR Documents=
Both the Aanmeldbericht and the Overdrachtsbericht are sent as a [https://www.hl7.org/fhir/STU3/documents.html FHIR Document]. A document is a FHIR Bundle that assembles all relevant resources that need to be exchanged, together with a [https://www.hl7.org/fhir/STU3/composition.html Composition resource] that summarizes and references all these resources.

A FHIR document is immutable and considered to be attested by a healthcare professional.
==Creating documents==
To construct a document, a FHIR Composition resource is created that summarizes and references all the resources that need to be exchanged. This Composition resource is then placed together with all referenced resources in a Bundle with <code>Bundle.type</code> set to "document". The Composition resource SHALL be the first entry.

Profiles have been created for both the Composition and the document Bundle resources for each transaction within eOverdracht. All documents SHOULD adhere to these profiles, which are summarized in this implementation guide at the transaction level.
==Sending documents==
The document should be sent as an HTTP POST operation on the target XIS's base:
POST [base] {?_format=[mime-type]}
where the body of the POST request is the document.
==Processing documents==
The document Bundle should be processed as a [http://hl7.org/fhir/STU3/http.html#transaction transaction] by the receiving XIS and each <code>Bundle.entry</code> should be treated as a <code>create</code> interaction for the <code>Bundle.entry.resource</code>. When the receiving XIS cannot create a new resource because of incorrect data or business rules, it should perform a rollback of the creation of any previous entries.

On success, the target XIS SHALL respond:
* With the HTTP status code 201 Created.
* With the Location header containing the new logical id and version id of the created resource version.
* With a response body set to a Bundle of type "transaction-response", containing one entry for each entry in the request, in the same order, with the outcome of processing the entry. The sender may use the returned Bundle to track the outcomes of processing the entry, and the identities assigned to the resources by the server.

On failure, the target XIS SHALL respond:
* With an HTTP status code set appropriate to the processing outcome:
** When the resource syntax or data is incorrect or invalid, the status code should be 400 Bad Request.
** When the server rejects the content of the resource because of business rules, the status code should be 422 Unprocessable Entity.
** Additional HTTP status code may be used if more appropriate.
* With a response body set to a FHIR [http://hl7.org/fhir/STU3/operationoutcome.html OperationOutcome] resource with detailed error messages describing the reason for the error.

=FHIR CapabilityStatements=
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-servercapabilities-phase-one|CapabilityStatement server}}
* {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-clientcapabilities-phase-one|CapabilityStatement server}}

=Footnotes=
<references />

MedMij:V2019.01 FHIR AllergyIntolerance

2020-05-07T12:48:55Z

Stephan Opdenberg: changed color of header

{{#customtitle:MedMij FHIR Implementation Guide AllergyIntolerance {{VersieInfo|V2019.01|AllergieIntolerantie}}}}
{{MedMij:V2019.01_Issuebox_FHIR_IG}}

[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:Allergie.png|link=|87px |links||AllergyIntolerance]]
<imagemap>Bestand:Leeswijzer-technisch-banner 03 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_OntwerpAllergieIntolerantie|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_IG|Technisch]]
desc none
</imagemap>

__TOC__

=Introduction=
[[Bestand:Functioneel-02.png|link=MedMij:V2019.01_Ontwerpen |100px|rechts|Functional design|Go to functional design]]

This page describes a patient's use case, in a personal health record (PHR) context, for exchanging allergy and intolerance data. Functional specification of this use case is described in the [[MedMij:V2019.01_Ontwerpen| functional design wiki pages]]. The technical specification is described here. HL7 FHIR STU3 is used for this purpose.

=Actors involved=
{| class="wikitable"
! colspan="2" style="text-align:left;" | Persons
! colspan="2" style="text-align:left;" | Systems
! colspan="2" style="text-align:left;" | FHIR Capability Statements
|-
! style="text-align:left;" |Name
! style="text-align:left;" |Description
! style="text-align:left;" |Name
! style="text-align:left;" |Description
! style="text-align:left;" |Name
! style="text-align:left;" |Description
|-
| Patient
| The user of a personal healthcare enviorment.
| PHR
| Personal health record
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/allergyintolerance-clientcapabilities|CapabilityStatement: Client}}
| AllergyIntolerance client requirements
|-
| Healthcare professional
| The user of a XIS
| XIS
| Healthcare information system
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/allergyintolerance-servercapabilities|CapabilityStatement: Server}}
| AllergyIntolerance server requirements
|}

=Use case: Retrieve AllergyIntolerance information=
{{FHIR-IG-Afsprakenstelsel-Note}}

==Introduction==
The retrieve AllergyIntolerance transaction is used by the PHR to retrieve allergy and intolerance information from the XIS.

==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;vertical-align:top;" rowspan="3"|Retrieve AllergyIntolerance(PULL)
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance request
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
|style="background-color: white;vertical-align:top;"|Request allergy and intolerance information from the XIS
|-
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance response
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
|style="background-color: white;vertical-align:top;"|Serves allergy and intolerance information to the PHR
|}

==Invocations==
===PHR: request message===
The request message represents an HTTP GET query from the PHR to the XIS.

====Trigger Events====
When the patient(PHR) wants to obtain allergy and intolerance information, it issues a retrieve AllergyIntolerance request message.

====Message Semantics====
The PHR executes an HTTP GET conform to the FHIR [http://hl7.org/fhir/http.html RESTfull] and [http://hl7.org/fhir/search.html search] specification against the XIS's AllergyIntolerance endpoint. This search query has the following format.

<pre>
GET [base]/AllergyIntolerance
</pre>

=====Search Parameters=====
No query parameters are defined for this use case. The PHR searches on all AllergyIntolerance resources available for the patient using a HTTP GET on the AllergyIntolerance endpoint without parameters.

=====Expected Actions=====
The XIS shall process the query to discover AllergyIntolerance resources that match the patient in the context.

===XIS: response message===
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the allergy and intolerance information.

====Trigger Events====
The XIS completed processing of the Retrieve AllergyIntolerance request message.

====Message Semantics====
Based on the query results, the XIS will either return an error or success. When the XIS needs to report an error, it SHALL use HTTP error response codes and SHOULD include a FHIR OperationOutcome resource with more details on the failure. If the request message is processed successfully, whether or not any AllergyIntolerance resources are found, the HTTP status code SHALL be 200.

The response message shall be a Bundle resource of type "searchset" containing zero or more FHIR resources as entries. If the XIS is sending warnings, the Bundle resource SHALL also contain a FHIR OperationOutcome resource that contains those warnings. The FHIR specification describes the relevant sections:
*[http://hl7.org/fhir/STU3/http.html RESTful API framework]
*[http://hl7.org/fhir/STU3/search.html#errors Search errors]
*[http://hl7.org/fhir/STU3/bundle.html Bundle resource]
*[http://hl7.org/fhir/operationoutcome.html OperationOutcome resource]

=====Message resource content=====
The returned data to the PHR should conform to the zib AllergyIntolerance profile. The table below shows the relevant zibs and their profiles. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

{{NoteBoxPackage|https://simplifier.net/NictizSTU3-Zib2017/~packages|1.3.x|MedMij:V2019.01_FHIR_IG}}

{| class="wikitable"
|-style="background-color: #1F497D; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px"
|Zib name NL||Zib name EN||FHIR Resource||URL profile
|-style="vertical-align:top; background-color: #E3E3E3;
|-
| Patient
| #Zib Patient|Patient
| Patient
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient}}
|-
| AllergieIntolerantie
| AllergyIntolerance
| AllergyIntolerance
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance}}
|-
| rowspan="2" | Zorgverlener
| rowspan="2" | HealthProfessional
| Practitioner
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner}}
|-
| PractitionerRole
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole}}
|-
| Zorgaanbieder
| HealthcareProvider
| Organization
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization}}
|-
| Contactpersoon
| ContactPerson
| Patient.contact
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson}}
|}
{{Sjabloon:Voorbeelden}}

====Expected Actions====
The PHR processes the results according to application-defined rules. The PHR should be robust as the response may contain AllergyIntolerance information resources as mentioned in the former section.

==Interactions, operations, search parameters==
===Interactions===
The following logical interactions are needed for the retrieve AllergyIntolerance information transaction:
* [http://hl7.org/fhir/STU3/http.html#search Search]

===Operations===
No operations are defined or needed for this transaction.

===Search parameters===
No search parameters are defined or needed for this transaction.

=Use case: Retrieve AllergyIntolerance612ToFHIRConversion =
{{FHIR-IG-Afsprakenstelsel-Note}}

==Introduction==
A PHR uses the retrieve AllergyIntolerance612ToFHIRConversion transaction to retrieve "6.12-based" allergy and intolerance information from a XIS. This information is based on a conversion from the [https://www.nictiz.nl/standaardisatie/informatiestandaarden/medicatieveiligheid/ 6.12 information standard]. The XIS converts the requested information by a PHR to FHIR-resources.

The 6.12 AllergyIntolerance information is originally exchanged in HL7v3-messaging format. For interested readers the HL7v3-specifications can be found in the [http://decor.nictiz.nl/medicatieproces/mp-html-20181220T121121/tmp-2.16.840.1.113883.2.4.3.11.60.20.77.10.12-2013-08-19T000000.html 6.12 template for 'potential contraindications'].

However, please note that it is not necessary for a PHR to have knowledge of the HL7v3-format to implement this use case.

==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;vertical-align:top;" rowspan="3"|Retrieve AllergyIntolerance612ToFHIRConversion (PULL)
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance612ToFHIRConversion request
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
|style="background-color: white;vertical-align:top;"|Request allergy and intolerance information from the XIS
|-
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance612ToFHIRConversion response
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
|style="background-color: white;vertical-align:top;"|Serves allergy and intolerance information to the PHR
|}

==Invocations==
===PHR: request message===
The request message represents an HTTP GET query from the PHR to the XIS.

====Trigger Events====
When the patient(PHR) wants to obtain allergy and intolerance information, it issues a retrieve AllergyIntolerance612ToFHIRConversion request message.

====Message Semantics====
The PHR executes an HTTP GET conform to the FHIR [http://hl7.org/fhir/http.html RESTfull] and [http://hl7.org/fhir/search.html search] specification against the XIS's AllergyIntolerance612ToFHIRConversion endpoint. This search query has the following format.

<pre>
GET [base]/AllergyIntolerance
</pre>

=====Search Parameters=====
No query parameters are defined for this use case. The PHR searches on all AllergyIntolerance resources available for the patient using a HTTP GET on the AllergyIntolerance endpoint without parameters.

=====Expected Actions=====
The XIS shall process the query to discover AllergyIntolerance resources that are part of the 6.12 information standard and match the patient in the context.

===XIS: response message===
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the appropriate allergy and intolerance information.

====Trigger Events====
The XIS completed processing of the Retrieve AllergyIntolerance request message.

====Message Semantics====
Based on the query results, the XIS will either return an error or success. When the XIS needs to report an error, it SHALL use HTTP error response codes and SHOULD include a FHIR OperationOutcome resource with more details on the failure. If the request message is processed successfully, whether or not any AllergyIntolerance resources are found, the HTTP status code SHALL be 200.

The response message shall be a Bundle resource of type "searchset" containing zero or more FHIR resources as entries. If the XIS is sending warnings, the Bundle resource SHALL also contain a FHIR OperationOutcome resource that contains those warnings. The FHIR specification describes the relevant sections:
*[http://hl7.org/fhir/STU3/http.html RESTful API framework]
*[http://hl7.org/fhir/STU3/search.html#errors Search errors]
*[http://hl7.org/fhir/STU3/bundle.html Bundle resource]
*[http://hl7.org/fhir/operationoutcome.html OperationOutcome resource]

=====Message resource content=====
The returned data to the PHR should conform to the zib AllergyIntolerance profile. The table below shows the relevant zibs and their profiles. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

{{NoteBoxPackage|https://simplifier.net/NictizSTU3-Zib2017/~packages|1.3.x|MedMij:V2019.01_FHIR_IG}}

{| class="wikitable"
|-style="background-color: #1F497D; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px"
|Zib name NL||Zib name EN||FHIR Resource||URL profile
|-style="vertical-align:top; background-color: #E3E3E3;
|-
| Patient
| #Zib Patient|Patient
| Patient
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient}}
|-
| AllergieIntolerantie
| AllergyIntolerance
| AllergyIntolerance
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp612-AllergyIntoleranceToFHIRConversion}}
|-
| rowspan="2" | Zorgverlener
| rowspan="2" | HealthProfessional
| Practitioner
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner}}
|-
| PractitionerRole
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole}}
|-
| Zorgaanbieder
| HealthcareProvider
| Organization
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization}}
|-
| Contactpersoon
| ContactPerson
| Patient.contact
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson}}
|}
{{Sjabloon:Voorbeelden}}

====Expected Actions====
The PHR processes the results according to application-defined rules. The PHR should be robust as the response may contain AllergyIntolerance information resources as mentioned in the former section.

==Interactions, operations, search parameters==
===Interactions===
The following logical interactions are needed for the retrieve AllergyIntolerance612ToFHIRConversion transaction:
* [http://hl7.org/fhir/STU3/http.html#search Search]

===Operations===
No operations are defined or needed for this transaction.

===Search parameters===
No search parameters are defined or needed for this transaction.

=Terminology, NamingSystems, Mappings=

===Terminology===
Relevant ValueSets can be found through the ValueSet bindings in the listed StructureDefinitions. All ValueSets can be found here [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ValueSet here] and can be downloaded as a .zip in XML or JSON format.

===NamingSystems===
Relevant NamingSystems can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=NamingSystem here].

===Mappings===
A FHIR ConceptMap resource is provided when a FHIR value set is used instead of a HCIM value set. A ConceptMap maps the values between the two value sets. These ConceptMaps can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap here].

An explanation about mappings can be found at [[MedMij:V2019.01_FHIR_IG#Mapping_of_coded_concepts|Mapping of coded concepts]].

=Annex: Document history=
==Release notes==
Release notes can be found on the [[MedMij:V2019.01_OntwerpAllergieIntolerantie#Release_notes|functional design page]].

==History==
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Date
!style="text-align:left;"|Description
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Deprecated invalid package 1.3.8, replaced with package 1.3.9
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Deprecated invalid package 1.3.7, replaced with package 1.3.8
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Changes for 2019.01 April 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - March 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Changes for 2019.01 March 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - January 2020
| style="background-color: white;"| 27-01-2020
| style="background-color: white;"|
* Changes for 2019.01 January 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - November
| style="background-color: white;"| 10-12-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - November
| style="background-color: white;"| 28-11-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - October
| style="background-color: white;"| 30-10-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white; | 2019.01
| style="background-color: white; | 18-10-2019
| style="background-color: white;"|
* Version 2.0.0 of this standaard, add use case.
* See release notes for changes.
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"|
*Publication of changes in version 2019.01, conform release notes.
*Moved release notes to the functional design page. 
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 12-11-2018
| style="background-color: white;"|
* Added section about Terminology, NamingSystems, Mappings.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 15-10-2018
| style="background-color: white;"|
* Added version in title, and document history.
|}

[[categorie:MedMij FHIR Use Cases]]

MedMij:Vprepub-2019.01 FHIR AllergyIntolerance

2020-05-07T12:48:55Z

Stephan Opdenberg: changed color of header

MedMij:V2019.01 FHIR AllergyIntolerance

2020-05-07T12:48:37Z

Stephan Opdenberg: changed color of header

{{#customtitle:MedMij FHIR Implementation Guide AllergyIntolerance {{VersieInfo|V2019.01|AllergieIntolerantie}}}}
{{MedMij:V2019.01_Issuebox_FHIR_IG}}

[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:Allergie.png|link=|87px |links||AllergyIntolerance]]
<imagemap>Bestand:Leeswijzer-technisch-banner 03 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_OntwerpAllergieIntolerantie|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_IG|Technisch]]
desc none
</imagemap>

__TOC__

=Introduction=
[[Bestand:Functioneel-02.png|link=MedMij:V2019.01_Ontwerpen |100px|rechts|Functional design|Go to functional design]]

This page describes a patient's use case, in a personal health record (PHR) context, for exchanging allergy and intolerance data. Functional specification of this use case is described in the [[MedMij:V2019.01_Ontwerpen| functional design wiki pages]]. The technical specification is described here. HL7 FHIR STU3 is used for this purpose.

=Actors involved=
{| class="wikitable"
! colspan="2" style="text-align:left;" | Persons
! colspan="2" style="text-align:left;" | Systems
! colspan="2" style="text-align:left;" | FHIR Capability Statements
|-
! style="text-align:left;" |Name
! style="text-align:left;" |Description
! style="text-align:left;" |Name
! style="text-align:left;" |Description
! style="text-align:left;" |Name
! style="text-align:left;" |Description
|-
| Patient
| The user of a personal healthcare enviorment.
| PHR
| Personal health record
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/allergyintolerance-clientcapabilities|CapabilityStatement: Client}}
| AllergyIntolerance client requirements
|-
| Healthcare professional
| The user of a XIS
| XIS
| Healthcare information system
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/allergyintolerance-servercapabilities|CapabilityStatement: Server}}
| AllergyIntolerance server requirements
|}

=Use case: Retrieve AllergyIntolerance information=
{{FHIR-IG-Afsprakenstelsel-Note}}

==Introduction==
The retrieve AllergyIntolerance transaction is used by the PHR to retrieve allergy and intolerance information from the XIS.

==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;vertical-align:top;" rowspan="3"|Retrieve AllergyIntolerance(PULL)
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance request
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
|style="background-color: white;vertical-align:top;"|Request allergy and intolerance information from the XIS
|-
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance response
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
|style="background-color: white;vertical-align:top;"|Serves allergy and intolerance information to the PHR
|}

==Invocations==
===PHR: request message===
The request message represents an HTTP GET query from the PHR to the XIS.

====Trigger Events====
When the patient(PHR) wants to obtain allergy and intolerance information, it issues a retrieve AllergyIntolerance request message.

====Message Semantics====
The PHR executes an HTTP GET conform to the FHIR [http://hl7.org/fhir/http.html RESTfull] and [http://hl7.org/fhir/search.html search] specification against the XIS's AllergyIntolerance endpoint. This search query has the following format.

<pre>
GET [base]/AllergyIntolerance
</pre>

=====Search Parameters=====
No query parameters are defined for this use case. The PHR searches on all AllergyIntolerance resources available for the patient using a HTTP GET on the AllergyIntolerance endpoint without parameters.

=====Expected Actions=====
The XIS shall process the query to discover AllergyIntolerance resources that match the patient in the context.

===XIS: response message===
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the allergy and intolerance information.

====Trigger Events====
The XIS completed processing of the Retrieve AllergyIntolerance request message.

====Message Semantics====
Based on the query results, the XIS will either return an error or success. When the XIS needs to report an error, it SHALL use HTTP error response codes and SHOULD include a FHIR OperationOutcome resource with more details on the failure. If the request message is processed successfully, whether or not any AllergyIntolerance resources are found, the HTTP status code SHALL be 200.

The response message shall be a Bundle resource of type "searchset" containing zero or more FHIR resources as entries. If the XIS is sending warnings, the Bundle resource SHALL also contain a FHIR OperationOutcome resource that contains those warnings. The FHIR specification describes the relevant sections:
*[http://hl7.org/fhir/STU3/http.html RESTful API framework]
*[http://hl7.org/fhir/STU3/search.html#errors Search errors]
*[http://hl7.org/fhir/STU3/bundle.html Bundle resource]
*[http://hl7.org/fhir/operationoutcome.html OperationOutcome resource]

=====Message resource content=====
The returned data to the PHR should conform to the zib AllergyIntolerance profile. The table below shows the relevant zibs and their profiles. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

{{NoteBoxPackage|https://simplifier.net/NictizSTU3-Zib2017/~packages|1.3.x|MedMij:V2019.01_FHIR_IG}}

{| class="wikitable"
|-style="background-color: #1F497D; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px"
|Zib name NL||Zib name EN||FHIR Resource||URL profile
|-style="vertical-align:top; background-color: #E3E3E3;
|-
| Patient
| #Zib Patient|Patient
| Patient
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient}}
|-
| AllergieIntolerantie
| AllergyIntolerance
| AllergyIntolerance
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance}}
|-
| rowspan="2" | Zorgverlener
| rowspan="2" | HealthProfessional
| Practitioner
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner}}
|-
| PractitionerRole
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole}}
|-
| Zorgaanbieder
| HealthcareProvider
| Organization
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization}}
|-
| Contactpersoon
| ContactPerson
| Patient.contact
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson}}
|}
{{Sjabloon:Voorbeelden}}

====Expected Actions====
The PHR processes the results according to application-defined rules. The PHR should be robust as the response may contain AllergyIntolerance information resources as mentioned in the former section.

==Interactions, operations, search parameters==
===Interactions===
The following logical interactions are needed for the retrieve AllergyIntolerance information transaction:
* [http://hl7.org/fhir/STU3/http.html#search Search]

===Operations===
No operations are defined or needed for this transaction.

===Search parameters===
No search parameters are defined or needed for this transaction.

=Use case: Retrieve AllergyIntolerance612ToFHIRConversion =
{{FHIR-IG-Afsprakenstelsel-Note}}

==Introduction==
A PHR uses the retrieve AllergyIntolerance612ToFHIRConversion transaction to retrieve "6.12-based" allergy and intolerance information from a XIS. This information is based on a conversion from the [https://www.nictiz.nl/standaardisatie/informatiestandaarden/medicatieveiligheid/ 6.12 information standard]. The XIS converts the requested information by a PHR to FHIR-resources.

The 6.12 AllergyIntolerance information is originally exchanged in HL7v3-messaging format. For interested readers the HL7v3-specifications can be found in the [http://decor.nictiz.nl/medicatieproces/mp-html-20181220T121121/tmp-2.16.840.1.113883.2.4.3.11.60.20.77.10.12-2013-08-19T000000.html 6.12 template for 'potential contraindications'].

However, please note that it is not necessary for a PHR to have knowledge of the HL7v3-format to implement this use case.

==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;vertical-align:top;" rowspan="3"|Retrieve AllergyIntolerance612ToFHIRConversion (PULL)
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance612ToFHIRConversion request
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
|style="background-color: white;vertical-align:top;"|Request allergy and intolerance information from the XIS
|-
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance612ToFHIRConversion response
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
|style="background-color: white;vertical-align:top;"|Serves allergy and intolerance information to the PHR
|}

==Invocations==
===PHR: request message===
The request message represents an HTTP GET query from the PHR to the XIS.

====Trigger Events====
When the patient(PHR) wants to obtain allergy and intolerance information, it issues a retrieve AllergyIntolerance612ToFHIRConversion request message.

====Message Semantics====
The PHR executes an HTTP GET conform to the FHIR [http://hl7.org/fhir/http.html RESTfull] and [http://hl7.org/fhir/search.html search] specification against the XIS's AllergyIntolerance612ToFHIRConversion endpoint. This search query has the following format.

<pre>
GET [base]/AllergyIntolerance
</pre>

=====Search Parameters=====
No query parameters are defined for this use case. The PHR searches on all AllergyIntolerance resources available for the patient using a HTTP GET on the AllergyIntolerance endpoint without parameters.

=====Expected Actions=====
The XIS shall process the query to discover AllergyIntolerance resources that are part of the 6.12 information standard and match the patient in the context.

===XIS: response message===
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the appropriate allergy and intolerance information.

====Trigger Events====
The XIS completed processing of the Retrieve AllergyIntolerance request message.

====Message Semantics====
Based on the query results, the XIS will either return an error or success. When the XIS needs to report an error, it SHALL use HTTP error response codes and SHOULD include a FHIR OperationOutcome resource with more details on the failure. If the request message is processed successfully, whether or not any AllergyIntolerance resources are found, the HTTP status code SHALL be 200.

The response message shall be a Bundle resource of type "searchset" containing zero or more FHIR resources as entries. If the XIS is sending warnings, the Bundle resource SHALL also contain a FHIR OperationOutcome resource that contains those warnings. The FHIR specification describes the relevant sections:
*[http://hl7.org/fhir/STU3/http.html RESTful API framework]
*[http://hl7.org/fhir/STU3/search.html#errors Search errors]
*[http://hl7.org/fhir/STU3/bundle.html Bundle resource]
*[http://hl7.org/fhir/operationoutcome.html OperationOutcome resource]

=====Message resource content=====
The returned data to the PHR should conform to the zib AllergyIntolerance profile. The table below shows the relevant zibs and their profiles. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

{{NoteBoxPackage|https://simplifier.net/NictizSTU3-Zib2017/~packages|1.3.x|MedMij:V2019.01_FHIR_IG}}

{| class="wikitable"
|-style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px"
|Zib name NL||Zib name EN||FHIR Resource||URL profile
|-style="vertical-align:top; background-color: #E3E3E3;
|-
| Patient
| #Zib Patient|Patient
| Patient
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient}}
|-
| AllergieIntolerantie
| AllergyIntolerance
| AllergyIntolerance
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp612-AllergyIntoleranceToFHIRConversion}}
|-
| rowspan="2" | Zorgverlener
| rowspan="2" | HealthProfessional
| Practitioner
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner}}
|-
| PractitionerRole
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole}}
|-
| Zorgaanbieder
| HealthcareProvider
| Organization
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization}}
|-
| Contactpersoon
| ContactPerson
| Patient.contact
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson}}
|}
{{Sjabloon:Voorbeelden}}
====Expected Actions====
The PHR processes the results according to application-defined rules. The PHR should be robust as the response may contain AllergyIntolerance information resources as mentioned in the former section.

==Interactions, operations, search parameters==
===Interactions===
The following logical interactions are needed for the retrieve AllergyIntolerance612ToFHIRConversion transaction:
* [http://hl7.org/fhir/STU3/http.html#search Search]

===Operations===
No operations are defined or needed for this transaction.

===Search parameters===
No search parameters are defined or needed for this transaction.

=Terminology, NamingSystems, Mappings=

===Terminology===
Relevant ValueSets can be found through the ValueSet bindings in the listed StructureDefinitions. All ValueSets can be found here [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ValueSet here] and can be downloaded as a .zip in XML or JSON format.

===NamingSystems===
Relevant NamingSystems can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=NamingSystem here].

===Mappings===
A FHIR ConceptMap resource is provided when a FHIR value set is used instead of a HCIM value set. A ConceptMap maps the values between the two value sets. These ConceptMaps can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap here].

An explanation about mappings can be found at [[MedMij:V2019.01_FHIR_IG#Mapping_of_coded_concepts|Mapping of coded concepts]].

=Annex: Document history=
==Release notes==
Release notes can be found on the [[MedMij:V2019.01_OntwerpAllergieIntolerantie#Release_notes|functional design page]].

==History==
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Date
!style="text-align:left;"|Description
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Deprecated invalid package 1.3.8, replaced with package 1.3.9
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Deprecated invalid package 1.3.7, replaced with package 1.3.8
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Changes for 2019.01 April 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - March 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Changes for 2019.01 March 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - January 2020
| style="background-color: white;"| 27-01-2020
| style="background-color: white;"|
* Changes for 2019.01 January 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - November
| style="background-color: white;"| 10-12-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - November
| style="background-color: white;"| 28-11-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - October
| style="background-color: white;"| 30-10-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white; | 2019.01
| style="background-color: white; | 18-10-2019
| style="background-color: white;"|
* Version 2.0.0 of this standaard, add use case.
* See release notes for changes.
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"|
*Publication of changes in version 2019.01, conform release notes.
*Moved release notes to the functional design page. 
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 12-11-2018
| style="background-color: white;"|
* Added section about Terminology, NamingSystems, Mappings.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 15-10-2018
| style="background-color: white;"|
* Added version in title, and document history.
|}

[[categorie:MedMij FHIR Use Cases]]

MedMij:Vprepub-2019.01 FHIR AllergyIntolerance

2020-05-07T12:48:37Z

Stephan Opdenberg: changed color of header

{{#customtitle:MedMij FHIR Implementation Guide AllergyIntolerance {{VersieInfo|V2019.01|AllergieIntolerantie}}}}
{{MedMij:V2019.01_Issuebox_FHIR_IG}}

[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:Allergie.png|link=|87px |links||AllergyIntolerance]]
<imagemap>Bestand:Leeswijzer-technisch-banner 03 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_OntwerpAllergieIntolerantie|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_IG|Technisch]]
desc none
</imagemap>

__TOC__

=Introduction=
[[Bestand:Functioneel-02.png|link=MedMij:V2019.01_Ontwerpen |100px|rechts|Functional design|Go to functional design]]

This page describes a patient's use case, in a personal health record (PHR) context, for exchanging allergy and intolerance data. Functional specification of this use case is described in the [[MedMij:V2019.01_Ontwerpen| functional design wiki pages]]. The technical specification is described here. HL7 FHIR STU3 is used for this purpose.

=Actors involved=
{| class="wikitable"
! colspan="2" style="text-align:left;" | Persons
! colspan="2" style="text-align:left;" | Systems
! colspan="2" style="text-align:left;" | FHIR Capability Statements
|-
! style="text-align:left;" |Name
! style="text-align:left;" |Description
! style="text-align:left;" |Name
! style="text-align:left;" |Description
! style="text-align:left;" |Name
! style="text-align:left;" |Description
|-
| Patient
| The user of a personal healthcare enviorment.
| PHR
| Personal health record
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/allergyintolerance-clientcapabilities|CapabilityStatement: Client}}
| AllergyIntolerance client requirements
|-
| Healthcare professional
| The user of a XIS
| XIS
| Healthcare information system
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/allergyintolerance-servercapabilities|CapabilityStatement: Server}}
| AllergyIntolerance server requirements
|}

=Use case: Retrieve AllergyIntolerance information=
{{FHIR-IG-Afsprakenstelsel-Note}}

==Introduction==
The retrieve AllergyIntolerance transaction is used by the PHR to retrieve allergy and intolerance information from the XIS.

==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;vertical-align:top;" rowspan="3"|Retrieve AllergyIntolerance(PULL)
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance request
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
|style="background-color: white;vertical-align:top;"|Request allergy and intolerance information from the XIS
|-
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance response
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
|style="background-color: white;vertical-align:top;"|Serves allergy and intolerance information to the PHR
|}

==Invocations==
===PHR: request message===
The request message represents an HTTP GET query from the PHR to the XIS.

====Trigger Events====
When the patient(PHR) wants to obtain allergy and intolerance information, it issues a retrieve AllergyIntolerance request message.

====Message Semantics====
The PHR executes an HTTP GET conform to the FHIR [http://hl7.org/fhir/http.html RESTfull] and [http://hl7.org/fhir/search.html search] specification against the XIS's AllergyIntolerance endpoint. This search query has the following format.

<pre>
GET [base]/AllergyIntolerance
</pre>

=====Search Parameters=====
No query parameters are defined for this use case. The PHR searches on all AllergyIntolerance resources available for the patient using a HTTP GET on the AllergyIntolerance endpoint without parameters.

=====Expected Actions=====
The XIS shall process the query to discover AllergyIntolerance resources that match the patient in the context.

===XIS: response message===
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the allergy and intolerance information.

====Trigger Events====
The XIS completed processing of the Retrieve AllergyIntolerance request message.

====Message Semantics====
Based on the query results, the XIS will either return an error or success. When the XIS needs to report an error, it SHALL use HTTP error response codes and SHOULD include a FHIR OperationOutcome resource with more details on the failure. If the request message is processed successfully, whether or not any AllergyIntolerance resources are found, the HTTP status code SHALL be 200.

The response message shall be a Bundle resource of type "searchset" containing zero or more FHIR resources as entries. If the XIS is sending warnings, the Bundle resource SHALL also contain a FHIR OperationOutcome resource that contains those warnings. The FHIR specification describes the relevant sections:
*[http://hl7.org/fhir/STU3/http.html RESTful API framework]
*[http://hl7.org/fhir/STU3/search.html#errors Search errors]
*[http://hl7.org/fhir/STU3/bundle.html Bundle resource]
*[http://hl7.org/fhir/operationoutcome.html OperationOutcome resource]

=====Message resource content=====
The returned data to the PHR should conform to the zib AllergyIntolerance profile. The table below shows the relevant zibs and their profiles. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

{{NoteBoxPackage|https://simplifier.net/NictizSTU3-Zib2017/~packages|1.3.x|MedMij:V2019.01_FHIR_IG}}

{| class="wikitable"
|-style="background-color: #1F497D; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px"
|Zib name NL||Zib name EN||FHIR Resource||URL profile
|-style="vertical-align:top; background-color: #E3E3E3;
|-
| Patient
| #Zib Patient|Patient
| Patient
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient}}
|-
| AllergieIntolerantie
| AllergyIntolerance
| AllergyIntolerance
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance}}
|-
| rowspan="2" | Zorgverlener
| rowspan="2" | HealthProfessional
| Practitioner
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner}}
|-
| PractitionerRole
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole}}
|-
| Zorgaanbieder
| HealthcareProvider
| Organization
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization}}
|-
| Contactpersoon
| ContactPerson
| Patient.contact
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson}}
|}
{{Sjabloon:Voorbeelden}}

====Expected Actions====
The PHR processes the results according to application-defined rules. The PHR should be robust as the response may contain AllergyIntolerance information resources as mentioned in the former section.

==Interactions, operations, search parameters==
===Interactions===
The following logical interactions are needed for the retrieve AllergyIntolerance information transaction:
* [http://hl7.org/fhir/STU3/http.html#search Search]

===Operations===
No operations are defined or needed for this transaction.

===Search parameters===
No search parameters are defined or needed for this transaction.

=Use case: Retrieve AllergyIntolerance612ToFHIRConversion =
{{FHIR-IG-Afsprakenstelsel-Note}}

==Introduction==
A PHR uses the retrieve AllergyIntolerance612ToFHIRConversion transaction to retrieve "6.12-based" allergy and intolerance information from a XIS. This information is based on a conversion from the [https://www.nictiz.nl/standaardisatie/informatiestandaarden/medicatieveiligheid/ 6.12 information standard]. The XIS converts the requested information by a PHR to FHIR-resources.

The 6.12 AllergyIntolerance information is originally exchanged in HL7v3-messaging format. For interested readers the HL7v3-specifications can be found in the [http://decor.nictiz.nl/medicatieproces/mp-html-20181220T121121/tmp-2.16.840.1.113883.2.4.3.11.60.20.77.10.12-2013-08-19T000000.html 6.12 template for 'potential contraindications'].

However, please note that it is not necessary for a PHR to have knowledge of the HL7v3-format to implement this use case.

==Actors==
{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transaction group'''
! style="text-align:left;"| '''Transaction'''
! style="text-align:left;"| '''Actor'''
! style="text-align:left;"| '''Role'''
|-
|style="background-color: white;vertical-align:top;" rowspan="3"|Retrieve AllergyIntolerance612ToFHIRConversion (PULL)
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance612ToFHIRConversion request
|style="background-color: white;vertical-align:top;"|Patient (using a PHR)
|style="background-color: white;vertical-align:top;"|Request allergy and intolerance information from the XIS
|-
|style="background-color: white;vertical-align:top;"|Retrieve AllergyIntolerance612ToFHIRConversion response
|style="background-color: white;vertical-align:top;"|Healthcare professional (using a XIS)
|style="background-color: white;vertical-align:top;"|Serves allergy and intolerance information to the PHR
|}

==Invocations==
===PHR: request message===
The request message represents an HTTP GET query from the PHR to the XIS.

====Trigger Events====
When the patient(PHR) wants to obtain allergy and intolerance information, it issues a retrieve AllergyIntolerance612ToFHIRConversion request message.

====Message Semantics====
The PHR executes an HTTP GET conform to the FHIR [http://hl7.org/fhir/http.html RESTfull] and [http://hl7.org/fhir/search.html search] specification against the XIS's AllergyIntolerance612ToFHIRConversion endpoint. This search query has the following format.

<pre>
GET [base]/AllergyIntolerance
</pre>

=====Search Parameters=====
No query parameters are defined for this use case. The PHR searches on all AllergyIntolerance resources available for the patient using a HTTP GET on the AllergyIntolerance endpoint without parameters.

=====Expected Actions=====
The XIS shall process the query to discover AllergyIntolerance resources that are part of the 6.12 information standard and match the patient in the context.

===XIS: response message===
The XIS returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the appropriate allergy and intolerance information.

====Trigger Events====
The XIS completed processing of the Retrieve AllergyIntolerance request message.

====Message Semantics====
Based on the query results, the XIS will either return an error or success. When the XIS needs to report an error, it SHALL use HTTP error response codes and SHOULD include a FHIR OperationOutcome resource with more details on the failure. If the request message is processed successfully, whether or not any AllergyIntolerance resources are found, the HTTP status code SHALL be 200.

The response message shall be a Bundle resource of type "searchset" containing zero or more FHIR resources as entries. If the XIS is sending warnings, the Bundle resource SHALL also contain a FHIR OperationOutcome resource that contains those warnings. The FHIR specification describes the relevant sections:
*[http://hl7.org/fhir/STU3/http.html RESTful API framework]
*[http://hl7.org/fhir/STU3/search.html#errors Search errors]
*[http://hl7.org/fhir/STU3/bundle.html Bundle resource]
*[http://hl7.org/fhir/operationoutcome.html OperationOutcome resource]

=====Message resource content=====
The returned data to the PHR should conform to the zib AllergyIntolerance profile. The table below shows the relevant zibs and their profiles. The resources in the response message SHALL be a valid instance of these profiles. All resources SHALL include their related profile canonical URL in the ''meta.profile'' element in order to show compliance.

{{NoteBoxPackage|https://simplifier.net/NictizSTU3-Zib2017/~packages|1.3.x|MedMij:V2019.01_FHIR_IG}}

{| class="wikitable"
|-style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px"
|Zib name NL||Zib name EN||FHIR Resource||URL profile
|-style="vertical-align:top; background-color: #E3E3E3;
|-
| Patient
| #Zib Patient|Patient
| Patient
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient}}
|-
| AllergieIntolerantie
| AllergyIntolerance
| AllergyIntolerance
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/mp612-AllergyIntoleranceToFHIRConversion}}
|-
| rowspan="2" | Zorgverlener
| rowspan="2" | HealthProfessional
| Practitioner
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner}}
|-
| PractitionerRole
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole}}
|-
| Zorgaanbieder
| HealthcareProvider
| Organization
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization}}
|-
| Contactpersoon
| ContactPerson
| Patient.contact
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-relatedperson}}
|}
{{Sjabloon:Voorbeelden}}
====Expected Actions====
The PHR processes the results according to application-defined rules. The PHR should be robust as the response may contain AllergyIntolerance information resources as mentioned in the former section.

==Interactions, operations, search parameters==
===Interactions===
The following logical interactions are needed for the retrieve AllergyIntolerance612ToFHIRConversion transaction:
* [http://hl7.org/fhir/STU3/http.html#search Search]

===Operations===
No operations are defined or needed for this transaction.

===Search parameters===
No search parameters are defined or needed for this transaction.

=Terminology, NamingSystems, Mappings=

===Terminology===
Relevant ValueSets can be found through the ValueSet bindings in the listed StructureDefinitions. All ValueSets can be found here [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ValueSet here] and can be downloaded as a .zip in XML or JSON format.

===NamingSystems===
Relevant NamingSystems can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=NamingSystem here].

===Mappings===
A FHIR ConceptMap resource is provided when a FHIR value set is used instead of a HCIM value set. A ConceptMap maps the values between the two value sets. These ConceptMaps can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap here].

An explanation about mappings can be found at [[MedMij:V2019.01_FHIR_IG#Mapping_of_coded_concepts|Mapping of coded concepts]].

=Annex: Document history=
==Release notes==
Release notes can be found on the [[MedMij:V2019.01_OntwerpAllergieIntolerantie#Release_notes|functional design page]].

==History==
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Date
!style="text-align:left;"|Description
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Deprecated invalid package 1.3.8, replaced with package 1.3.9
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Deprecated invalid package 1.3.7, replaced with package 1.3.8
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Changes for 2019.01 April 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - March 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Changes for 2019.01 March 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - January 2020
| style="background-color: white;"| 27-01-2020
| style="background-color: white;"|
* Changes for 2019.01 January 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - November
| style="background-color: white;"| 10-12-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - November
| style="background-color: white;"| 28-11-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - October
| style="background-color: white;"| 30-10-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white; | 2019.01
| style="background-color: white; | 18-10-2019
| style="background-color: white;"|
* Version 2.0.0 of this standaard, add use case.
* See release notes for changes.
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"|
*Publication of changes in version 2019.01, conform release notes.
*Moved release notes to the functional design page. 
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 12-11-2018
| style="background-color: white;"|
* Added section about Terminology, NamingSystems, Mappings.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 15-10-2018
| style="background-color: white;"|
* Added version in title, and document history.
|}

[[categorie:MedMij FHIR Use Cases]]

MedMij:V2019.01 FHIR BGZ 2017

2020-05-07T12:41:54Z

Stephan Opdenberg: changed header colour of table

__NUMBEREDHEADINGS__
{{#customtitle:MedMij FHIR Implementation Guide: BgZ {{VersieInfo|V2019.01|BgZ}}}}
{{MedMij:V2019.01_Issuebox_FHIR_IG}}

[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:BGZ_icoon.png |link=|links|90px|Use case BgZ 2017|Patient Summary (BgZ)]]
<imagemap>Bestand:Leeswijzer-technisch-banner 03 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_OntwerpBGZ_2017|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_IG|Technisch]]
desc none
</imagemap>

__TOC__

==Introduction==
[[Bestand:Functioneel-02.png|link=MedMij:V2019.01_Ontwerpen |100px|rechts|Functional design|Go to functional design]]

The program ‘Registratie aan de bron’ (Clinical documentation at the point of care) has defined Health and Care Information models ([https://zibs.nl/wiki/HCIM_Mainpage HCIMs] (English) or [https://zibs.nl/wiki/ZIB_Hoofdpagina zibs] (Dutch)) for The Netherlands. Next to these HCIMs, the program ‘Registratie aan de bron’ also made a selection of these HCIMs into the so-called ‘Basisgegevensset Zorg’ (Common Clinical Dataset, a Dutch version of a ‘patient summary’, further referred to as ‘BgZ’). The BgZ serves as a minimal healthcare dataset that is always appropriate for caregivers in order to provide continuity of care for a patient and can be seen as a representation of a patient summary.

A subselection of the published [https://zibs.nl/wiki/HCIM_Release_2017(EN) HCIMs release 2017] constitute the [https://www.registratieaandebron.nl/pdf/BgZ_specificatie_obv_zibs_2017_v1.1.pdf BgZ 2017]. The BgZ makes a subselection of the information concepts within the HCIMs or restricts the HCIMs to a certain category. For example, only include the general practitioner of the patient or only the last known value of 'X'. MedMij created FHIR profiles that represent these HCIMs completely if no existing and usable profiles were available. The profiles represent their entire respective HCIM, to make them applicable in a broader context than a patient summary or even the MedMij context. An overview of the profiles can be found at the [[MedMij:V2019.01_FHIR_BGZ_2017#List_of_StructureDefinitions|list of StructureDefinitions]].

The patient journey of [https://www.nictiz.nl/ehealth/MedMij Thomas van Beek], provides a patients context for exchanging a patient summary from a healthcare provider's system (XIS) to a personal health record (PHR). MedMij created a [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2019.01_Ontwerpen functional design] of the BgZ use case. This use case consists of enabling a patient to view his own BgZ in a PHR. This page will elaborate further on the HL7 FHIR details needed to exchange the BgZ information using FHIR.

==Actors involved==
{| class="wikitable"
! colspan="2" style="text-align:left;" | Actors
! colspan="2" style="text-align:left;" | Systems
! colspan="2" style="text-align:left;" | FHIR Capability Statements
|-
! style="text-align:left;" |Name
! style="text-align:left;" |Description
! style="text-align:left;" |Name
! style="text-align:left;" |Description
! style="text-align:left;" |Name
! style="text-align:left;" |Description
|-
| Patient
| The user of a personal healthcare enviorment.
| PHR
| Personal health record
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/bgz2017-clientcapabilities|CapabilityStatement: Client}}
| FHIR Client requirements
|-
| Healthcare professional
| The user of a XIS
| XIS
| Healthcare information system
|[[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/bgz2017-servercapabilities|CapabilityStatement: Server}}
| FHIR Server requirements
|}

==Boundaries and Relationships==
The BgZ 2017 v1.1 use case follows the BgZ v1.0 use case. The difference between the two is the underlying HCIMs, which have been upgraded from release 2015 to release 2017. The changes are documented in a [https://github.com/Nictiz/Nictiz-STU3-Zib2017/raw/master/ReleaseNotes%20FHIR%20profielen%20ZIB2017.pdf release notes] document.

The BgZ use case has similarities and differences with other use cases such as Medication Process, Vital Signs and Lab Results. These use cases use the same HCIM based FHIR profiles for exchanging information. The BgZ use case covers practically all profiles included in the other use cases. However, the BgZ differs in the scope of the actual health information content that should be exchanged. For example, the BgZ conveys only the last known lab result of each type while the Lab Results use case may cover all known information.

==List of invocations==
[[Bestand:Afsprakenstelsel-01.png|link=https://www.medmij.nl/afsprakenstelsel/|rechts |100px|Go to MedMij Afsprakenstelsel]]

This FHIR implementation guide assumes that the PHR system is able to make a connection to the XIS that contains the patients BgZ information. It does not provide information on finding the right XIS nor does it provide information about security. These infrastructure and interface specifications are described in the [https://www.medmij.nl/afsprakenstelsel/ 'MedMij Afsprakenstelsel'].

===Client - PHR===
The PHR system requests the BgZ using individual search interactions. The BgZ consists of multiple FHIR resources with certain constraints. To obtain the patient's BgZ, the client can use multiple individual search operations based on specified search queries. The interaction can be performed by an HTTP GET or command as shown:

<code>GET [base]/[type]/{?[parameters]{&_format=[mime-type]}}</code>

The table below shows in the first four columns the BgZ sections, the HCIMs that constitute those sections and the specific content of the BgZ. The last column shows the FHIR search queries to obtain the BgZ information. These queries are based on StructureDefinitions listed in [[#List_of_StructureDefinitions| this section]].

{{FHIR-IG-Afsprakenstelsel-Note}}

{| class="wikitable collapsible" width="100%" style="horizontal-align: right"
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px" | #
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px" | BgZ Section
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px" | HCIM EN
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px" | Content
!style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px" | Example Search URL
|-
| 1
| Patient information
| Patient
| Identification, birth date, gender, deceased indicator, contact details, last known marital status, and general practitioner (practitioner or organization)
| <pre>GET [base]/Patient?_include=Patient:general-practitioner</pre>
|-
| 2
| Payment details
| Payer
| Insurance information
| <pre>GET [base]/Coverage?_include=Coverage:payor:Patient&_include=Coverage:payor:Organization</pre>
|-
| rowspan="2" | 3
| rowspan="2" | Treatment directives
| TreatmentDirective
| Known treatment directives
| <pre>GET [base]/Consent?category=http://snomed.info/sct|11291000146105</pre>
|-
| AdvanceDirective
| Known advance directives
| <pre>GET [base]/Consent?category=http://snomed.info/sct|11341000146107</pre>
|-
| 4
| Contact persons
| ContactPerson
| First relation/contact
| <pre style="font-style: italic;">see Patient</pre>
|-
| 5
| Functional status
| FunctionalOrMentalStatus
| Last known functional / mental status
| <pre>GET [base]/Observation/$lastn?category=http://snomed.info/sct|118228005,http://snomed.info/sct|384821006</pre>
|-
| 6
| Problems
| Concern
| All known problems
| <pre>GET [base]/Condition</pre>
|-
| rowspan="5" | 7
| rowspan="5" | Social history
| LivingSituation
| Current living situation
| <pre>GET [base]/Observation/$lastn?code=http://snomed.info/sct|365508006</pre>
|-
| DrugUse
| All known drug use
| <pre>GET [base]/Observation?code=http://snomed.info/sct|228366006</pre>
|-
| AlcoholUse
| All known alcohol use
| <pre>GET [base]/Observation?code=http://snomed.info/sct|228273003</pre>
|-
| TobaccoUse
| All known tobacco use
| <pre>GET [base]/Observation?code=http://snomed.info/sct|365980008</pre>
|-
| NutritionAdvice
| All known current dietary recommendations
| <pre>GET [base]/NutritionOrder?status=active</pre>
|-
| 8
| Alerts
| Alert
| All known alerts
| <pre>GET [base]/Flag</pre>
|-
| 9
| Allergies
| AllergyIntolerance
| All known information regarding allergies
| <pre>GET [base]/AllergyIntolerance</pre>
|-
| rowspan="3" | 10
| rowspan="3" | Medication
| MedicationUse
| Known medication use
| <pre>GET [base]/MedicationStatement?category=urn:oid:2.16.840.1.113883.2.4.3.11.60.20.77.5.3|6&_include=MedicationStatement:medication</pre>
|-
| MedicationAgreement
| Known medication agreements
| <pre>GET [base]/MedicationRequest?category=http://snomed.info/sct|16076005&_include=MedicationRequest:medication</pre>
|-
| AdministrationAgreement
| Known administration agreements
| <pre>GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&_include=MedicationDispense:medication</pre>
|-
| 11
| Medical aids
| MedicalAid
| Known medical aids
| <pre>GET [base]/DeviceUseStatement?_include=DeviceUseStatement:device</pre>
|-
| 12
| Vaccinations
| Vaccination
| Known vaccinations
| <pre>GET [base]/Immunization?status=completed</pre>
|-
| rowspan="3" | 13
| rowspan="3" | Vital signs
| BloodPressure
| Last known blood pressure
| <pre>GET [base]/Observation/$lastn?code=http://loinc.org|85354-9</pre>
|-
| BodyWeight
| Last known body weight
| <pre>GET [base]/Observation/$lastn?code=http://loinc.org|29463-7</pre>
|-
| BodyHeight
| Last known body height
| <pre>GET [base]/Observation/$lastn?code=http://loinc.org|8302-2,http://loinc.org|8306-3,http://loinc.org|8308-9</pre>
|-
| 14
| Results
| LaboratoryTestResult
| Last known laboratory results per type
| <pre>GET [base]/Observation/$lastn?category=http://snomed.info/sct|275711006&_include=Observation:related-target&_include=Observation:specimen</pre>
|-
| 15
| Procedures
| Procedure
| Known surgical procedures
| <pre>GET [base]/Procedure?category=http://snomed.info/sct|387713003</pre>
|-
| 16
| Encounters
| Contact
| Known hospital admissions (no outpatient contacts)
| <pre>GET [base]/Encounter?class=http://hl7.org/fhir/v3/ActCode|IMP,http://hl7.org/fhir/v3/ActCode|ACUTE,http://hl7.org/fhir/v3/ActCode|NONAC</pre>
|-
| rowspan="5" | 17
| rowspan="5" | Planned care
| rowspan="5" | PlannedCareActivity
| rowspan="5" | Known planned care activities <nowiki>[</nowiki> [[#MM-115|*]] <nowiki>]</nowiki>
| <pre>GET [base]/ProcedureRequest?status=active</pre>
|-
| <pre>GET [base]/ImmunizationRecommendation</pre>
|-
| <pre style="text-decoration: line-through;">GET [base]/MedicationDispense?category=http://snomed.info/sct|422037009&status=in-progress,preparation&_include=MedicationDispense:medication</pre>
|-
| <pre>GET [base]/DeviceRequest?status=active&_include=DeviceRequest:device</pre>
|-
| <pre>GET [base]/Appointment?status=booked,pending,proposed</pre>
|-
| 18
| General practitioner
| HealthProfessional
| General Practitioner of the patient
| <pre style="font-style: italic;">see Patient</pre>
|}
{{Sjabloon:Voorbeelden}}

===Server - XIS===
Important sections of the FHIR specification for a server in this use case are the [http://hl7.org/fhir/STU3/http.html#2.21.0 RESTful API section] the [http://hl7.org/fhir/STU3/search.html search section] and [http://hl7.org/fhir/STU3/operations.html operation section] (for the lastn operation).

====Response to resource requests====
If the search succeeds, the server SHALL return a 200 OK HTTP status code and the returned content SHALL be a Bundle with type = searchset containing the results of the search as a collection of zero or more resources in a defined order. The returned content SHALL conform to the StructureDefinition applicable for the specific HCIM request. The list of a StructureDefinitions relevant for this use case is shown in the following paragraph: [[#List_of_StructureDefinitions | List of StructureDefinitions]]

The result collection can be long, so servers may use paging. If they do, they SHALL use the method described below (adapted from RFC 5005 (Feed Paging and Archiving ) for breaking the collection into pages if appropriate. The server MAY also return an [http://hl7.org/fhir/stu3/operationoutcome.html OperationOutcome resource] within the searchset Bundle entries that contains additional information about the search; if one is sent it SHALL NOT include any issues with a fatal or error severity, and it SHALL be marked with a Bundle.entry.search.mode of outcome.

In order to allow the client to be confident about what search parameters were used as criteria by the server, the server SHALL return the parameters that were actually used to process the search. Applications processing search results SHALL check these returned values where necessary. For example, if the server did not support some of the filters specified in the search, a client might manually apply those filters to the retrieved result set, display a warning message to the user or take some other action.

In the case of a RESTful search, these parameters are encoded in the self-link in the bundle that is returned:
<pre>
<link>
<relation value="self"/>
<url value="http://example.org/Patient?identifier=[Patient-ID]/>
</link>
</pre>

Link to the relevant FHIR specification: http://hl7.org/fhir/STU3/http.html#search

====Handling errors====
If the search fails '''(cannot be executed, not that there are no matches)''', the return value is a status code 4xx or 5xx with an OperationOutcome. An HTTP status code of 403 signifies that the server refused to perform the search, while other 4xx and 5xx codes signify that some sort of error has occurred. The HTTP status code 404 is returned if a XIS did not implement an endpoint used in a request by a PHR. When the search fails, a server SHOULD return an OperationOutcome detailing the cause of the failure. For example, in case of a not implemented FHIR endpoint, the OperationOutcome would state that the resource type is not supported. Note: an empty search result is not a failure.

Common HTTP Status codes returned on FHIR-related errors (in addition to normal HTTP errors related to security, header and content type negotiation issues):

* 400 Bad Request - search could not be processed or failed basic FHIR validation rules
* 401 Not Authorized - authorization is required for the interaction that was attempted
* 404 Not Found - resource type not supported, or not a FHIR end-point

In some cases, parameters may cause an error. For instance:

* A parameter may refer to a non-existent resource e.g. <code>GET [base]/Observation?subject=101</code>, where "101" does not exist
* A parameter may refer to an unknown code e.g. <code>GET [base]/Observation?code=loinc|1234-1</code>, where the LOINC code "1234-1" is not known to the server
* A parameter may refer to a time that is out of scope e.g. <code>GET [base]/Condition?onset=le1995</code>, where the system only has data going back to 2001
* A parameter may use an illegal or unacceptable modifier e.g. <code>GET [base]/Condition?onset:text=1995</code>, where the modifier cannot be processed by the server
* A date/time parameter may have incorrect format e.g. <code>GET [base]/Condition?onset=23%20May%202009</code>
* A parameter may be unknown or unsupported
Where the content of the parameter is syntactically incorrect, servers SHOULD return an error. However, where the issue is a logical condition (e.g. unknown subject or code), the server SHOULD process the search, including processing the parameter - with the result of returning an empty search set, since the parameter cannot be satisfied.

In such cases, the search process MAY include an OperationOutcome in the search set that contains additional hints and warnings about the search process. This is included in the search results as an entry with search mode = outcome. Clients can use this information to improve future searches.

Link to relevant FHIR specification: http://hl7.org/fhir/STU3/search.html#errors

==Interactions, operations, search parameters==

===Interactions===

The following logical interactions are needed for the BgZ use case:
* [http://hl7.org/fhir/STU3/http.html#search Search]

===Operations===
The following [http://hl7.org/fhir/STU3/operations.html operation] is needed for this use case.
* [http://hl7.org/fhir/STU3/observation-operations.html#lastn Last N Observations Query]

The lastn query meets the common need for searching for the most recent or last n=number of observations for a subject. For example, retrieving the last 5 temperatures for a patient to view trends or fetching the most recent laboratory results or vital signs. The link will provide more detailed information and examples regarding this operation.

===Search parameters===
The following search parameter types and search result parameters need to be supported for this use case.

Search parameter types:
* [http://hl7.org/fhir/STU3/search.html#token token]
** Including modifier 'in'
* [http://hl7.org/fhir/STU3/search.html#reference reference]

Search result parameters:
* [http://hl7.org/fhir/STU3/search.html#include _include]

==List of StructureDefinitions==
The profiles represent their entire respective HCIM, to make them applicable in a broader context than the exchange of BgZ or a MedMij context. An example of reuse of existing profiles is those of the patient administration resources and vital signs.

{{NoteBoxPackage|https://simplifier.net/NictizSTU3-Zib2017/~packages|1.3.x|MedMij:V2019.01_FHIR_IG}}

{| class="wikitable" style="horizontal-align: right"
!style="background-color: #1F497D; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px" | Section
!style="background-color: #1F497D; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px" | Zib NL
!style="background-color: #1F497D; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px" | HCIM EN
!style="background-color: #1F497D; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:100px" | FHIR Resource
!style="background-color: #1F497D; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:400px" | FHIR Profile
|-
| 1
| Patient
| #Zib Patient|Patient
| Patient
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient}}
|-
| rowspan="3" |2
| rowspan="3" | Betaler
| rowspan="3" | Payer
| Coverage
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Payer}}
|-
| Organization
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization}}
|-
| Patient
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient}}
|-
| rowspan="2" |3
| BehandelAanwijzing
| TreatmentDirective
| Consent
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TreatmentDirective}}
|-
| Wilsverklaring
| AdvanceDirective
| Consent
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AdvanceDirective}}
|-
| 4
| Contactpersoon
| ContactPerson
| Patient.contact
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient}}
|-
| 5
| Funct. OfMentaleStatus
| FunctionalOrMentalStatus
| Observation
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-FunctionalOrMentalStatus}}
|-
| 6
| Probleem
| Problem
| Condition
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Problem}}
|-
| rowspan="5" | 7
| Woonsituatie
| LivingSituation
| Observation
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LivingSituation}}
|-
| DrugsGebruik
| DrugUse
| Observation
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-DrugUse}}
|-
| AlcoholGebruik
| AlcoholUse
| Observation
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AlcoholUse}}
|-
| TabakGebruik
| TobaccoUse
| Observation
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-TobaccoUse}}
|-
| Voedingsadvies
| NutritionAdvice
| NutritionOrder
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-NutritionAdvice}}
|-
| 8
| Alert
| Alert
| Flag
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Alert}}
|-
| 9
| AllergieIntolerantie
| AllergyIntolerance
| AllergyIntolerance
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AllergyIntolerance}}
|-
| rowspan="3" | 10
| rowspan="3" | MedicatieGebruik
| MedicationUse
| MedicationStatement
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationUse}}
|-
| MedicationAgreement
| MedicationRequest
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicationAgreement}}
|-
| AdministrationAgreement
| MedicationDispense
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AdministrationAgreement}}
|-
| rowspan="2" | 11
| rowspan="2" | MedischHulpmiddel
| rowspan="2" | MedicalDevice
| Device
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicalDeviceProduct}}
|-
| DeviceUseStatement
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicalDevice}}
|-
| rowspan="2" | 12
| rowspan="2" | Vaccinatie
| rowspan="2" | Vaccination
| Immunization
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Vaccination}}
|-
| ImmunizationRecommendation
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VaccinationRecommendation}}
|-
| rowspan="3" | 13
| Bloeddruk
| BloodPressure
| Observation
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BloodPressure}}
|-
| LichaamsGewicht
| BodyWeight
| Observation
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyWeight}}
|-
| LichaamsLengte
| BodyHeight
| Observation
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-BodyHeight}}
|-
| rowspan="2" | 14
| rowspan="2" | LaboratoriumUitslag
| rowspan="2" | LaboratoryTestResult
| Observation
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Observation}}
|-
| Specimen
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-LaboratoryTestResult-Specimen}}
|-
| 15
| Verrichting
| Procedure
| Procedure
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Procedure}}
|-
| 16
| Contact
| Encounter
| Encounter
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-Encounter}}
|-
| rowspan="5" | 17
| rowspan="5" | GeplandeZorgActiviteit
| rowspan="5" | PlannedCareActivity
| ProcedureRequest
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-ProcedureRequest}}
|-
| MedicationDispense <nowiki>[</nowiki> [[#MM-115|*]] <nowiki>]</nowiki>
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-AdministrationAgreement}}
|-
| ImmunizationRecommendation
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-VaccinationRecommendation}}
|-
| DeviceRequest
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/zib-MedicalDeviceRequest}}
|-
| Appointment
| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/eAfspraak-Appointment}}
|-
| rowspan="3" | 18
| rowspan="2" | Zorgverlener
| rowspan="2" | HealthProfessional
| Practitioner
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner}}
|-
| PractitionerRole
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-practitionerrole}}
|-
| Zorgaanbieder
| HealthcareProvider
| Organization
| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-organization}}
|}

==Terminology, NamingSystems, Mappings==

===Terminology===
Relevant value sets can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ValueSet using the ValueSet category]. All resources can be downloaded in a .zip in XML or JSON format. In the .zip, the value sets are stored in the directory 'value sets'.

===NamingSystems===
Relevant NamingSystems can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=NamingSystem using the NamingSystem category].

===Mappings===
A FHIR ConceptMap resource is provided when a FHIR value set is used instead of a HCIM value set. A ConceptMap maps the values between the two value sets. These ConceptMaps can be found [https://simplifier.net/NictizSTU3-Zib2017/~resources?category=ConceptMap here].

An explanation about mappings can be found at [[MedMij:V2019.01_FHIR_IG#Mapping_of_coded_concepts|Mapping of coded concepts]].

=Annex: Document history=
==Release notes==
Release notes can be found on the [[MedMij:V2019.01_OntwerpBGZ_2017#Release_notes|functional design page]].

==History==
{| class="wikitable" "cellpadding="10" style="background-color: white;"
!style="text-align:left;"|Release
!style="text-align:left;"|Date
!style="text-align:left;"|Description
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Deprecated invalid package 1.3.8, replaced with package 1.3.9
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Deprecated invalid package 1.3.7, replaced with package 1.3.8
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Changes for 2019.01 April 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - March 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Changes for 2019.01 March 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - February 2020
| style="background-color: white;"| 27-02-2020
| style="background-color: white;"|
* Changes for 2019.01 February 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - January 2020
| style="background-color: white;"| 27-01-2020
| style="background-color: white;"|
* Changes for 2019.01 January 2020 patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - November
| style="background-color: white;"| 10-12-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - November
| style="background-color: white;"| 28-11-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - October
| style="background-color: white;"| 30-10-2019
| style="background-color: white;"|
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Changes for 2019.01 September patch release
* Added new version of FHIR package
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"| '''*''' [https://bits.nictiz.nl/browse/MM-115 MM-115] Solved inconsistency in the List of StructureDefinitions. Also we will no longer check PlannedCareActivityForTransfer for MedicationAdministration in section 17 Zorgplan, because we found it was unimplementable as-is. Presumed solution will come from a future HCIM release.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"|
*Publication of changes in version 2019.01, conform release notes
*Moved release notes to functional design page
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 18-10-2018
| style="background-color: white;"|
* Corrected SNOMED code in search url for FunctionalOrMentalStatus
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 15-10-2018
| style="background-color: white;"|
* Added version in title, and document history
|}
[[categorie:MedMij FHIR Use Cases]]

MedMij:Vprepub-2019.01 FHIR BGZ 2017

2020-05-07T12:41:54Z

Stephan Opdenberg: changed header colour of table

MedMij:V2019.01 OntwerpBeelden

2020-05-01T07:44:01Z

Stephan Opdenberg: /* Release notes */

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp Beelden {{VersieInfo|V2019.01|Beelden}}}}

[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:beeldenIcoon.png|link=|87px |links||media]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_Images|Technisch]]
desc none
</imagemap>

=Inleiding=
==Algemeen==
Deze pagina beschrijft het functioneel ontwerp voor de uitwisseling van beelden binnen MedMij. De algemene inleiding van de MedMij functionele ontwerpen kan [[MedMij:V2019.01_Ontwerpen| hier]] gevonden worden.

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de MedMij functionele ontwerpen, die [[MedMij:V2019.01_Ontwerpen#Doelgroep| hier]] gevonden kan worden.

==Kaders en uitgangspunten==
===Richtlijn===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Richtlijn| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

=Use Cases=
==Use case 1: Sturen beelden vanuit een PGO==
=== Doel en relevantie ===
*Het voor patiënten/ personen mogelijk maken regie op hun eigen gezondheid te nemen door beelden te sturen naar (verschillende) zorgaanbieders.
*Deze use case ondersteunt geen interactie met de patiënt middels het PGO. De zorgverlener kan niet online reageren op de gestuurde beelden. De zorgverlener dient buiten deze use case om de beelden te bespreken met de patiënt.

=== Domein ===
Beelden in het domein van zorgaanbieders en patiënten/ personen.

=== Context ===
Het gaat om het elektronisch en gestructureerd sturen van beelden vanuit een [[#persoonlijke-gezondheidsomgeving|persoonlijke gezondheidsomgeving]] (PGO) naar een zorgaanbiederssysteem (XIS). Deze pagina bevat (verwijzingen naar) beschrijvingen van:
* informatie,
* bedrijfsrollen (actoren),
* proces,
* systemen,
* systeemrollen,
* transactiegroepen en transacties, inclusief de inhoud van deze transacties.

De beschrijving is infrastructuur-onafhankelijk.

=== Informatie ===
Bij het sturen van beelden gaat het om de volgende informatie die uitgewisseld wordt: de beelden, bijbehorende meta-informatie per beeld en een mogelijk toelichting/ begeleidende tekst.

De informatie-elementen voor sturen en ontvangen van een beeld of collectie beelden staan in [http://decor.nictiz.nl/pub/beelden/bd-html-20190512T171559/tr-2.16.840.1.113883.2.4.3.11.60.54.4.2-2019-02-25T131649.html ART-DECOR Sturen Beelden].

==== Beeldformaat ====
*De ontvangende systemen dienen de volgende gegevensformaten te ondersteunen: JPEG, PNG, GIF en JP2. De PGO bepaalt zelf in welke van deze ondersteunende beeldformaten, de beelden worden verstuurd. De genoemde beeldformaten zijn ook de gegevensformaten, bestaande uit één frame, die door [[#DICOM-beeldformaten|DICOM standaard]] worden gespecificeerd voor gebruik bij DICOM web-services. Binnen deze use case zijn dit de enige gebruikte gegevensformaten voor beelden. Beeldformaat DICOM is niet in scope voor deze use case.
*Beelden mogen extra (meta)informatie bevatten in bijvoorbeeld de [[#Exif|Exif standaard]]. Een voorbeeld is het opslaan van patiëntgegevens binnen het beeldformaat JPEG. Hier wordt in deze use case echter geen gebruik van gemaakt.

==== Frequentie sturen beeld(en) ====
*Met het oog op bijvoorbeeld een ''denial of service attack'' is de overweging geweest om de frequentie waarmee de patiënt beelden kan versturen te beperken. Besloten is om voorlopig geen beperkingen op te nemen in de standaard.

==== Grootte van beeld(en) ====
De maximale grootte van een beeld is 20 MB (voordat het Base64 encoded is). Een PGO kan één tot maximaal 3 beelden tegelijk sturen. De maximale grootte van een collectie beelden is 60 MB. Base64 codering maakt het resultaat 37% groter.

==== Toelichting ====
De patiënt kan per beeld en/of per collectie beelden een begeleidende tekst meegeven. Dit gaat middels de 'toelichting' meta-informatie elementen.

==== Meta-informatie ====
Het beeld dient te worden voorzien van voldoende meta-informatie om door het ontvangende systeem goed te kunnen worden geïnterpreteerd. De specificatie van de meta-informatie wordt gegeven in de dataset en transactiebeschrijving. Daarnaast kent het FHIR profiel, verwezen vanuit het technisch ontwerp, nog een aantal verplichte concepten.
Deze use case houdt rekening met zelfstandige XIS-sen en met XIS-sen die zijn aangesloten op een XDS-netwerk door het bericht te voorzien van voldoende meta-informatie voor indexatie. Het correct indexeren van beelden in een XDS netwerk is de verantwoordelijkheid van het ontvangende XIS. Het technische ontwerp geeft een niet-normatieve implemenatierichtlijn middels een mapping van het FHIR bericht naar XDS concepten en het IHE MHD profiel.

=== Bedrijfsrollen ===
Deze use case onderscheidt twee bedrijfsrollen, namelijk de ''Patiënt'' en de ''Zorgaanbieder'' zoals te zien in onderstaande tabel.

{| class="wikitable" "cellpadding="10" width="100%"
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil beelden sturen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Wil beelden ontvangen
|}
'''Bedrijfsrollen sturen beelden'''

Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd.

[[Image:Activity_Diagram_-_Sturen_Beelden.png|Activiteitendiagram sturen beelden]]

'''Activiteitendiagram sturen beelden'''

=== Procesbeschrijving ===
==== Patient Journey – Thomas van Beek ====
Een voorbeeldsituatie die de meerwaarde van het sturen van beelden vanuit het PGO schetst is de patiënt journey van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Thomas_van_Beek_MedMij.pdf Thomas van Beek].
<blockquote>De afgelopen periode heeft Thomas wisselend last van eczeem. De vorige keer dat Thomas een dergelijke aanval had, waren de klachten al afgenomen op het moment dat de afspraak met de huisarts plaatsvond. Om de ernst van de klachten te kunnen inschatten heeft de huisarts gevraagd of Thomas in het vervolg een foto kan maken van de eczeem wanneer deze in alle ernst aanwezig zijn.
Vandaag is het weer zover. Bij het maken van de afspraak met de huisarts verzoekt de assistente of Thomas direct een foto kan maken en deze de huisarts wil toesturen. Thomas maakt foto's van onder andere zijn gezicht en upload deze naar zijn PGO. Een paar dagen na het versturen van de foto heeft hij een afspraak bij de huisarts. De foto's komen tijdens het consult ter sprake en een passende behandeling wordt gekozen.</blockquote>

==== Patient Journey – Kenneth van Someren ====
Een tweede voorbeeld waarbij de meerwaarde van het sturen van beelden vanuit het PGO geschetst kan worden is de patiënt journey van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Kenneth_van_Someren_MedMij.pdf Kenneth van Someren].

<blockquote>De grote antieke stoel in de woonkamer is het plekje waar Kenneth thuis graag te vinden is. De stoel begon echter de laatste tijd steeds minder lekker te zitten. De zuster adviseert regelmatig af te wisselen met de bank, maar de televisie is lang niet zo interessant als het dorpsplein aan de overkant van de straat. Het begon met enkel een klein rood plekje op zijn ruggengraat, maar inmiddels begon dit vormen aan te nemen die ook dochter Debby zorgen baarde. Na kort overleg met de thuiszorg besluit ze telefonisch contact op te nemen met de wondverpleegkundige van de organisatie. Deze vraagt om een duidelijke foto te maken en via het PGO te sturen voor beoordeling. De wondverpleegkundige ziet de foto en vind het ook zorgelijk. Daarom maak ze direct een afspraak met Kenneth om de plek zelf te beoordelen. De volgende ochtend lukt dat al en die middag komt de thuiszorg met de juiste kennis en materialen om de wond te behandelen.</blockquote>

==== Proces ====
Het stuk van het proces waar het in deze use case omgaat is:
* Patiënt en zorgverlener maken de afspraak dat de patient een beeld kan sturen aan de zorgverlener.
* Patiënt maakt, ontvangt of downloadt één of meerdere beelden en uploadt deze naar zijn PGO. De beelden kunnen gemaakt zijn door de patiënt, een zorgaanbieder of iemand anders.
* Patiënt heeft de mogelijkheid om een begeleidende tekst van maximaal 1 MB toe te voegen aan het beeld en/of beelden.
* Het PGO stuurt de beelden naar het systeem van de zorgaanbieder.
** Mogelijk moet of kan de patiënt metagegevens behorende bij de beelden aanvullen of invullen.
* De zorgaanbieder raadpleegt de beelden in zijn eigen dossier (XIS).
* De zorgverlener bespreekt het beeld buiten het PGO om met de patiënt. Deze use-case ondersteunt geen interactie met de patiënt middels het PGO.

Deze paragraaf vervolgt met een beschrijving van precondities, processtappen, en postcondities.

===== Preconditie =====
* De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van beelden tussen het eigen PGO en de betreffende XIS.
* De patiënt en zorgaanbieder hebben onderling afspraken gemaakt over het sturen van beelden.
* Het XIS van de zorgaanbieder is in staat afbeeldingen van de patient te ontvangen.
* De beelden bevinden zich in of zijn toegankelijk voor, het PGO

===== Processtappen =====
* Het systeem van de patiënt (PGO) stuurt de beelden naar het systeem van de zorgaanbieder (XIS).
* Het systeem van de zorgaanbieder (XIS) ontvangt de beelden van het PGO.

===== Postconditie =====
* Indien het systeem van de zorgaanbieder (XIS) gebruik maakt van een XDS-omgeving zal dit systeem de beelden op gepaste wijze in het netwerk registreren.
* De zorgaanbieder gebruikt het systeem (XIS) om de beelden te kunnen zien en/of beoordelen.

=== Systemen & Systeemrollen ===
Zowel de patiënt als de zorgaanbieder maken ieder gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om beelden van de patiënt naar de zorgaanbieder.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| Sturen van Beelden
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Beelden}}-BES-FHIR
| style="background-color: white;"| Sturen van beelden naar zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| Ontvangen van Beelden
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Beelden}}-BEO-FHIR
| style="background-color: white;"| Ontvangen van beelden vanuit het PGO
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:Component_Diagram_-_Sturen_Beelden_(Totaal).png|Componenten diagram]]

'''Componenten diagram van systemen en systeemrollen'''

=== Transacties & Transactiegroepen ===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een stuur- en ontvangstbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:middle;" rowspan="2"|Beelden (PUSH)
|style="background-color: white;vertical-align:top;"|Sturen Beelden
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Beelden}}-BES-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_Images |Beelden in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Ontvangen Beelden
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Beelden}}-BEO-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:Use_Case_Diagram_-_Sturen_Beelden.png|Use case diagram Sturen Beelden]]

'''Use case diagram sturen beelden

=Functionaliteit=

== Eisen en wensen ==
*'''Afstemming vooraf''': Tijdens de ontwikkeling van de informatiestandaard is er nagedacht over het opnemen van een verplichte checkbox die de patiënt moet aanvinken om aan te geven dat er afstemming is geweest met de zorgverlener. Uiteindelijk is besloten om deze eis niet op te nemen in de standaard omdat in de praktijk patiënt en zorgverlener altijd een context hebben waarin het sturen van de beelden past. Daarnaast is het uitgangspunt om de patiënt zo min mogelijk te laten invullen bij het sturen van een beeld.

== Niet functionele eisen en wensen ==
Het technisch ontwerp bevat een aantal verplichte (technische) data elementen die niet zijn opgenomen in de functionele dataset. Een aantal van deze velden zijn verplicht gesteld om compatibiliteit met XDS-netwerken te ondersteunen. Het gaat om de volgende elementen:

* Indentificatie van het beeld en collectie beelden
* Een hash van de data van het beeld

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="text-align:left;"|Auteur(s)
!style="text-align:left;"|Titel
!style="text-align:left;"|Versie
!style="text-align:left;"|Datum
!style="text-align:left;"|Bron
!style="text-align:left;"|Organisatie
|-
| style="background-color: white;"| -
| style="background-color: white;"| Persoonlijke Gezondheidsomgeving
| style="background-color: white;"|
| style="background-color: white;"| 06-12-2018
| style="background-color: white;"| https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/
| style="background-color: white;"| Patiëntenfederatie Nederland
|-
| style="background-color: white;"| -
| style="background-color: white;"| Rendered Media Types
| style="background-color: white;"|
| style="background-color: white;"| 10-12-2018
| style="background-color: white;"| http://dicom.nema.org/medical/dicom/2017d/output/html/part18.html#table_6.1.1-3
| style="background-color: white;"| NEMA (DICOM)
|-
| style="background-color: white;"| -
| style="background-color: white;"| Exif
| style="background-color: white;"|
| style="background-color: white;"| 10-12-2018
| style="background-color: white;"| https://en.wikipedia.org/wiki/Exif
| style="background-color: white;"| Wikipedia
|}

'''Referenties

=Bijlage: Documenthistorie=

==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:V2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

{| class="wikitable" "cellpadding="10" style="background-color: white;"
!style="text-align:left;"|Release
!style="text-align:left;"|Versie
!style="text-align:left;"|BITS issue
!style="width:850px; text-align:left;"|Omschrijving

{{ReleaseNotes|package=2019.01 - April|release=1.0.6|issues=2|MM-1032|MM-954}}
{{ReleaseNotes|package=2019.01 - Maart|release=1.0.4|issues=1|MM-1007}}
|-
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
|-
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
|}

==Paginahistorie==
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Datum
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor april 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Maart 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Wijzigingen voor maart 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Februari 2020
| style="background-color: white; | 27-02-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Januari 2020
| style="background-color: white; | 27-01-2020
| style="background-color: white;"|
* Wijzigingen voor januari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 28-11-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 13-05-2019
| style="background-color: white;"|
* Versie 1.0.0 gepubliceerd.
|}

MedMij:Vprepub-2019.01 OntwerpBeelden

2020-05-01T07:44:01Z

Stephan Opdenberg: /* Release notes */

MedMij:V2019.01 OntwerpGGZ

2020-05-01T07:42:18Z

Stephan Opdenberg: /* Release notes */

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp Basisgegevens GGZ {{VersieInfo|V2019.01|BgGGZ}} (op basis van zibs release 2017)}}

[[Bestand:MedMij-GGZ-63.png |link=|links|80px|Use case GGZ|GGZ]]
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_GGZ|Technisch]]
desc none
</imagemap>

=Inleiding=

==Algemeen==
Deze pagina beschrijft het functioneel ontwerp voor de uitwisseling van Basisgegevens GGZ op basis van een selectie zorginformatiebouwstenen (zibs) binnen MedMij. De algemene inleiding van de MedMij functionele ontwerpen kan [[MedMij:V2019.01_Ontwerpen| hier]] gevonden worden.

Binnen het [https://www.vippggz.nl/regeling/doelstellingen.html VIPP GZZ programma] zijn een drietal modules opgenomen:
* Module "Patiënt & Informatie": de Basisgegevens GGZ is bedoeld voor deze module.
* Module "Patiënt & Medicatie": hiervoor wordt verwezen naar het [[MedMij:V2019.01_OntwerpMedicatie| functioneel ontwerp]] voor [https://www.nictiz.nl/programmas/medicatieproces Medicatieproces 9.0].
* Module "Patiënt & eHealth".

Voor de module "Patiënt & Informatie" is een [https://zoek.officielebekendmakingen.nl/stcrt-2018-60877.html#d17e2089 lijst van verplichte zorginformatiebouwstenen (zibs)] vastgesteld die geschikt zijn verklaard voor de GGZ sector, de Basisgegevens GGZ. Deze lijst omvat momenteel alleen de reeds beschikbare zibs (publicatie 2017) met minimale inhoud en structuur als opmaat naar een volwaardige GGZ informatiestandaard (in ontwikkeling door GGZ Nederland en Nictiz). De lijst van zibs en hierop gebaseerd specificaties vertoont enige overlap met de [https://www.nictiz.nl/standaardisatie/informatiestandaarden/basisgegevensset-zorg-bgz Basisgegevensset Zorg (BgZ)] maar is zeker niet hetzelfde: zie [[MedMij:V2019.01_OntwerpGGZ#Informatie| Informatie]] voor een nadere toelichting over het samenstellen van de inhoud.

De use cases voor de toekomstige GGZ informatiestandaard zijn nog niet omschreven, echter staat voor het VIPP GGZ programma het perspectief van de patiënt centraal. Het doel van deze pagina is dan ook om de uitwisseling van de Basisgegevens GGZ met de patiënt te omschrijven.

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de MedMij functionele ontwerpen, die [[MedMij:V2019.01_Ontwerpen#Doelgroep| hier]] gevonden kan worden.

==Kaders en uitgangspunten==
===Richtlijn===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Richtlijn| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

===Specifieke informatie over deze kwalificatie===
Specifieke informatie over de kwalificatie van de transacties 'Raadplegen GGZ' en 'Beschikbaarstellen GGZ' is [[MedMij:V2019.01_ToelichtingKwalificatieGGZ| hier]] te vinden.

=Use Cases=
==Use case 1: Raadplegen Basisgegevens GGZ in persoonlijke gezondheidsomgeving==
=== Doel en relevantie ===
Het voor patiënten mogelijk maken regie op hun eigen gezondheid te nemen door inzicht te geven in de Basisgegevens GGZ die over henzelf gaan.

=== Domein ===
Basisgegevens GGZ in het domein van zorgaanbieders en patiënten.

=== Context ===
Het gaat om het elektronisch en gestructureerd beschikbaar maken van de Basisgegevens GGZ vanuit een zorgaanbiederssysteem (XIS) naar een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO).
Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie,
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.

De beschrijving is infrastructuur-onafhankelijk.

=== Informatie ===
De Basisgegevens GGZ bestaat uit een selectie van 24 zibs. Deze zibs vormen samen een verzameling van gegevens die binnen de GGZ sector toepasbaar zijn. Hierbij bestaat de selectie voorlopig alleen uit reeds bestaande zibs (publicatie 2017) die voor de GGZ sector geschikt zijn met een minimale inhoud en structuur zoals te vinden in dit [[MedMij:V2019.01_InhoudGGZ|overzicht]]. Bij de ontwikkeling van de volwaardige GGZ informatiestandaard wordt dit nader gespecificeerd, met nadere uitwerking van GGZ-specifieke gegevens die nog niet gedekt worden door bestaande zibs. De Basisgegevens GGZ zal in de toekomst hiermee worden aangevuld. De huidige lijst aan geselecteerde zibs komt voor een deel overeen met de [https://www.nictiz.nl/standaardisatie/informatiestandaarden/basisgegevensset-zorg-bgz/ Basisgegevensset Zorg (BgZ)], maar voor een deel ook niet: het gaat om twee aparte sets. Zie het [[MedMij:V2019.01_InhoudGGZ|overzicht van de inhoud]] voor een nadere toelichting.

Medicatiegegevens vallen buiten de Basisgegevens GGZ, omdat hiervoor gebruik wordt gemaakt van het reeds bestaande [https://www.nictiz.nl/programmas/medicatieproces Medicatieproces 9.0] (zie [[MedMij:V2019.01_OntwerpMedicatie| hier]] voor uitwisseling medicatiegegevens in PGO).

In de bestaande zibs valt de zogenaamde juridische status en vertegenwoordiging binnen de zib VrijheidsbeperkendeMaatregelen. Voor de GGZ sector is het loskoppelen van dit gegeven (als losstaande zib) van groot belang, omdat deze ook relevant is buiten de toepassing van vrijheidsbeperkende maatregelen. In de verdere uitwerking van de Basisgegevens GGZ is het element JuridischeStatus losgekoppeld van de verdere zib VrijheidsbeperkendeMaatregelen. Deze loskoppeling wordt tevens als wijzigingsverzoek behandeld bij de nieuwe publicatie zibs: de huidige uitwerking loopt op deze toekomstige ontwikkeling vooruit.

In de MedMij FHIR implementatie gids staat de technische representatie van de betreffende zibs in zogenaamde FHIR profielen. In dit [[MedMij:V2019.01_FHIR_GGZ#List_of_StructureDefinitions|overzicht]] is te zien welk FHIR profiel bij welke zib hoort.

=== Bedrijfsrollen ===
Deze use case onderscheidt twee bedrijfsrollen, namelijk de ''Patiënt'' en de ''Zorgaanbieder'' zoals te zien in onderstaande tabel.

{| class="wikitable" "cellpadding="10" width="100%"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Bedrijfsrol'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil de eigen Basisgegevens GGZ raadplegen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Stelt de Basisgegevens GGZ beschikbaar
|}
'''Bedrijfsrollen Basisgegevens GGZ'''

Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd.

[[Image:InzienGGZ_activity.png|Activiteitendiagram Raadplegen GGZ]]

'''Activiteitendiagram Raadplegen GGZ'''

=== Procesbeschrijving ===
==== Patient journey - Jelmer Postma ====
De 'patient journey' van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Jelmer_Postma_MedMij.pdf Jelmer Postma] beschrijft enkele momenten waarop je als patiënt zijnde inzicht kan of zou willen hebben in zijn/haar Basisgegevens GGZ.

<blockquote>In zijn PGO kan Jelmer doorlezen wat de huisarts voorgeschreven heeft en vindt hij de verwijzing voor een psycholoog. Hij zoekt een psycholoog uit en maakt een afspraak waarbij hij de verwijzing bijvoegt.</blockquote>

<blockquote>‘Pling’, Jelmer krijgt van zijn PGO een reminder dat hij morgen om 10.00 zijn eerste afspraak heeft bij de psycholoog. Tevens kan hij vanuit zijn PGO een vragenlijst invullen voor de psycholoog over zijn klachten, gezondheid en verwachtingen. Wat zijn huisarts al vermoedde, wordt door de psycholoog bevestigd.</blockquote>

<blockquote>Gedurende de sessie komen er onverwerkte zaken uit zijn jeugd boven. Deze zijn zo heftig dat Jelmer in een acute depressie belandt. Zijn vriendin Karin geeft aan dat Jelmer op het moment niet thuis kan wonen en samen met de huisarts nemen ze het besluit dat Jelmer voor korte duur opgenomen wordt bij een GGZ-instelling in de buurt. Hier wordt een nieuw behandelplan opgesteld waarin groepstherapie een onderdeel gaat worden. Jelmer heeft Karin gemachtigd om in zijn PGO te kijken zodat ze onder andere het behandelplan in kan zien en ze goed betrokken wordt.</blockquote>

<blockquote>De opname in de GGZ-instelling is van korte duur. Vanaf nu wordt Jelmer ambulant behandeld door een reguliere GGZ-instelling. Gelukkig is deze met 5 minuten fietsen van huis lekker dichtbij. De psychiater van de instelling schrijft een overdracht voor zijn nieuwe hoofdbehandelaar. Zowel Karin als Jelmer kunnen via het PGO inzien wat daarin staat. Daarom weten ze nu dat de medicatie is aangepast.</blockquote>

==== Proces ====
Het stuk van het proces waar het in deze use case om gaat is:
* Het systeem van een zorgaanbieder (XIS) stelt de Basisgegevens GGZ van de patiënt beschikbaar aan het systeem van een patiënt (PGO).

Deze paragraaf vervolgt met een beschrijving van precondities, proces stappen, en post condities.

===== Preconditie =====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van de Basisgegevens GGZ tussen het betreffende XIS en het eigen PGO.

De Basisgegevens GGZ, of een gedeelte van de Basisgegevens GGZ, welke de persoon wil inzien, bestaat en de zorgaanbieder wil deze beschikbaar stellen.
:Soms zijn er valide redenen om de Basisgegevens GGZ, of gedeeltes daarvan, tijdelijk nog niet beschikbaar te stellen aan de patiënt. Bijvoorbeeld omdat de zorgverlener deze eerst zelf wil interpreteren en/of er eerst met de patiënt over wil spreken.
:Een patiënt kan steeds zelf het initiatief nemen om de Basisgegevens GGZ op te halen, maar het is ook mogelijk dat een PGO geconfigureerd is om dit 'automatisch' te doen. Dit maakt voor de scope van deze use case beschrijving geen verschil.

===== Proces stappen =====
* Het systeem van de patiënt (PGO) raadpleegt het systeem van de zorgaanbieder (XIS) voor de Basisgegevens GGZ van de patiënt.
* Het systeem van de zorgaanbieder (XIS) maakt (een deel van) de Basisgegevens GGZ beschikbaar voor de patiënt.
* De patiënt gebruikt de persoonlijke gezondheidsomgeving om de Basisgegevens GGZ in te zien.

===== Post conditie =====
De persoon kan de Basisgegevens GGZ inzien via een persoonlijke gezondheidsomgeving.

=== Systemen & Systeemrollen ===
Zowel de persoon als de zorgaanbieder maken ieder gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om de Basisgegevens GGZ van zorgaanbieder naar de persoon.

{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Systeem
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Naam systeemrol
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Systeemrolcode
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| GGZRaadplegend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|BgGGZ}}-GGR-FHIR
| style="background-color: white;"| Raadplegen Basisgegevens GGZ bij zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| GGZBeschikbaarstellend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|BgGGZ}}-GGB-FHIR
| style="background-color: white;"| Beschikbaarstellen Basisgegevens GGZ aan de patiënt
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:InzienGGZ_componenten.png.PNG|Componenten diagram]]

'''Componenten diagram van systemen en systeemrollen'''

=== Transacties & Transactiegroepen ===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Transactiegroep'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Transactie'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Systeemrolcode'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Systeem'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Bedrijfsrol'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:middle;" rowspan="2"|GGZ (PULL)
|style="background-color: white;vertical-align:top;"|[https://decor.nictiz.nl/decor/services/RetrieveTransaction?id=2.16.840.1.113883.2.4.3.11.60.57.4.2&effectiveDate=2019-03-05T17:07:53&language=nl-NL&ui=nl-NL&format=html&hidecolumns=34567 Raadplegen GGZ]
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|BgGGZ}}-GGR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_GGZ |GGZ in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|[https://decor.nictiz.nl/decor/services/RetrieveTransaction?id=2.16.840.1.113883.2.4.3.11.60.57.4.3&effectiveDate=2019-03-05T17:07:53&language=nl-NL&ui=nl-NL&format=html&hidecolumns=34567 Beschikbaarstellen GGZ]
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|BgGGZ}}-GGB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:InzienGGZ_useCase.png|Use case diagram raadplegen Basisgegevens GGZ]]

'''Use case diagram raadplegen Basisgegevens GGZ

=Functionaliteit=
Er zijn geen aanwijzingen/eisen voor functionaliteit van de systemen.

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Auteur(s)
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Titel
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Versie
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Datum
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Bron
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Organisatie
|-
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
|}
'''Referenties

=Bijlage: Documenthistorie=

==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:V2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

{| class="wikitable" "cellpadding="10" style="background-color: white;"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Release
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Versie
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|BITS issue
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black; width:850px;"|Omschrijving

{{ReleaseNotes|package=2019.01 - April|release=1.1.13|issues=3|MM-1025|MM-1003|MM-939}}
{{ReleaseNotes|package=2019.01 - Maart|release=1.1.10|issues=4|MM-997|MM-953|MM-931|MM-657}}
|-
| rowspan = 2 style="background-color: white; | 2019.01 - November
| style="background-color: white; | 1.1.7
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-806 MM-806]
| style="background-color: white;"| Fixed MM-430: adjusted incorrect FHIRPath constraints, moved extension to Consent.extension and moved mappings in extension from extension.value[x].reference to extension.value[x] in zib TreatmentDirective profile.
|-
| style="background-color: white; | 1.1.6
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-430 MM-430]
| style="background-color: white;"| The TreatmentDirective profile allowed at most 1 reference to an AdvanceDirective resource, because of restrictions in the FHIR base. There is now an extension inside the source element to allow referencing additional AdvanceDirective resources.
|-
| style="background-color: white; | 2019.01 - Oktober
| style="background-color: white; | 1.1.5
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-594 MM-594]
| style="background-color: white;"| Updated date time example in profile to include timezone as required by the FHIR specification.
|-
| rowspan = 4 style="background-color: white;"| 2019.01 - September
| rowspan = 4 style="background-color: white;"| 1.1.4
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-358 MM-358]
| style="background-color: white;"| Tekstcorrectie op de kwalificatie pagina ToelichtingKwalificatieGGZ.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-336 MM-336]
| style="background-color: white;"| Aanpassen ConceptMap InterpretatieVlaggenCodelijst-to-observation-interpretation
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-327 MM-327]
| style="background-color: white;"|
Fixed reference to generalPractitioner in examples nl-core-patient-languageProficiency - example.xml and nl-core-patient-legalStatus - example.xml.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-322 MM-322]
| style="background-color: white;"| Aanpassen conceptnaam ResultaatVlaggen naar InterpretatieVlaggen in FHIR profiel voor LaboratoryResults.
|-
| rowspan = 10; style="background-color: white;"| 2019.01
|-
| rowspan = 3; style="background-color: white;"| 1.1.3
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-346 MM-346]
| style="background-color: white;"| Ongeldig discriminator pad in code slicing in zib Verrichting
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-294 MM-294]
| style="background-color: white;"| Naam mapping binnen div. FHIR profielen aangepast conform zib: HCIM LaboratoryTestResult-v4.1(2017EN).
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-252 MM-252]
| style="background-color: white;"| FreedomRestrictingMeasures incorrecte terminologie in profiel en technisch ontwerp pagina
|-
| style="background-color: white;"| 1.1.1
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-206 MM-206]
| style="background-color: white;"| Reference vanuit Observation naar Specimen Isolate onjuist.
|-
| rowspan = 5; style="background-color: white;"| 1.1.0
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-143 MM-143]
| style="background-color: white;"| Aanpassing modellering Procedure.performer in het profiel voor HCIM Verrichting.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-118 MM-118]
| style="background-color: white;"| Profiel naam zib-Product niet passend bij zib FarmaceutischProduct.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-100 MM-100]
| style="background-color: white;"| Mapping CBV naar SNOMED codes.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-99 MM-99]
| style="background-color: white;"| Interval heeft Period maar geen PeriodUnit op simplifier.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-50 MM-50]
| style="background-color: white;"| Contact ondersteunt geen klinische contacten.
|-
| rowspan = 4; style="background-color: white;"| 2018.06
| rowspan = 4; style="background-color: white;"| 1.0.0
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-128 MM-128]
| style="background-color: white;"| CanceledIndicator possible values.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-66 MM-66]
| style="background-color: white;"| Update mappings LaboratoriumUitslag in DiagnosticReport en Observation.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-55 MM-55]
| style="background-color: white;"| Profile for HCIM TobaccoUse was missing a specification for PackYears unit - profile updated to 2.0.1.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-54 MM-54]
| style="background-color: white;"| Wrong SNOMED code in search URL for FunctionalOrMentalStatus in BgZ and GGZ.
|}

==Paginahistorie==
{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Release
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Datum
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor april 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Maart 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Wijzigingen voor maart 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Februari 2020
| style="background-color: white; | 27-02-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Januari 2020
| style="background-color: white; | 27-01-2020
| style="background-color: white;"|
* Wijzigingen voor januari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 10-12-2019
| style="background-color: white;"|
* Wijzigingen voor november patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 28-11-2019
| style="background-color: white;"|
* Wijzigingen voor november patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Oktober
| style="background-color: white; | 30-10-2019
| style="background-color: white;"|
* Wijzigingen voor oktober patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 27-06-2019
| style="background-color: white;"|
* Toevoeging release notes voor patches. Ophogen versie nummers naar 1.1.3.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-04-2019
| style="background-color: white;"|
* Toelichting over de verschillende modules van het VIPP GGZ programma, waarvan de Basisgegevens GGZ 1 module beslaat.
* Toevoeging transactie specificaties op ART-DECOR.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 28-03-2019
| style="background-color: white;"|
* Plaatsen release notes behorende bij patch 1.
* Versienummer systeemrol codes ophogen met 1 patch nummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"|
*Wijzigingen gepubliceerd in versie 2019.01, zie release notes.
*Verplaatsing release notes naar functionele pagina.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 01-11-2018
| style="background-color: white;"|
* Toevoeging verwijzing naar gepubliceerde VIPP GGZ regeling en uitgangspunten voor kwalificatie.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 15-10-2018
| style="background-color: white;"|
* Aanpassing versienummer in titel.
* Toevoeging documenthistorie.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 26-09-2018
| style="background-color: white;"|
* Toevoeging toelichting over de inhoud m.b.t. overlap en verschillen met de Basisgegevensset Zorg (BgZ).
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 10-09-2018
| style="background-color: white;"|
* Eerste conceptversie.
|}

MedMij:Vprepub-2019.01 OntwerpGGZ

2020-05-01T07:42:18Z

Stephan Opdenberg: /* Release notes */

MedMij:V2019.01 OntwerpLangdurigeZorg

2020-05-01T07:41:22Z

Stephan Opdenberg: /* Release notes */

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp Basisgegevens Langdurige Zorg {{VersieInfo|V2019.01|BgLZ}} (op basis van zibs release 2017)}}
{{MedMij:V2019.01_Issuebox}}

[[Bestand:BgLZ-icon.png|link=|links|95px|Use case BgLZ|BgLZ]]
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_BGLZ|Technisch]]
desc none
</imagemap>

=Inleiding=

==Algemeen==
Deze pagina beschrijft het functioneel ontwerp voor de uitwisseling van Basisgegevens Langdurige Zorg (BgLZ) op basis van een selectie zorginformatiebouwstenen (zibs) binnen MedMij. De algemene inleiding van de MedMij functionele ontwerpen kan [[MedMij:V2019.01_Ontwerpen|hier]] gevonden worden.

Binnen het [https://www.dus-i.nl/subsidies/inzicht InZicht programma] (VIPP langdurige zorg) zijn een drietal modules opgenomen.
* Module PGO: de Basisgegevens Langdurige Zorg is bedoeld voor deze module
* Module [https://www.nictiz.nl/standaardisatie/informatiestandaarden/verpleegkundige-overdracht eOverdracht] (gericht op de verpleegkundige overdracht tussen zorgprofessionals)
* Module Medicatieveiligheid: hiervoor wordt verwezen naar het [[MedMij:V2019.01_OntwerpMedicatie| functioneel ontwerp]] voor [https://www.nictiz.nl/programmas/medicatieproces Medicatieproces 9.0].

De Basisgegevens Langdurige Zorg bestaat uit gegevens die relevant zijn voor uitwisseling met patiënten binnen de langdurige zorg via hun [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO). De Basisgegevens Langdurige Zorg vertoont enige overlap met de [https://www.nictiz.nl/standaardisatie/informatiestandaarden/basisgegevensset-zorg-bgz/ Basisgegevensset Zorg (BgZ)] en [https://www.nictiz.nl/standaardisatie/informatiestandaarden/verpleegkundige-overdracht eOverdracht] maar is zeker niet hetzelfde: zie [[MedMij:V2019.01_OntwerpLangdurigeZorg#Informatie| Informatie]] voor een nadere toelichting over het samenstellen van de inhoud.

Het doel van deze pagina is om de uitwisseling van de Basisgegevens Langdurige Zorg met de patiënt te omschrijven.

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de MedMij functionele ontwerpen, die [[MedMij:V2019.01_Ontwerpen#Doelgroep| hier]] gevonden kan worden.

==Kaders en uitgangspunten==
===Richtlijn===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Richtlijn| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

===Specifieke informatie over deze kwalificatie===
Specifieke informatie over de kwalificatie van de transacties 'Raadplegen Langdurige Zorg' en 'Beschikbaarstellen Langdurige Zorg' is [[MedMij:V2019.01_ToelichtingKwalificatieLangdurigeZorg| hier]] te vinden.

=Use Cases=
==Use case 1: Raadplegen Basisgegevens Langdurige Zorg in persoonlijke gezondheidsomgeving==
=== Doel en relevantie ===
Het voor patiënten mogelijk maken regie op hun eigen gezondheid te nemen door inzicht te geven in de Basisgegevens Langdurige Zorg die over henzelf gaan.

=== Domein ===
Basisgegevens Langdurige Zorg in het domein van zorgaanbieders en patiënten.

=== Context ===
Het gaat om het elektronisch en gestructureerd beschikbaar maken van de Basisgegevens Langdurige Zorg vanuit een zorgaanbiederssysteem (XIS) naar een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO).
Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie,
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.

De beschrijving is infrastructuur-onafhankelijk.

=== Informatie ===
De Basisgegevens Langdurige Zorg bestaat uit een selectie van 14 zibs zoals te vinden in dit [[MedMij:V2019.01_InhoudLangdurigeZorg|overzicht]]. Deze zibs vormen samen een verzameling van gegevens die patiënten binnen de langdurige zorg zelf relevant vinden om via hun PGO in te zien, zoals bepaald tijdens een aantal veldverkenningen met zowel patiënten als zorgprofessionals. De Basisgegevens Langdurige Zorg komt voor een deel overeen met de [https://www.nictiz.nl/standaardisatie/informatiestandaarden/basisgegevensset-zorg-bgz/ Basisgegevensset Zorg (BgZ)] en [https://www.nictiz.nl/standaardisatie/informatiestandaarden/verpleegkundige-overdracht/ eOverdracht], maar voor een deel ook niet: het gaat om drie aparte sets. Zie het [[MedMij:V2019.01_InhoudLangdurigeZorg|overzicht van de inhoud]] voor een nadere toelichting.

Medicatiegegevens vallen buiten de Basisgegevens Langdurige Zorg, omdat hiervoor gebruik wordt gemaakt van het reeds bestaande [https://www.nictiz.nl/programmas/medicatieproces Medicatieproces 9.0] (zie [[MedMij:V2019.01_OntwerpMedicatie|uitwisseling medicatiegegevens]] in PGO).

In de MedMij FHIR implementatiegids staat de technische representatie van de betreffende zibs in zogenaamde FHIR profielen. In dit [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2019.01_FHIR_BGLZ#List_of_StructureDefinitions overzicht] is te zien welk FHIR profiel bij welke zib hoort.

=== Bedrijfsrollen ===
Deze use case onderscheidt twee bedrijfsrollen, namelijk de ''Patiënt'' en de ''Zorgaanbieder'' zoals te zien in onderstaande tabel.

{| class="wikitable" "cellpadding="10" width="100%"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Bedrijfsrol'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil de eigen Basisgegevens Langdurige Zorg raadplegen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Stelt de Basisgegevens Langdurige Zorg beschikbaar
|}
'''Bedrijfsrollen Basisgegevens Langdurige Zorg'''

Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd.

[[Image:InzienLZ_activity.PNG|Activiteitendiagram Raadplegen Langdurige Zorg]]

'''Activiteitendiagram Raadplegen Langdurige Zorg'''

=== Procesbeschrijving ===
==== Patient journey - Kenneth van Someren ====
De 'patient journey' van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Kenneth_van_Someren_MedMij.pdf Kenneth van Someren] beschrijft enkele momenten waarop je als patiënt zijnde inzicht kan of zou willen hebben in zijn/haar Basisgegevens Langdurige Zorg.

<blockquote>Op aanraden van zijn dochter heeft Kenneth nu ook een PGO, waarop hij kan zien wanneer de wijkverpleegkundige komt of de huishoudelijke hulp. Als het nodig is kan hij via zijn PGO doorgeven dat hij niet mee eet omdat hij bij een van zijn kinderen eet. De vrijwilligers van de bezorgdienst krijgen dit automatisch doorgegeven.</blockquote>

<blockquote>Hij krijgt een EVV-er (eerst verantwoordelijke verpleegkundige) toegewezen, die samen met Kenneth een zorgleefplan gaat opstellen. Zodra het zorgleefplan compleet is, komt dit beschikbaar in zijn PGO. Daarmee kan Kenneth goed zien welke afspraken er met de instelling zijn gemaakt.</blockquote>

==== Proces ====
Het stuk van het proces waar het in deze use case om gaat is:
* Het systeem van een zorgaanbieder (XIS) stelt de Basisgegevens Langdurige Zorg van de patiënt beschikbaar aan het systeem van een patiënt (PGO).

Deze paragraaf vervolgt met een beschrijving van precondities, proces stappen, en post condities.

===== Preconditie =====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van de Basisgegevens Langdurige Zorg tussen het betreffende XIS en het eigen PGO.

De Basisgegevens Langdurige Zorg, of een gedeelte van de Basisgegevens Langdurige Zorg, welke de persoon wil inzien, bestaat en de zorgaanbieder wil deze beschikbaarstellen.
:Soms zijn er valide redenen om de Basisgegevens Langdurige Zorg, of gedeeltes daarvan, tijdelijk nog niet beschikbaar te stellen aan de patiënt. Bijvoorbeeld omdat de zorgverlener deze eerst zelf wil interpreteren en/of er eerst met de patiënt over wil spreken.
:Een patiënt kan steeds zelf het initiatief nemen om de Basisgegevens Langdurige Zorg op te halen, maar het is ook mogelijk dat een PGO geconfigureerd is om dit 'automatisch' te doen. Dit maakt voor de scope van deze use case beschrijving geen verschil.

===== Processtappen =====
* Het systeem van de patiënt (PGO) raadpleegt het systeem van de zorgaanbieder (XIS) voor de Basisgegevens Langdurige Zorg van de patiënt.
* Het systeem van de zorgaanbieder (XIS) maakt (een deel van) de Basisgegevens Langdurige Zorg beschikbaar voor de patiënt.
* De patiënt gebruikt de persoonlijke gezondheidsomgeving om de Basisgegevens Langdurige Zorg in te zien.

===== Postconditie =====
De persoon kan de Basisgegevens Langdurige Zorg inzien via een persoonlijke gezondheidsomgeving.

=== Systemen & Systeemrollen ===
Zowel de persoon als de zorgaanbieder maken ieder gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om de Basisgegevens Langdurige Zorg van zorgaanbieder naar de persoon.

{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Systeem
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Naam systeemrol
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Systeemrolcode
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| LZRaadplegend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|BgLZ}}-LZR-FHIR
| style="background-color: white;"| Raadplegen Basisgegevens Langdurige Zorg bij zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| LZBeschikbaarstellend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|BgLZ}}-LZB-FHIR
| style="background-color: white;"| Beschikbaarstellen Basisgegevens Langdurige Zorg aan de patiënt
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:InzienLZ_component.PNG|Componenten diagram]]

'''Componenten diagram van systemen en systeemrollen'''

=== Transacties & Transactiegroepen ===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Transactiegroep'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Transactie'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Systeemrolcode'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Systeem'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Bedrijfsrol'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:middle;" rowspan="2"|Basisgegevens Langdurige Zorg (PULL)
|style="background-color: white;vertical-align:top;"|[https://decor.nictiz.nl/decor/services/RetrieveTransaction?id=2.16.840.1.113883.2.4.3.11.60.58.4.2&effectiveDate=2019-04-09T16:33:35&language=*&ui=nl-NL&version=2019-09-04T10:21:41&format=html&hidecolumns=34567 Raadplegen Basisgegevens Langdurige Zorg]
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|BgLZ}}-LZR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_BGLZ|Basisgegevens Langdurige Zorg in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|[https://decor.nictiz.nl/decor/services/RetrieveTransaction?id=2.16.840.1.113883.2.4.3.11.60.58.4.3&effectiveDate=2019-04-09T16:33:35&language=*&ui=nl-NL&version=2019-09-04T10:21:41&format=html&hidecolumns=34567 Beschikbaarstellen Basisgegevens Langdurige Zorg]
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|BgLZ}}-LZB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:InzienLZ_usecase.PNG|Use case diagram raadplegen Basisgegevens Langdurige Zorg]]

'''Use case diagram raadplegen Basisgegevens Langdurige Zorg

=Functionaliteit=
Er zijn geen aanwijzingen/eisen voor functionaliteit van de systemen.

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="text-align:left;"|Auteur(s)
!style="text-align:left;"|Titel
!style="text-align:left;"|Versie
!style="text-align:left;"|Datum
!style="text-align:left;"|Bron
!style="text-align:left;"|Organisatie
|-
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
|}

=Bijlage: Documenthistorie=

==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

{| class="wikitable" "cellpadding="10" style="background-color: white"
!style="text-align:left;"|Release
!style="text-align:left;"|Versie
!style="text-align:left;"|BITS issue
!style="width:850px; text-align:left;"|Omschrijving

{{ReleaseNotes|package=2019.01 - April|release=1.0.9|issues=3|MM-1059|MM-1025|MM-939}}
{{ReleaseNotes|package=2019.01 - Maart|release=1.0.7|issues=3|MM-997|MM-953|MM-931}}
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 1.0.4
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-806 MM-806]
| style="background-color: white;"| Fixed MM-430: adjusted incorrect FHIRPath constraints, moved extension to Consent.extension and moved mappings in extension from extension.value[x].reference to extension.value[x] in zib-TreatmentDirective profile.
|-
| style="background-color: white; | 2019.01 - Oktober
| style="background-color: white; | 1.0.2
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-599 MM-599]
| style="background-color: white;"| URL value on detailCodeableConcept.coding.system in HCIM TreatmentObjective example was incorrect, changed to the correct value.
|-
| style="background-color: white; | 2019.01 - September
| style="background-color: white; | 1.0.1
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-358 MM-358]
| style="background-color: white;"| Tekstcorrectie op de kwalificatiepagina's van BgZ, GGZ en BgLZ.
|}

==Paginahistorie==
{| class="wikitable" "cellpadding="10" style="background-color: white;
!style="text-align:left;"|Release
!style="text-align:left;"|Datum
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor april 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Maart 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Wijzigingen voor maart 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Februari 2020
| style="background-color: white; | 27-02-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Januari 2020
| style="background-color: white; | 27-01-2020
| style="background-color: white;"|
* Wijzigingen voor januari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 10-12-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 28-11-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Oktober
| style="background-color: white; | 30-10-2019
| style="background-color: white;"|
* Wijzigingen voor oktober patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 05-09-2019
| style="background-color: white;"|
* Versie van v0.1.0 (openbare consultatie) naar v1.0.0 (definitieve versie).
* Transactie links aangepast naar ART-DECOR publicatie versie.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 20-05-2019
| style="background-color: white;"|
* Eerste versie van de BgLZ toegevoegd aan de 2019.01 release voor openbare consultatie.
|}

MedMij:Vprepub-2019.01 OntwerpLangdurigeZorg

2020-05-01T07:41:22Z

Stephan Opdenberg: /* Release notes */

MedMij:V2019.01 OntwerpZelfmetingen

2020-05-01T07:39:59Z

Stephan Opdenberg: /* Release notes */

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp Zelfmetingen {{VersieInfo|V2019.01|Zelfmetingen}}}}
{{MedMij:V2019.01_Issuebox}}

[[Bestand:Self-Measuements_zonder_tekst.png |link=|links |85px|Zelfmetingen]]
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_VitalSigns|Technisch]]
desc none
</imagemap>

=Inleiding=
==Algemeen==
Deze pagina beschrijft use cases voor de patiënt in relatie tot zelfmetingen van vitale functies die een patiënt kan verzamelen en delen door middel van een PGO. De vitale functies van de mens zijn de lichaamsfuncties die de persoon vitaal of ook wel in leven houden, voorbeelden zijn ademhaling en circulatie (hartslag en bloeddruk).

Momenteel bestaat er geen standaard voor zelfmeet gegevens van de vitale functies. Het doel van deze pagina is om verschillende uitwisseling scenario's van zelfmeet gegevens met de patiënt te beschrijven voor gebruik in MedMij.

Zoals [[MedMij:V2019.01_Ontwerpen|op deze pagina]] aangegeven, gebruikt MedMij zorginformatiebouwstenen (zibs) als leidraad voor de inhoud van informatie uitwisseling. Voor uitwisseling van zelfmeet gegevens gaat het om de volgende zibs:

*Patiënt
*Ademhaling
*Bloeddruk
*Glucose (gebaseerd op zib LaboratoriumUitslag)
*Hartfrequentie
*Lichaamsgewicht
*Lichaamslengte
*Lichaamstemperatuur
*O2Saturatie
*Polsfrequentie

PGO-leveranciers dienen de beschikbare zibs en/of FHIR profielen te gebruiken. Als er geen specifieke zib en/of FHIR profiel beschikbaar is, gebruik dan zib AlgemeneMeting of LaboratoriumUitslag.

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de MedMij functionele ontwerpen, die [[MedMij:V2019.01_Ontwerpen#Doelgroep| hier]] gevonden kan worden.

==Kaders en uitgangspunten==
===Richtlijn===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Richtlijn| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

===Specifieke informatie over deze kwalificatie===
De kwalificatie richt zich vooralsnog op: bloeddruk, lichaamsgewicht en glucose. Deze dienen minimaal te worden ondersteund. De verwachting is dat leveranciers zoveel mogelijk zelfmetingen ondersteunen.

=Use Cases=
==Use case: Raadplegen metingen betreffende de vitale functies door patiënt==
===Doel en relevantie===
Het voor patiënten mogelijk maken regie op hun eigen gezondheid te nemen door inzicht te geven in de vitale functie meetwaarden die over henzelf gaan.
===Domein===
Metingen betreffende vitale functies in het domein van zorgaanbieders en patiënten.

===Context===
Het gaat om het elektronisch en gestructureerd beschikbaar maken van de meetwaarden van vitale functies vanuit een zorgaanbiederssysteem (XIS) naar een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO).
Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.
De beschrijving is infrastructuur-onafhankelijk.

===Informatie===
De informatie-elementen die van toepassing zijn.

====Raadplegen meetwaarden ====
Informatie elementen in de vraag om meetwaarden van vitale functies.

* Patient identificatienummer
* Periode (startdatum - einddatum)
* Type (soort meetwaarden, bijvoorbeeld bloeddruk)

Dit betreft de filtermogelijkheden (query paramaters) in de vraag om meetwaarden van de vitale functies.

====Beschikbaarstellen meetwaarden====
Informatie elementen in meetwaarden van vitale functies staan hieronder. Het betreffen de Zorginformatiebouwstenen die te vinden zijn op https://zibs.nl/wiki/ZIB_Hoofdpagina.

*Patiënt
*Ademhaling
*Bloeddruk
*Glucose (gebaseerd op zib LaboratoriumUitslag)
*Hartfrequentie
*Lichaamsgewicht
*Lichaamslengte
*Lichaamstemperatuur
*O2Saturatie
*Polsfrequentie

PGO-leveranciers dienen de beschikbare zibs en/of FHIR profielen te gebruiken. Als er geen specifieke zib en/of FHIR profiel beschikbaar is, gebruik dan zib AlgemeneMeting of LaboratoriumUitslag.

=== Bedrijfsrollen ===
Deze use case kent twee bedrijfsrollen.

{| class="wikitable" "cellpadding="10" width="50%"
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil meetwaarden van vitale functies raadplegen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Stelt meetwaarden van vitale functies beschikbaar
|}
'''Bedrijfsrollen Medicatieoverzicht'''

Onderstaande afbeelding toont de bedrijfsrollen en de activiteiten die zij uitvoeren.

[[Bestand:Activity_Diagram_-_MVF_raadplegen.jpg|Activiteitendiagram Raadplegen Meetwaarden vitale functies]]

'''Activiteitendiagram Raadplegen meetwaarden vitale functies'''

===Procesbeschrijving===
===='Patient journey' - Thomas van Beek ====
Het verhaal van de 'patient journey' van Thomas van Beek vindt u [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Thomas_van_Beek_MedMij.pdf hier]. Hieronder een voor Thomas relevante situatie waarbij het raadplegen van meetwaarden betreffende de vitale functie een rol speelt.

<blockquote>Voordat Thomas zijn consult bij de internist heeft om de resultaten door te spreken worden er een aantal andere waarden getest. Zijn gewicht en zijn bloeddruk worden opgemeten. De laboratoriumwaarden zijn al bekend voordat de internist ze aan Thomas mee kan delen. Alhoewel Thomas zoals gezegd zo min mogelijk met zijn ziekte bezig wil zijn, vindt hij de jaarlijkse controle heel belangrijk. Hij vindt het dan ook heel erg handig om de resultaten van de onderzoeken een dag van tevoren al in te zien in zijn PGO. Hij kan zich zo goed voorbereiden en zal niet meer verrast zijn over de resultaten als zijn internist deze voorlegt.</blockquote>

===='Patient journey' - Roos Dalstra ====
Het verhaal van de 'patient journey' van Roos Dalstra vindt u [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Roos_Dalstra_MedMij.pdf hier]. Hieronder een voor Roos relevante situatie waarbij het raadplegen van meetwaarden betreffende de vitale functie een rol speelt.

<blockquote>Na het ontslag komt de informatie over de opnameperiode vanuit het ziekenhuis beschikbaar in de PGO, zodat zij een goed beeld heeft van haar opname en haar medicatie. Dit kan zij ook delen met haar naasten</blockquote>

Roos kan na haar opname haar vitale waarden gemeten in ziekenhuis raadplegen. Zo beschikt zij over deze informatie die ze als referentiewaarden kan gebruiken.

====Proces====
Het stuk van het proces waar het in deze use case om gaat is:
*Het systeem van een zorgaanbieder (XIS) stelt de gevraagde meetwaarden van de vitale functies beschikbaar aan het systeem van een patiënt (PGO).
Deze paragraaf vervolgt met een beschrijving van precondities, proces stappen, en post condities.
=====Preconditie=====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van vitale functie meetwaarden tussen het betreffende XIS en de eigen persoonlijke gezondheidsomgeving.

De patiënt wil de meetwaarden van de vitale functies inzien en de zorgaanbieder stelt dit ook beschikbaar.
:Een patiënt kan steeds zelf het initiatief nemen om de meetwaarden op te halen, maar het is ook mogelijk dat een PGO geconfigureerd is om dit 'automatisch' te doen. Dit maakt voor de beschrijving van deze use case geen verschil.

=====Proces stappen=====
*Het systeem van de patiënt (PGO) stuurt meetwaarden van de vitale functies naar een XIS.
*Het systeem van de zorgaanbieder (XIS) ontvangt meetwaarden van de vitale functies op voor de patiënt.
*De zorgverlener gebruikt zijn systeem om de meetwaarden van de vitale functies in te zien.

=====Post conditie=====
De patiënt heeft de meetwaarden vitale functies geraadpleegd via de persoonlijke gezondheidsomgeving.

=== Systemen & Systeemrollen ===
Zowel zorgaanbieder als patiënt maken gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)
Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om de meetwaarden vitale functies van zorgaanbieder naar de patiënt.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| MeetwaardenVitaleFunctiesRaadplegend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Zelfmetingen}}-MVR-FHIR
| style="background-color: white;"| Raadplegen meetwaarden vitale functies bij zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| MeetwaardenVitaleFunctiesBeschikbaarstellend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Zelfmetingen}}-MVB-FHIR
| style="background-color: white;"| Beschikbaarstellen meetwaarden vitale functies aan de patiënt
|-
|}
Zie ook onderstaande afbeelding.

[[Bestand:Component_Diagram_-_MVF_raadplegen_(Totaal).jpg|Componenten diagram]]

'''Componenten diagram'''

De kwalificatie van informatiesystemen vindt plaats op basis van systeemrollen.

=== Transacties, Transactiegroepen en systeemrollen===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|Meetwaarden Vitale Functies(PULL)
|style="background-color: white;vertical-align:top;"|Raadplegen meetwaarden vitale functies
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Zelfmetingen}}-MVR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_VitalSigns|Meetwaarden vitale functies in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen meetwaarden vitale functies
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Zelfmetingen}}-MVB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:Use_Case_Diagram_-_MVF_raadplegen.jpg|Use case diagram raadplegen meetwaarden vitale functies]]

'''Use case diagram

==Use case: Sturen zelfmetingen van de vitale functies door patiënt==
===Doel en relevantie===
Het voor patiënten mogelijk maken regie op hun eigen gezondheid te nemen door het kunnen delen van hun zelfmeet gegevens met de zorgverlener.
===Domein===
Zelfmetingen betreffende vitale functies in het domein van zorgaanbieders en patiënten.

===Context===
Het gaat om het elektronisch en gestructureerd beschikbaar maken van de zelfmeetwaarden van vitale functies vanuit een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO) naar een zorgaanbiederssysteem (XIS) .
Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.
De beschrijving is infrastructuur-onafhankelijk.

===Informatie===
De informatie-elementen die van toepassing zijn.
====Beschikbaarstellen meetwaarden====
Informatie elementen in meetwaarden van vitale functies staan hieronder. Het betreffen de Zorginformatiebouwstenen die te vinden zijn op https://zibs.nl/wiki/ZIB_Hoofdpagina.

*Patiënt
*Ademhaling
*Bloeddruk
*Glucose (gebaseerd op zib LaboratoriumUitslag)
*Hartfrequentie
*Lichaamsgewicht
*Lichaamslengte
*Lichaamstemperatuur
*O2Saturatie
*Polsfrequentie

PGO-leveranciers dienen de beschikbare zibs en/of FHIR profielen te gebruiken. Als er geen specifieke zib en/of FHIR profiel beschikbaar is, gebruik dan zib AlgemeneMeting of LaboratoriumUitslag.

====Ontvangen zelfmetingen====
Het ontvangende systeem stuurt een ontvangstbevestiging van de zelfmetingen.

=== Bedrijfsrollen ===
Deze use case kent twee bedrijfsrollen.

{| class="wikitable" "cellpadding="10" width="50%"
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil zelfmetingen van vitale functies sturen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Ontvangt zelfmetingen van vitale functies
|}
'''Bedrijfsrollen Medicatieoverzicht'''

Onderstaande afbeelding toont de bedrijfsrollen en de activiteiten die zij uitvoeren.

[[Bestand:Activity_Diagram_-_MVF_sturen.jpg|Activiteitendiagram Raadplegen Meetwaarden vitale functies]]

'''Activiteitendiagram sturen zelfmetingen vitale functies'''

===Procesbeschrijving===
===='Patient journey' - Roos Dalstra ====
Het verhaal van de 'patient journey' van Roos Dalstra vindt u [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Roos_Dalstra_MedMij.pdf hier].

Hieronder een voor Roos relevante situatie waarbij het sturen van zelfmetingen betreffende de vitale functie een rol speelt.

<blockquote>Sinds een aantal maanden maakt Roos gebruik van een online persoonlijke gezondheidsomgeving. Daarin houdt ze onder andere haar bloedglucosewaarden bij. Daarnaast moet ze zich dagelijks wegen in verband met haar hartfalen. Bij hartfalen is de pompfunctie van het hart verminderd. Het hart pompt niet genoeg bloed rond, hierdoor kun je vocht vasthouden. Om dit te monitoren weegt Roos zich dagelijks, en houdt ze haar gewicht bij in haar persoonlijke gezondheidsomgeving. Wanneer haar gewicht toeneemt, dan krijgt ze een signaal vanuit haar PGO, omdat dit zou kunnen duiden op het vasthouden van vocht. Doordat Roos de huisarts toestemming heeft gegeven om haar gegevens te delen kan informatie worden uitgewisseld. Als er bijvoorbeeld iets in de medicatie wordt gewijzigd, dan ziet Roos dit in haar persoonlijke gezondheidsomgeving terug. De huisarts kan op zijn beurt de gegevens die Roos heeft ingevoerd bekijken, bijvoorbeeld met een handige grafiek die haar bloedsuikers over de afgelopen periode laat zien</blockquote>

====Proces====
Het stuk van het proces waar het in deze use case om gaat is:
*Het systeem van een patiënt (PGO) stelt zelfmetingen van de vitale functies beschikbaar aan het systeem van een zorgaanbieder (XIS).
Deze paragraaf vervolgt met een beschrijving van precondities, proces stappen, en post condities.
=====Preconditie=====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van zelfmetingen van de vitale functies tussen het betreffende XIS en de eigen persoonlijke gezondheidsomgeving.

De zorgaanbieder wil de zelfmetingen van de vitale functies inzien en de patiënt stelt dit ook beschikbaar.
:Een patiënt kan steeds zelf het initiatief nemen om de meetwaarden te sturen, maar het is ook mogelijk dat een PGO geconfigureerd is om dit 'automatisch' te doen. Dit maakt voor de beschrijving van deze use case geen verschil.

=====Proces stappen=====
*Het systeem van de patiënt (PGO) stuurt zelfmetingen van de vitale functies naar een XIS.
*Het systeem van de zorgaanbieder (XIS) ontvangt en verwerkt de zelfmetingen van de patiënt.
*De zorgaanbieder gebruikt de het XIS om de zelfmetingen van de vitale functies in te zien.

=====Post conditie=====
De patiënt heeft zelfmetingen gestuurd via de persoonlijke gezondheidsomgeving.

=== Systemen & Systeemrollen ===
Zowel zorgaanbieder als patiënt maken gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om de meetwaarden vitale functies van zorgaanbieder naar de patiënt.

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om zelfmetingen vitale functies van patiënt naar zorgaanbieder.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| ZelfmetingenVitaleFunctiesSturend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Zelfmetingen}}-ZVS-FHIR
| style="background-color: white;"| Sturen zelfmetingen vitale functies naar zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| ZelfmetingenVitaleFunctiesOntvangend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Zelfmetingen}}-ZVO-FHIR
| style="background-color: white;"| Ontvangen zelfmetingen vitale functies van de patiënt
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:Component_Diagram_-_MVF_sturen_(Totaal).jpg|Componenten diagram]]

'''Componenten diagram'''

De kwalificatie van informatiesystemen vindt plaats op basis van systeemrollen.

=== Transacties, Transactiegroepen en systeemrollen===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|Zelfmetingen Vitale Functies(PUSH)
|style="background-color: white;vertical-align:top;"|Sturen zelfmetingen van vitale functies
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Zelfmetingen}}-ZVS-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|-
|style="background-color: white;vertical-align:top;"|Ontvangen zelfmetingen vitale functies
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Zelfmetingen}}-ZVO-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:Use_Case_Diagram_-_MVF_sturen.jpg|Use case diagram sturen zelfmetingen vitale functies]]

'''Use case diagram

=Functionaliteit=
Er zijn geen aanwijzingen/eisen voor functionaliteit van de systemen.

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="text-align:left;"|Auteur(s)
!style="text-align:left;"|Titel
!style="text-align:left;"|Versie
!style="text-align:left;"|Datum
!style="text-align:left;"|Bron
!style="text-align:left;"|Organisatie
|-
| style="background-color: white;"| AUTEUR(S)
| style="background-color: white;"| TITEL
| style="background-color: white;"| VERSIE
| style="background-color: white;"| DATUM
| style="background-color: white;"| BRON
| style="background-color: white;"| ORGANISATIE
|}
'''Referenties

=Bijlage: Documenthistorie=
==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:V2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

{| class="wikitable" "cellpadding="10" style="background-color: white;"
!style="text-align:left;"|Release
!style="text-align:left;"|Versie
!style="text-align:left;"|BITS issue
!style="width:1500px; text-align:left;"|Omschrijving
{{ReleaseNotes|package=2019.01 - April 2020|release=1.2.13|issues=2|MM-1017|MM-949}}
|-
| rowspan = 1; style="background-color: white; | 2019.01 - Januari 2020
| rowspan = 1; style="background-color: white; | 1.2.7
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-833 MM-833]
| style="background-color: white;"| Added known issue to SelfMeasurements FHIR IG regarding incorrect use of BloodGlucose LOINC code.
|-
| rowspan = 2; style="background-color: white; | 2019.01 - September
| rowspan = 2; style="background-color: white; | 1.2.3
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-436 MM-436]
| style="background-color: white;"| Aanpassen ConceptMap InterpretatieVlaggenCodelijst-to-observation-interpretation.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-422 MM-422]
| style="background-color: white;"| Aanpassen conceptnaam ResultaatVlaggen naar InterpretatieVlaggen in FHIR profiel voor LaboratoryResults.
|-
| rowspan = 6; style="background-color: white;"| 2019.01
| style="background-color: white;"| 1.2.1
| style="background-color: white;"| [https://bits.nictiz.nl/projects/MM/issues/MM-185 MM-185]
| style="background-color: white;"| Verkeerde fixed value voor Observation.code.coding:postBreakfastGlucoseNhgtable45.code
|-
| rowspan = 5; style="background-color: white;"| 1.2.0
| style="background-color: white;"| [https://bits.nictiz.nl/projects/MM/issues/MM-175 MM-175]
| style="background-color: white;"| Mapping concept Positie van Zib Lichaamslengte niet duidelijk.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/projects/MM/issues/MM-314 MM-314]
| style="background-color: white;"| Zelfmeting pijnscore FHIR.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/projects/MM/issues/MM-147 MM-147]
| style="background-color: white;"| Mappen PulseRegularity binnen PulseRate.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-141 MM-141]
| style="background-color: white;"| Vital Signs profielen inconsistent m.b.t. baseDefinition.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/projects/MM/issues/MM-95 MM-95]
| style="background-color: white;"| Added support for the lastn operation for retrieving the latest available measurement.
|-
| rowspan = 4; style="background-color: white;"| 2018.06
| rowspan = 4; style="background-color: white;"| 1.1.0
| style="background-color: white;"| [https://bits.nictiz.nl/projects/MM/issues/MM-87 MM-87]
| style="background-color: white;"| The links in the table for FHIR profiles have been updated. The BloodGlucose profile in the Retrieve Vital Signs use case and all profiles under the Send Vital Signs use case linked to a deprecated version.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/projects/MM/issues/MM-80 MM-80]
| style="background-color: white;"| The profile mapping for HCIM element NL-CM:12.6.2 TemperatuurType has been updated Observation.method from Observation.bodySite based on feedback received from the ZIB Centrum that even though the definition appears to point to a body site, that the focus of TemperatureType is a method that includes body site. The profile version was updated to 2.0.1
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-66 MM-66]
| style="background-color: white;"| Update mappings LaboratoriumUitslag in DiagnosticReport en Observation.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/projects/MM/issues/MM-64 MM-64]
| style="background-color: white;"| Koppelen van meetinstrument aan relevante profielen.
|}

==Paginahistorie==
{| class="wikitable" "cellpadding="10" style="background-color: white;
!style="text-align:left;"|Release
!style="text-align:left;"|Datum
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - April 2020
| style="background-color: white; | 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - March 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Februari 2020
| style="background-color: white; | 27-02-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Januari 2020
| style="background-color: white; | 27-01-2020
| style="background-color: white;"|
* Wijzigingen voor januari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 10-12-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 28-11-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Oktober
| style="background-color: white;"| 30-10-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 21-06-2019
| style="background-color: white;"|
* Verduidelijking FO m.b.t. glucose meting. Zie [https://bits.nictiz.nl/browse/MM-333 MM-333] voor meer info.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 28-03-2019
| style="background-color: white;"|
* Plaatsen release notes behorende bij patch 1.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"|
* Wijzigingen gepubliceerd in versie 2019.01, zie release notes.
* Verplaatsing release notes naar functionele pagina.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"| Pijnscore verwijderd uit lijst van toegepaste Zibs voor deze use case. Voor Pijnscore is nog geen FHIR documentatie beschikbaar.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 10-01-2019
| style="background-color: white;"|
* Aanpassing versienummer naar 1.1.0.
* Wijzigingen doorgevoerd betreffende BITS issue MM-80 en MM-87.
* Kwalificatieparagraaf aangevuld.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 15-10-2018
| style="background-color: white;"|
* Aanpassing versienummer in titel.
* Toevoeging documenthistorie.
|}

MedMij:Vprepub-2019.01 OntwerpZelfmetingen

2020-05-01T07:39:59Z

Stephan Opdenberg: /* Release notes */

MedMij:V2019.01 OntwerpBGZ 2017

2020-05-01T07:38:28Z

Stephan Opdenberg: /* Release notes */

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp BgZ {{VersieInfo|V2019.01|BgZ}} (op basis van zibs release 2017)}}
{{MedMij:V2019.01_Issuebox}}

[[Bestand:BGZ_icoon.png |link=|links |87px|Use case BgZ|Patient Summary (BgZ)]]
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_BGZ_2017|Technisch]]
desc none
</imagemap>

=Inleiding=

==Algemeen==
Deze pagina beschrijft het functioneel ontwerp voor de Basisgegevensset Zorg binnen MedMij.

De [https://www.registratieaandebron.nl/wat-is-registreren-aan-de-bron/de-kern-van-registreren-aan-de-bron/basisgegevensset/ Basisgegevensset Zorg], ofwel BgZ, is de minimale set van patiëntgegevens die specialisme, ziektebeeld en beroepsgroep overstijgend relevant is en die van belang is voor de continuïteit van zorg en is in Nederland door [https://www.registratieaandebron.nl 'Registratie aan de Bron'] gedefinieerd. Deze set aan patiëntgegevens wordt door alle zorgverleners hetzelfde vastgelegd. Hierdoor wordt uitwisseling van deze gegevens mogelijk gemaakt. De BgZ is gespiegeld aan de Europese Patient Summary.

De bekende use cases voor het uitwisselen van de BgZ zijn gericht op uitwisseling tussen zorgverleners voor spoedeisende hulp of ongeplande zorg. Tot op heden is uitwisseling vanuit het perspectief van de patiënt niet beschreven. Het doel van deze pagina is om de uitwisseling van de BgZ met de patiënt toe te voegen.

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de [[MedMij:V2019.01_Ontwerpen#Doelgroep| MedMij functionele ontwerpen]].

==Kaders en uitgangspunten==
===Richtlijn===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Richtlijn| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

===Specifieke informatie over deze kwalificatie===
Specifieke informatie over de kwalificatie van de transacties 'Raadplegen BgZ' en 'Beschikbaarstellen BgZ' is te vinden in [[MedMij:V2019.01_ToelichtingKwalificatieBgZ|Toelichting Kwalificatie BgZ]].

=Use Cases=
==Use case 1: Raadplegen Basisgegevensset Zorg in persoonlijke gezondheidsomgeving==
=== Doel en relevantie ===
Het voor patiënten mogelijk maken regie op hun eigen gezondheid te nemen door inzicht te geven in gegevens uit de Basisgegevensset Zorg (BgZ) die over henzelf gaan.

=== Domein ===
Basisgegevensset Zorg in het domein van zorgaanbieders en patiënten.

=== Context ===
Het gaat om het elektronisch en gestructureerd beschikbaar maken van de BgZ vanuit een zorgaanbiederssysteem (XIS) naar een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO).
Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie,
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.

De beschrijving is infrastructuur-onafhankelijk.

=== Informatie ===
De [https://www.registratieaandebron.nl/pdf/BgZ_specificatie_obv_zibs_2017_v1.1.pdf BgZ op basis van zibs release 2017] bestaat uit een selectie van 28 [https://zibs.nl/wiki/ZIB_Publicatie_2017(NL) zibs]. Deze zibs vormen samen een verzameling van patiëntgegevens die minimaal nodig is om patiënten continuïteit van zorg te kunnen bieden.

Deze use case gebruikt de structuur van 18 secties die is aangebracht in BgZ 2017. Hierin zijn de onderdelen gegroepeerd waaruit de BgZ is opgebouwd. Deze secties komen sterk overeen met de secties van [https://www.nictiz.nl/wp-content/uploads/2012/09/Alles-wat-je-wilt-weten-over-CCR-CCD-v1-0.pdf CCR/CCD] en maken het o.a. mogelijk om in de technische implementatie (bv FHIR) structuur aan te brengen. In de [[MedMij:V2019.01_FHIR_IG | MedMij FHIR implementatie gids]] staat de technische representatie van de betreffende zibs in zogenaamde FHIR profielen. In dit [[MedMij:V2019.01_FHIR_BGZ_2017#List_of_StructureDefinitions | overzicht]] is te zien welk FHIR profiel bij welke zib hoort.

Voor het gebruik van codestelsel geldt de [[MedMij:V2019.01_Ontwerpen#Richtlijn|algemene richtlijn]].

====Raadplegen BgZ====
Er zijn geen specifieke filtermogelijkheden (query parameters) gedefinieerd voor de BgZ. Bij het raadplegen van de BgZ wordt om alle gegevens behorende bij de patiënt gevraagd.

====Beschikbaarstellen BgZ====
Informatie-elementen in de BgZ staan hieronder. Deze informatie is ook in een [https://decor.nictiz.nl/pub/bgz2017/bgz2017-html-20190313T152910/tr-2.16.840.1.113883.2.4.3.11.60.42.4.37-2018-08-30T093049.html nieuw tabblad] te openen. Bij het beschikbaarstellen van de BgZ worden alle beschikbare gegevens behorende bij de patiënt beschikbaargesteld.

<html>
<iframe width="100%" height="800" src=https://decor.nictiz.nl/pub/bgz2017/bgz2017-html-20190313T152910/tr-2.16.840.1.113883.2.4.3.11.60.42.4.37-2018-08-30T093049.html frameborder="0" align="middle"></iframe>
</html>

=== Bedrijfsrollen ===
Deze use case onderscheidt twee bedrijfsrollen, namelijk de ''Patiënt'' en de ''Zorgaanbieder'' zoals te zien in onderstaande tabel.

{| class="wikitable" "cellpadding="10" width="100%"
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt (PGO)
|style="background-color: white;vertical-align:top;"|Wil de eigen BgZ raadplegen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder (XIS)
|style="background-color: white;vertical-align:top;"|Stelt de BgZ beschikbaar
|}


Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd.

[[Bestand:InzienBGZ activity.PNG|Activiteitendiagram Raadplegen BgZ]]


=== Procesbeschrijving ===
==== Patient journey - Thomas van Beek ====
De 'patient journey' van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Thomas_van_Beek_MedMij.pdf Thomas van Beek] beschrijft enkele momenten waarop je als patiënt zijnde inzicht kan of zou willen hebben in zijn/haar BgZ.

<blockquote>Voor zijn afstuderen verhuist Thomas 9 maanden naar Groningen. Hij gaat daar bij een heel leuk bedrijf stagelopen. Om het voor hem makkelijk te maken en omdat hij een arts dicht in de buurt wil hebben, schrijft hij zich in bij het ziekenhuis in Groningen. Hiervoor moet het ziekenhuis in Amsterdam alle gegevens van Thomas overdragen aan het ziekenhuis in Groningen. Zo weet de nieuwe arts van Thomas precies wat het verloop van de diabetes is. Thomas is zelf eigenlijk wel nieuwsgierig naar zijn medische gegevens die verstuurd worden. In zijn PGO vindt hij de belangrijkste gegevens die over hem bekend zijn.</blockquote>

==== Proces ====
Het stuk van het proces waar het in deze use case omgaat is:
* Het systeem van een zorgaanbieder (XIS) stelt de BgZ van de patiënt beschikbaar aan het systeem van een patiënt (PGO).

Deze paragraaf vervolgt met een beschrijving van precondities, proces stappen, en post condities.

===== Preconditie =====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van de BgZ tussen het betreffende XIS en het eigen PGO.

De BgZ, of een gedeelte van de BgZ, welke de persoon wil inzien, bestaat en de zorgaanbieder (XIS) wil deze beschikbaarstellen.
:Soms zijn er valide redenen om de BgZ, of gedeeltes daarvan, tijdelijk nog niet beschikbaar te stellen aan de patiënt. Bijvoorbeeld omdat de zorgverlener deze eerst zelf wil interpreteren en/of er eerst met de patiënt over wil spreken.
:Een patiënt kan steeds zelf het initiatief nemen om de BgZ op te halen, maar het is ook mogelijk dat een PGO geconfigureerd is om dit 'automatisch' te doen. Dit maakt voor de scope van deze use case beschrijving geen verschil.

===== Proces stappen =====
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Stap
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 01
| style="background-color: white;"| Het systeem van de patiënt (PGO) raadpleegt het systeem van de zorgaanbieder (XIS) voor de BgZ van de patiënt.
|-
| style="background-color: white;"| 02
| style="background-color: white;"| Het systeem van de zorgaanbieder (XIS) maakt (een deel van) de BgZ beschikbaar voor de patiënt.
|-
| style="background-color: white;"| 03
| style="background-color: white;"| De patiënt gebruikt de persoonlijke gezondheidsomgeving (PGO) om de BgZ in te zien.
|}

===== Post conditie =====
De persoon kan de Basisgegevensset Zorg inzien via een persoonlijke gezondheidsomgeving (PGO).

=== Systemen & Systeemrollen ===
Zowel patiënt als zorgaanbieder maken ieder gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om de BgZ van zorgaanbieder naar de patiënt.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| BGZRaadplegend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|BgZ}}-BZR-FHIR
| style="background-color: white;"| Raadplegen BgZ bij zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| BGZBeschikbaarstellend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|BgZ}}-BZB-FHIR
| style="background-color: white;"| Beschikbaarstellen BgZ aan de patiënt
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:InzienBGZ_componenten.PNG|Componenten diagram]]


=== Transacties & Transactiegroepen ===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:middle;" rowspan="2"|BgZ (PULL)
|style="background-color: white;vertical-align:top;"|Raadplegen BgZ
|style="background-color: white;vertical-align:top;"|[[MedMij:Register_van_informatiestandaarden#Register_van_Informatiestandaarden|MM-{{VersieInfo|V2019.01|BgZ}}-BZR-FHIR]]
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_BGZ_2017|BgZ in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen BgZ
|style="background-color: white;vertical-align:top;"|[[MedMij:Register_van_informatiestandaarden#Register_van_Informatiestandaarden|MM-{{VersieInfo|V2019.01|BgZ}}-BZB-FHIR]]
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:InzienBGZ_useCase.PNG|Use case diagram inzien BgZ]]


=Functionaliteit=
Er zijn geen aanwijzingen/eisen voor functionaliteit van de systemen.

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="text-align:left;"|Auteur(s)
!style="text-align:left;"|Titel
!style="text-align:left;"|Versie
!style="text-align:left;"|Datum
!style="text-align:left;"|Bron
!style="text-align:left;"|Organisatie
|-
| style="background-color: white;"| -
| style="background-color: white;"| Basisgegevensset Zorg
| style="background-color: white;"| -
| style="background-color: white;"| 12-08-2019
| style="background-color: white;"| [https://www.registratieaandebron.nl/alles-over-de-bgz/de-basisgegevensset-zorg Alles over de BgZ]
| style="background-color: white;"| Registratie aan de bron (RadB)
|-
| style="background-color: white;"| -
| style="background-color: white;"| BgZ - specificatie gebaseerd op zibs release 2017
| style="background-color: white;"| 1.1
| style="background-color: white;"| 19-04-2018
| style="background-color: white;"| [https://www.registratieaandebron.nl/pdf/BgZ_specificatie_obv_zibs_2017_v1.1.pdf BgZ - specificatie gebaseerd op zibs release 2017]
| style="background-color: white;"| Registratie aan de bron (RadB)
|-
| style="background-color: white;"| Albert-Jan Spruyt & Jan A. Hazelzet
| style="background-color: white;"| Alles wat je wilt (moet) weten over CCR/CCD
| style="background-color: white;"| 1.0
| style="background-color: white;"| 13-09-2012
| style="background-color: white;"| [https://www.nictiz.nl/wp-content/uploads/2012/09/Alles-wat-je-wilt-weten-over-CCR-CCD-v1-0.pdf Alles wat je wilt (moet) weten over CCR/CCD]
| style="background-color: white;"| Nictiz
|}


=Bijlage: Documenthistorie=
==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:V2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

{| class="wikitable" "cellpadding="10" style="background-color: white;"
!style="text-align:left;"|Release
!style="text-align:left;"|Versie
!style="text-align:left;"|BITS issue
!style="width:850px; text-align:left;"|Omschrijving
|-
{{ReleaseNotes|package=2019.01 - April 2020|release=2.1.13|issues=3|MM-1025|MM-1003|MM-939}}
{{ReleaseNotes|package=2019.01 - Maart 2020|release=2.1.10|issues=4|MM-997|MM-953|MM-926|MM-657}}
{{ReleaseNotes|package=2019.01 - Februari 2020|release=2.1.9|issues=5|MM-901|MM-900|MM-852|MM-440|MM-414}}
{{ReleaseNotes|package=2019.01 - Januari 2020|release=2.1.8|issues=2|MM-492|MM-467}}
{{ReleaseNotes|package=2019.01 - November|packageIssues=3|release=2.1.7|MM-806}}
{{ReleaseNotes|release=2.1.6|issues=2|MM-729|MM-430}}
{{ReleaseNotes|package=2019.01 - Oktober|release=2.1.5|issues=2|MM-597|MM-594}}
{{ReleaseNotes|package=2019.01 - September|release=2.1.4|issues=5|MM-436|MM-425|MM-422|MM-359|MM-358}}
{{ReleaseNotes|package=2019.01|packageIssues=28|release=2.1.3|issues=6|MM-348|MM-346|MM-307|MM-294|MM-258|MM-248}}
{{ReleaseNotes|release=2.1.2|MM-219}}
{{ReleaseNotes|release=2.1.1|issues=2|MM-210|MM-206}}
{{ReleaseNotes|release=2.1.0|issues=19|MM-174|MM-161|MM-145|MM-144|MM-143|MM-142|MM-141|MM-134|MM-127|MM-125|MM-118|MM-115|MM-100|MM-99|MM-98|MM-94|MM-50|MM-42|MM-41}}
{{ReleaseNotes|package=2018.06|release=2.0.1|issues=6|MM-174|MM-128|MM-66|MM-55|MM-54|MM-23}}
|}

==Paginahistorie==
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Datum
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor april 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Maart 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Wijzigingen voor maart 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Februari 2020
| style="background-color: white; | 27-02-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Januari 2020
| style="background-color: white; | 27-01-2020
| style="background-color: white;"|
* Wijzigingen voor januari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 10-12-2019
| style="background-color: white;"|
* Wijzigingen voor november patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 28-11-2019
| style="background-color: white;"|
* Wijzigingen voor november patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Oktober
| style="background-color: white; | 30-10-2019
| style="background-color: white;"|
* Wijzigingen voor oktober patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - September
| style="background-color: white; | 30-09-2019
| style="background-color: white;"|
* Wijzigingen voor september patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 27-06-2019
| style="background-color: white;"|
* Toevoegen releasenotes voor patches. Ophogen versienummer naar 2.1.3.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 24-04-2019
| style="background-color: white;"|
* Toevoegen releasenote voor [https://bits.nictiz.nl/browse/MM-219 MM-219]
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 28-03-2019
| style="background-color: white;"|
* Plaatsen release notes behorende bij patch 1.
* Versienummer systeemrolcodes ophogen met 1 patch nummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"|
* Wijzigingen gepubliceerd in versie 2019.01, zie release notes.
* Verplaatsing release notes naar functionele pagina.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 18-10-2018
| style="background-color: white;"|
* Toevoeging releasenotes en ophoging systeemrol versienummer vanwege een technische verbetering in de raadpleging van FunctioneleOfMentale gegevens.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 15-10-2018
| style="background-color: white;"|
* Aanpassing versienummer in titel en documenthistorie.
|-
| style="background-color: white;vertical-align:top;"| 2018.06
| style="background-color: white;vertical-align:top;"| 30-08-2018
| style="background-color: white;"|
* Paragraaf 2.1.4, Verwijzing naar ART-DECOR toegevoegd.
* Bijlage: Documenthistorie toegevoegd.
* Paragraaf 1.4, verwijzing naar nieuwe pagina kwalificatie informatie toegevoegd.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 16-08-2018
| style="background-color: white;"|
* Structuur paragraaf 1.1 t/m 1.4 toegevoegd, ter voorbereiding kwalificatie informatie.
|}

MedMij:Vprepub-2019.01 OntwerpBGZ 2017

2020-05-01T07:38:28Z

Stephan Opdenberg: /* Release notes */

MedMij:V2019.01 OntwerpVragenlijsten

2020-05-01T07:34:54Z

Stephan Opdenberg: versie package verhoogd

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp Vragenlijsten {{VersieInfo|V2019.01|Vragenlijsten}}}}
{{MedMij:V2019.01_Issuebox}}

[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:Vragenlijsten-zonder-tekst-dun.png|link=|87px |links||media|Vragenlijsten]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_Questionnaire_and_Questionnaire_Response_(Vragenlijsten)|Technisch]]
desc none
</imagemap>

=Inleiding=
==Algemeen==
Op deze pagina wordt het functioneel ontwerp beschreven voor de uitwisseling van vragenlijsten en antwoorden binnen MedMij. De algemene inleiding van de MedMij functionele ontwerpen kan gevonden worden op de pagina [[MedMij:V2019.01_Ontwerpen|Ontwerpen MedMij]].

Het ontwerp richt zich op de uitwisseling van informatie en niet op de gebruikersfunctionaliteiten en/of gebruiksvriendelijkheid van een PGO of het systeem van de zorgaanbieder (XIS).

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de MedMij functionele ontwerpen.

==Kaders en uitgangspunten==
===Richtlijn===
Er zijn geen richtlijnen van het zorgaanbiedersdomein. Bij implementeren van de standaard gelden de volgende uitgangspunten:
* Maak gebruik gemaakt van de bestaande, internationale, FHIR-profielen van [http://hl7.org/fhir/us/sdc/index.html SDC (Structured Data Capture)]
** Bij het overnemen van een profiel, zijn deze in hun geheel toegepast
** Het gaat alleen om die profielen die voor deze use case toegevoegde waarde hebben
* Bij ieder overgenomen profiel is, een voor Nederland specifiek profiel opstellen. Er is bijvoorbeeld minimaal een referentie nodig naar het Nederlandse patiëntprofiel
* De SDC-profielen hebben reeds veel verschillende vraagsoorten & antwoordmogelijkheden gespecificeerd, deze worden overgenomen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Informatie reikwijdte===
Het ontwerp richt zich op de uitwisseling van informatie en niet op de gebruikersfunctionaliteiten en/of gebruiksvriendelijkheid van een PGO of het systeem van de zorgaanbieder (XIS).
Het ontwerp bevat:
* Een eenvoudige zorgsituatie:

# Een zorgaanbieder maakt, buiten de persoonlijke gezondheidsomgeving om, een afspraak met een patiënt over het invullen van een vragenlijst
# Deze zorgaanbieder maakt de vragenlijst beschikbaar voor de persoonlijke gezondheidsomgeving van de patiënt
# De patiënt gebruikt zijn persoonlijke gezondheidsomgeving om de vragenlijst op te halen
# De patiënt vult de vragenlijst in en stuurt de antwoorden in zijn geheel terug naar het systeem van de zorgaanbieder (XIS).

Expliciet buiten scope van het ontwerp zijn de volgende onderwerpen:
* Workflow-gerelateerde zaken.
** Notificaties, anders dan waarin het afsprakenstelsel van MedMij wordt voorzien.
** Werkafspraken over (tijdigheid van) invullen en terug sturen.
** Aanpak voor multi-channel mogelijkheden (bijvoorbeeld: via PGO in combinatie met portaal en schriftelijk).

* Complexe computergestuurde vragenlijsten (bijvoorbeeld: Computer Adaptive Testing - CAT).
* Interpretatie van antwoorden. Een uitgangspunt is om PGO's nog niet te belasten met het berekenen van scores op basis van ingevulde antwoorden. Het uitwisselen van de definitie van score-berekening is daarom ook buiten scope. Een XIS kan eventueel berekende scores en terugsturen aan een PGO met de use case [[MedMij:V2019.01_OntwerpPDFA#Use_case:_Raadplegen_medische_gegevens_in_PDF.2FA_door_pati.C3.ABnt|PDF/A]].
* Ontwikkeling van nieuwe zibs specifiek voor vragenlijsten.
* Standaardisatie van de inhoud van vragenlijsten (de deliverables van dit project zijn content-agnostisch).
* Toepassing van specifieke coderingen of codestelsels (met uitzondering van administratieve gegevens van patiënt).
* Mogelijke financiële consequenties van het gebruik van vragenlijsten, bijvoorbeeld licentiekosten.

'''Nb.''' Vragenlijsten kunnen gespecificeerde opmaak (bijvoorbeeld vet- of schuingedrukte tekst) hebben die betekenisvol is voor het invullen van een vragenlijst door een PGO-Gebruiker en hiermee relevant is voor een zorgverlener om de uitkomsten te interpreteren. De standaard voorziet in de mogelijkheden om opmaak te specificeren en van gebruikers van deze standaard wordt verwacht dat ze hiermee om kunnen gaan.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

=Use Cases=
Het raadplegen van de vragenlijstverwijzing, vragenlijst en het sturen van de antwoorden zijn 3 use cases die nadrukkelijk bij elkaar horen. Functioneel kunnen ze zelfs gezien worden als verschillende acties binnen een zelfde use case. Ze zijn echter als separate use case gedefinieerd omdat:
* Het raadplegen van een verwijzing naar een vragenlijst, de vragenlijst en het sturen van de antwoorden asynchroon plaatsvindt
* Het MedMij-afsprakenstelsel voor 'raadplegen en beschikbaarstellen' en voor 'sturen en ontvangen' separate use cases definieert.
Door dit ook in de informatiestandaard gescheiden te houden, kunnen de use cases uit de informatiestandaard goed gemapt worden op de use cases uit het [https://afsprakenstelsel.medmij.nl/display/MedMijAfsprakenstelsel120/MedMij+Afsprakenstelsel+1.2.0 MedMij-afsprakenstelsel]. De splitsing is alleen niet goed voor het totaaloverzicht van de verschillende scenario's.

Er zijn twee bedrijfsrollen, namelijk ''Patiënt'' en ''Zorgaanbieder''. Een zorgaanbieder biedt een verwijzing naar een vragenlijst aan, die gebruikt kan worden door een patiënt om bij de zorgaanbieder zelf of een externe repository een vragenlijst op te halen. De patiënt kan dan de vragenlijst invullen en terugsturen naar de zorgaanbieder. Onderstaande tabel geeft de rollen weer.

{| class="wikitable" "cellpadding="10" width="100%"
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil vragenlijsten in een persoonlijke gezondheidsomgeving kunnen invullen en de antwoorden terugsturen.
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Wil dat patiënten vragenlijsten invullen en de antwoorden aan de zorgaanbieder sturen.
|}

Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd in samenhang met de beschreven use cases.

[[Image:Activity_Diagram_-_Vragenlijsten.png|Activiteitendiagram vragenlijsten]]

'''Activiteitendiagram vragenlijsten'''

==Use case: Raadplegen vragenlijstverwijzing ==
=== Doel en relevantie ===
Het voor patiënten mogelijk maken om in een PGO een vragenlijst te ontvangen en in te vullen.
=== Domein ===
Vragenlijsten in het domein van zorgaanbieders en patiënten.

=== Context ===
Het gaat om het elektronisch en gestructureerd aanbieden c.q. beschikbaarstellen van vragenlijsten door zorgaanbieders vanuit een zorgaanbiederssysteem (XIS) naar een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO).
Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.
De beschrijving is infrastructuur-onafhankelijk.

=== Informatie ===
De informatie-elementen voor raadplegen en beschikbaarstellen vragenlijstverwijzing staan in [https://decor.nictiz.nl/pub/vragenlijsten/ ART-DECOR]

==== Raadplegen vragenlijstverwijzing ====
Er zijn geen specifieke filtermogelijkheden (query parameters) gedefinieerd voor de raadplegen vragenlijstverwijzing.

==== Beschikbaarstellen vragenlijstverwijzing ====
Informatie-elementen in Vragenlijsten staan hieronder. Deze informatie is ook in een nieuw tabblad te openen.

<html>
<iframe width="100%" height="400" src=https://decor.nictiz.nl/pub/vragenlijsten/vl-html-20200403T135608/tr-2.16.840.1.113883.2.4.3.11.60.56.4.248-2019-04-11T132707.html frameborder="0" align="middle"></iframe>
</html>

=== Bedrijfsrollen ===
Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd in samenhang met de beschreven use cases.

[[Image:Activity_Diagram_-_Vragenlijsten.png|Activiteitendiagram vragenlijsten]]

=== Procesbeschrijving ===
==== Patient Journey – Jelmer Postma ====
Een voorbeeldsituatie die de meerwaarde van vragenlijsten met een PGO schetst is de patient journey van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Jelmer_Postma_MedMij.pdf Jelmer Postma].
<blockquote>Jelmer wordt door zijn GZ-psycholoog gevraagd een vragenlijst te vullen over zijn stemmingen gedurende een dag. De psycholoog spreekt met Jelmer af dat hij deze zal invullen voorafgaand aan het volgende consult. Een patiënt als Jelmer Postma kan via zijn PGO een vragenlijst van een zorgverlener ontvangen. Hij vult deze op een later moment in en stuurt de antwoorden volgens afspraak weer terug naar de zorgaanbieder. Bij het volgende consult kan de GZ-psycholoog samen met Jelmer de vragenlijst doornemen.</blockquote>

==== Proces ====
Deze use case ondersteunt geen workflow tussen zorgaanbieder en patiënt. Eventuele procesafspraken zijn dus geen onderdeel van deze use case. Voordat het proces start heeft een medewerker van de zorgaanbieder met een patiënt afgesproken om op of voor een bepaald moment een vragenlijst in te vullen. Het stuk van het proces waar het in deze use case om gaat is:
* Een zorgaanbieder (XIS) stelt de vragenlijstverwijzing beschikbaar.
Het resultaat is dat de patiënt (PGO) de beschikking over een verwijzing waarmee die vervolgens de relevante vragenlijst kan ophalen.

Deze paragraaf vervolgt met een beschrijving van precondities, processtappen, en post condities.

===== Preconditie =====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van vragenlijsten tussen zijn PGO en het betreffende XIS.
De patiënt en zorgaanbieder hebben onderling procesafspraken gemaakt over het invullen van de vragenlijst.
Het XIS van de zorgaanbieder is in staat vragenlijstverwijzingen specifiek beschikbaar te stellen aan een patiënt en vervolgens de antwoorden weer te ontvangen van de patiënt via zijn PGO.
De XIS is in staat de betreffende vragenlijst beschikbaar te stellen aan raadplegers.

===== Processtappen =====
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Stap
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 01
| style="background-color: white;"| Zorgaanbieder wijst een bepaalde vragenlijst toe aan patiënt (in het XIS)
|-
| style="background-color: white;"| 02
| style="background-color: white;"| PGO bevraagt het XIS om deze toewijzing te ontvangen in de vorm van een verwijzing naar een vragenlijst. Deze verwijzing is een URI waar het PGO de daadwerkelijke vragenlijst kan ophalen.
|}

===== Postconditie =====
Patiënt heeft de beschikking over de vragenlijst in zijn PGO en kan de vragen daar gaan invullen.

=== Systemen & Systeemrollen ===
Zowel de patiënt als de zorgaanbieder maken ieder gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om vragenlijsten en antwoorden tussen de persoon en de zorgaanbieder.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| Vragenlijstverwijzing raadplegend systeem
| style="background-color: white;"| VL-1.0.0-QLR-FHIR
| style="background-color: white;"| Raadplegen van verwijzing naar vragenlijst door patiënt
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| Vragenlijstverwijzing beschikbaarstellend systeem
| style="background-color: white;"| VL-1.0.0-QLB-FHIR
| style="background-color: white;"| Beschikbaarstellen van verwijzing naar vragenlijst voor PGO
|}

Zie ook onderstaande afbeelding.

[[Bestand:Component_Diagram_-_Vragenlijsten_(Raadplegen).png|Componenten diagram Vragenlijstverwijzing en Vragenlijst raadplegen]]

'''Componenten diagram Vragenlijsten raadplegen'''

De kwalificatie van informatiesystemen vindt plaats op basis van systeemrollen.

=== Transacties & Transactiegroepen ===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:middle;" rowspan="2"|Verwijzing naar vragenlijsten(PULL)
|style="background-color: white;vertical-align:top;"|Raadplegen verwijzing naar vragenlijst
|style="background-color: white;vertical-align:top;"|VL-1.0.0-QLR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_Questionnaire_and_Questionnaire_Response_(Vragenlijsten)|Questionnaire(response) in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen verwijzing naar vragenlijst
|style="background-color: white;vertical-align:top;"|VL-1.0.0-QLB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:Use_Case_Diagram_-_Vragenlijsten_(Raadplegen).png|Use case diagram Sturen Beelden]]

'''Use case diagram raadplegen vragenlijstverwijzing en raadplegen vragenlijst

==Use case: Raadplegen vragenlijst ==
=== Doel en relevantie ===
Het voor patiënten mogelijk maken om in een PGO een vragenlijst te ontvangen en in te vullen. Het vervolgens weer terugsturen van de antwoorden staat beschreven in een aparte use case: [[MedMij:V2019.01_OntwerpVragenlijsten#Use_case:_Sturen_vragenlijstantwoorden|sturen vragenlijstantwoorden]].

=== Domein ===
Vragenlijsten in het domein van zorgaanbieders en patiënten.

=== Context ===
Het gaat om het elektronisch en gestructureerd aanbieden c.q. beschikbaarstellen van vragenlijsten door zorgaanbieders vanuit een zorgaanbiederssysteem (XIS) naar een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO).
Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.
De beschrijving is infrastructuur-onafhankelijk.

=== Informatie ===
De informatie-elementen voor raadplegen en beschikbaarstellen vragenlijst staan in [https://decor.nictiz.nl/pub/vragenlijsten/ ART-DECOR]

Deze informatie-elementen ondersteunen de volgende aspecten:
* Het al dan niet tonen van bepaalde vragen in de vragenlijst afhankelijk van de antwoorden:
** Hierbij gaat het er om dat sommige vragen overgeslagen worden op basis van een antwoord op een andere vraag (sprongvragen). De dataset kent hiervoor het element 'enableWhen'
* Specificeren van verschillende type vragen:
** Het gaat dan om bijvoorbeeld keuzelijst met één of meerdere selecties, vrije tekst, combinaties hiervan, schalen, et cetera
* Vragenlijsten kunnen ook bepaalde eisen aan de weergave van vragen/antwoordopties definiëren, welke dan verplicht zijn om te volgen. Het verschillend weergegeven van vragenlijsten compromitteren de validiteit en/of vergelijkbaarheid van de vragenlijst. Denk hierbij aan:
** volgorde van antwoordopties of
** het in één keer tonen van alle antwoordopties of
** het recht onder elkaar staan van antwoordopties
** specifieke opmaak zoals '''vet'''- of ''schuin''gedrukte tekst

==== Raadplegen vragenlijst ====
Er zijn geen specifieke filtermogelijkheden (query parameters) gedefinieerd voor de raadplegen vragenlijst.

==== Beschikbaarstellen vragenlijst ====
Informatie-elementen in Vragenlijsten staan hieronder. Deze informatie is ook in een nieuw tabblad te openen.

<html>
<iframe width="100%" height="400" src=https://decor.nictiz.nl/pub/vragenlijsten/vl-html-20200403T135608/tr-2.16.840.1.113883.2.4.3.11.60.56.4.255-2019-04-11T140121.html frameborder="0" align="middle"></iframe>
</html>

=== Bedrijfsrollen ===
Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd in samenhang met de beschreven use cases.

[[Image:Activity_Diagram_-_Vragenlijsten.png|Activiteitendiagram vragenlijsten]]

=== Procesbeschrijving ===
==== Patient Journey – Jelmer Postma ====
Een voorbeeldsituatie die de meerwaarde van vragenlijsten met een PGO schetst is de patient journey van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Jelmer_Postma_MedMij.pdf Jelmer Postma].
<blockquote>Jelmer wordt door zijn GZ-psycholoog gevraagd een vragenlijst te vullen over zijn stemmingen gedurende een dag. De psycholoog spreekt met Jelmer af dat hij deze zal invullen voorafgaand aan het volgende consult. Een patiënt als Jelmer Postma kan via zijn PGO een vragenlijst van een zorgverlener ontvangen. Hij vult deze op een later moment in en stuurt de antwoorden volgens afspraak weer terug naar de zorgaanbieder. Bij het volgende consult kan de GZ-psycholoog samen met Jelmer de vragenlijst doornemen.</blockquote>

==== Proces ====
Deze use case ondersteunt geen workflow tussen zorgaanbieder en patiënt. Eventuele procesafspraken zijn dus geen onderdeel van deze use case.
Voordat het proces start heeft een medewerker van de zorgaanbieder met een patiënt afgesproken om op of voor een bepaald moment een vragenlijst in te vullen.

Het stuk van het proces waar het in deze use case om gaat is:
* Een zorgaanbieder stelt de vragenlijst beschikbaar (bijvoorbeeld via een vragenlijst-repository waarbij het niet relevant is of de zorgaanbieder deze repository zelf aanbiedt of gebruik maakt van een externe partij).
* De zorgaanbieder koppelt een vragenlijst aan de patiënt.
* De patiënt haalt vervolgens de relevante vragenlijst op.
Het resultaat is dat de patiënt de beschikking heeft over de vragenlijst in zijn PGO en de vragen kan gaan beantwoorden.

Deze paragraaf vervolgt met een beschrijving van precondities, processtappen, en post condities.

===== Preconditie =====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van vragenlijsten tussen zijn PGO en het betreffende XIS.
De patiënt en zorgaanbieder hebben onderling procesafspraken gemaakt over het invullen van de vragenlijst.
Het XIS van de zorgaanbieder is in staat vragenlijstverwijzingen specifiek beschikbaar te stellen aan een patiënt en vervolgens de antwoorden weer te ontvangen van de patiënt via zijn PGO.
XIS is in staat de betreffende vragenlijst beschikbaar te stellen aan raadplegers.

===== Processtappen =====
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Stap
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 01
| style="background-color: white;"| PGO heeft vanuit het XIS een verwijzing naar een vragenlijst ontvangen. Zie use case [[MedMij:V2019.01_OntwerpVragenlijsten#Use_case:_Raadplegen_vragenlijstverwijzing|Raadplegen vragenlijstverwijzing]]
|-
| style="background-color: white;"| 02
| style="background-color: white;"| PGO haalt vervolgens de vragenlijst op (Nb. Ophalen kán plaatsvinden buiten het MedMij-Afsprakenstelsel. Als dit buiten het MedMij-afsprakenstelsel plaatsvindt, wordt dit 'niet op de persoon herleidbaar' gedaan.).
|}

===== Postconditie =====
Patiënt heeft de beschikking over de vragenlijst in zijn PGO en kan de vragen daar gaan invullen.

=== Systemen & Systeemrollen ===
Zowel de patiënt als de zorgaanbieder maken ieder gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)
Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om vragenlijsten en antwoorden tussen de persoon en de zorgaanbieder.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| Vragenlijst raadplegend systeem
| style="background-color: white;"| VL-1.0.0-QER-FHIR
| style="background-color: white;"| Raadplegen van vragenlijst door PGO (zonder dat het herleidbaar is op de persoon)
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| Vragenlijst beschikbaarstellend systeem
| style="background-color: white;"| VL-1.0.0-QEB-FHIR
| style="background-color: white;"| Beschikbaarstellen van vragenlijst voor PGO (zonder dat het herleidbaar is op de persoon)
|}

Zie ook onderstaande afbeelding.

[[Bestand:Component_Diagram_-_Vragenlijsten_(Raadplegen).png|Componenten diagram Vragenlijstverwijzing en Vragenlijst raadplegen]]

'''Componenten diagram Vragenlijsten raadplegen'''

De kwalificatie van informatiesystemen vindt plaats op basis van systeemrollen.

=== Transacties & Transactiegroepen ===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:middle;" rowspan="2"|Vragenlijsten(PULL)
|style="background-color: white;vertical-align:top;"|Raadplegen vragenlijst
|style="background-color: white;vertical-align:top;"|VL-1.0.0-QER-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_Questionnaire_and_Questionnaire_Response_(Vragenlijsten)|Questionnaire(response) in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen vragenlijst
|style="background-color: white;vertical-align:top;"|VL-1.0.0-QEB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder

|}

===Use case diagram===
[[Bestand:Use_Case_Diagram_-_Vragenlijsten_(Raadplegen).png|Use case diagram Sturen Beelden]]

'''Use case diagram raadplegen vragenlijstverwijzing en raadplegen vragenlijst

==Use case: Sturen vragenlijstantwoorden ==
=== Doel en relevantie ===
Het voor patiënten mogelijk maken om vanuit een PGO de antwoorden op een vragenlijst terug te sturen naar de zorgaanbieder.

=== Domein ===
Antwoorden op vragenlijsten in het domein van zorgaanbieders en patiënten.

=== Context ===
Het gaat om het elektronisch en gestructureerd sturen van antwoorden op vragenlijsten door PGO-gebruiker aan zorgaanbieders vanuit een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO) naar zorgaanbiederssysteem (XIS). Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.
De beschrijving is infrastructuur-onafhankelijk.

=== Informatie ===
De informatie-elementen voor sturen en ontvangen vragenlijstantwoorden staan in [https://decor.nictiz.nl/pub/vragenlijsten/ ART-DECOR]

Informatie-elementen in Vragenlijstantwoorden staan hieronder. Deze informatie is ook in een nieuw tabblad te openen.

<html>
<iframe width="100%" height="500" src=https://decor.nictiz.nl/pub/vragenlijsten/vl-html-20200403T135608/tr-2.16.840.1.113883.2.4.3.11.60.56.4.263-2020-04-01T135355.html frameborder="0" align="middle"></iframe>
</html>

=== Bedrijfsrollen ===
Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd in samenhang met de hieronder beschreven use cases.

[[Image:Activity_Diagram_-_Vragenlijsten.png|Activiteitendiagram vragenlijsten]]

=== Procesbeschrijving ===
==== Patient Journey – Jelmer Postma ====
Een voorbeeldsituatie die de meerwaarde van vragenlijsten met een PGO schetst is de patient journey van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Jelmer_Postma_MedMij.pdf Jelmer Postma].
<blockquote>Jelmer wordt door zijn GZ-psycholoog gevraagd een vragenlijst te vullen over zijn stemmingen gedurende een dag. De psycholoog spreekt met Jelmer af dat hij deze zal invullen voorafgaand aan het volgende consult. Een patiënt als Jelmer Postma kan via zijn PGO een vragenlijst van een zorgverlener ontvangen. Hij vult deze op een later moment in en stuurt de antwoorden volgens afspraak weer terug naar de zorgaanbieder. Bij het volgende consult kan de GZ-psycholoog samen met Jelmer de vragenlijst doornemen.</blockquote>

==== Proces ====
Deze use case ondersteunt geen workflow tussen zorgaanbieder en patiënt. Eventuele procesafspraken zijn dus geen onderdeel van deze use case.
Voordat het proces start heeft een medewerker van de zorgaanbieder met een patiënt afgesproken om op of voor een bepaald moment een vragenlijst in te vullen. Ook heeft de patiënt de vragenlijst opgehaald zoals beschreven in [[MedMij:V2019.01_OntwerpVragenlijsten#Use_case_1:_Raadplegen_vragenlijst|de use case raadplegen vragenlijst]].

Het stuk van het proces waar het in deze use case om gaat is:
* De patiënt beantwoordt de vragenlijst in zijn PGO en stuurt de antwoorden terug naar de zorgaanbieder.

Afhankelijk van het doel van de vragenlijst kan een medewerker van de zorgaanbieder de vragenlijst met de patiënt op een later moment bespreken.

Deze paragraaf vervolgt met een beschrijving van precondities, proces stappen, en post condities.

===== Preconditie =====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van (antwoorden op) vragenlijsten tussen zijn PGO en het betreffende XIS.
De patiënt en zorgaanbieder hebben onderling procesafspraken gemaakt over het invullen van de vragenlijst. Het PGO heeft een vragenlijst opgehaald.

===== Proces stappen =====
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Stap
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 01
| style="background-color: white;"| PGO stelt de patiënt in staat de vragenlijsten in te vullen
|-
| style="background-color: white;"| 02
| style="background-color: white;"| Patiënt beantwoordt de vult de vragenlijsten in
|-
| style="background-color: white;"| 03
| style="background-color: white;"| Patiënt bepaalt wanneer het invullen gereed is
|-
| style="background-color: white;"| 04
| style="background-color: white;"| PGO stuurt de antwoorden terug naar het XIS
|}

===== Postconditie =====
De zorgaanbieder kan de vragenlijst met antwoorden inzien in het XIS.
De patiënt en zorgaanbieder kunnen hierover in overleg.

=== Systemen & Systeemrollen ===
Zowel de persoon als de zorgaanbieder maken gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om vragenlijsten en antwoorden tussen de persoon en de zorgaanbieder.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| Antwoorden op vragenlijst sturend systeem
| style="background-color: white;"| VL-1.0.0-QRS-FHIR
| style="background-color: white;"| Sturen van antwoorden op de vragenlijst aan zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| Antwoorden op vragenlijst ontvangend systeem
| style="background-color: white;"| VL-1.0.0-QRO-FHIR
| style="background-color: white;"| Ontvangen van antwoorden op de vragenlijst van de patiënt
|}

Zie ook onderstaande afbeelding.

[[Bestand:Component_Diagram_-_Vragenlijsten_(Sturen).png|Componenten diagram Vragenlijstverwijzing en Vragenlijst sturen]]

'''Componenten diagram Vragenlijsten sturen'''

De kwalificatie van informatiesystemen vindt plaats op basis van systeemrollen.

=== Transacties & Transactiegroepen ===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:middle;" rowspan="2"|Antwoorden op vragenlijst (PUSH)
|style="background-color: white;vertical-align:top;"|Sturen antwoorden op vragenlijst
|style="background-color: white;vertical-align:top;"|VL-1.0.0-QRS-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_Questionnaire_and_Questionnaire_Response_(Vragenlijsten)|Questionnaire(response) in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Ontvangen antwoorden op vragenlijst
|style="background-color: white;vertical-align:top;"|VL-1.0.0-QRO-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang met [[MedMij:V2019.01_OntwerpVragenlijsten#Use_case_1:_Raadplegen_vragenlijst|de use case raadplegen vragenlijsten]].

[[Bestand:Use_Case_Diagram_-_Vragenlijsten_(Sturen).png|Use case diagram Sturen Vragenlijsten]]

'''Use case diagram Vragenlijsten

=Functionaliteit=
Er zijn geen aanwijzingen/eisen voor functionaliteit van de systemen.

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="text-align:left;"|Auteur(s)
!style="text-align:left;"|Titel
!style="text-align:left;"|Versie
!style="text-align:left;"|Datum
!style="text-align:left;"|Bron
!style="text-align:left;"|Organisatie
|-
| style="background-color: white;"| -
| style="background-color: white;"| Structured Data Capture (SDC)
| style="background-color: white;"| 2.0 (STU2)
| style="background-color: white;"| 2017-04-21
| style="background-color: white;"| https://hl7.org/fhir/us/sdc/STU2/
| style="background-color: white;"| U.S. Office of the National Coordinator (ONC)'s Standards and Infrastructure (S & I) Framework
|}
'''Referenties

=Bijlage: Documenthistorie=

==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:V2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

==Paginahistorie==
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Datum
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor april 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
|-
| style="background-color: white;"| -
| style="background-color: white;"| 03-04-2020
| style="background-color: white;"| Publicatie standaard.

|}

MedMij:Vprepub-2019.01 OntwerpVragenlijsten

2020-05-01T07:34:54Z

Stephan Opdenberg: versie package verhoogd

MedMij:V2019.01 OntwerpBeelden

2020-05-01T07:33:59Z

Stephan Opdenberg: versie package verhoogd

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp Beelden {{VersieInfo|V2019.01|Beelden}}}}

[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:beeldenIcoon.png|link=|87px |links||media]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_Images|Technisch]]
desc none
</imagemap>

=Inleiding=
==Algemeen==
Deze pagina beschrijft het functioneel ontwerp voor de uitwisseling van beelden binnen MedMij. De algemene inleiding van de MedMij functionele ontwerpen kan [[MedMij:V2019.01_Ontwerpen| hier]] gevonden worden.

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de MedMij functionele ontwerpen, die [[MedMij:V2019.01_Ontwerpen#Doelgroep| hier]] gevonden kan worden.

==Kaders en uitgangspunten==
===Richtlijn===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Richtlijn| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

=Use Cases=
==Use case 1: Sturen beelden vanuit een PGO==
=== Doel en relevantie ===
*Het voor patiënten/ personen mogelijk maken regie op hun eigen gezondheid te nemen door beelden te sturen naar (verschillende) zorgaanbieders.
*Deze use case ondersteunt geen interactie met de patiënt middels het PGO. De zorgverlener kan niet online reageren op de gestuurde beelden. De zorgverlener dient buiten deze use case om de beelden te bespreken met de patiënt.

=== Domein ===
Beelden in het domein van zorgaanbieders en patiënten/ personen.

=== Context ===
Het gaat om het elektronisch en gestructureerd sturen van beelden vanuit een [[#persoonlijke-gezondheidsomgeving|persoonlijke gezondheidsomgeving]] (PGO) naar een zorgaanbiederssysteem (XIS). Deze pagina bevat (verwijzingen naar) beschrijvingen van:
* informatie,
* bedrijfsrollen (actoren),
* proces,
* systemen,
* systeemrollen,
* transactiegroepen en transacties, inclusief de inhoud van deze transacties.

De beschrijving is infrastructuur-onafhankelijk.

=== Informatie ===
Bij het sturen van beelden gaat het om de volgende informatie die uitgewisseld wordt: de beelden, bijbehorende meta-informatie per beeld en een mogelijk toelichting/ begeleidende tekst.

De informatie-elementen voor sturen en ontvangen van een beeld of collectie beelden staan in [http://decor.nictiz.nl/pub/beelden/bd-html-20190512T171559/tr-2.16.840.1.113883.2.4.3.11.60.54.4.2-2019-02-25T131649.html ART-DECOR Sturen Beelden].

==== Beeldformaat ====
*De ontvangende systemen dienen de volgende gegevensformaten te ondersteunen: JPEG, PNG, GIF en JP2. De PGO bepaalt zelf in welke van deze ondersteunende beeldformaten, de beelden worden verstuurd. De genoemde beeldformaten zijn ook de gegevensformaten, bestaande uit één frame, die door [[#DICOM-beeldformaten|DICOM standaard]] worden gespecificeerd voor gebruik bij DICOM web-services. Binnen deze use case zijn dit de enige gebruikte gegevensformaten voor beelden. Beeldformaat DICOM is niet in scope voor deze use case.
*Beelden mogen extra (meta)informatie bevatten in bijvoorbeeld de [[#Exif|Exif standaard]]. Een voorbeeld is het opslaan van patiëntgegevens binnen het beeldformaat JPEG. Hier wordt in deze use case echter geen gebruik van gemaakt.

==== Frequentie sturen beeld(en) ====
*Met het oog op bijvoorbeeld een ''denial of service attack'' is de overweging geweest om de frequentie waarmee de patiënt beelden kan versturen te beperken. Besloten is om voorlopig geen beperkingen op te nemen in de standaard.

==== Grootte van beeld(en) ====
De maximale grootte van een beeld is 20 MB (voordat het Base64 encoded is). Een PGO kan één tot maximaal 3 beelden tegelijk sturen. De maximale grootte van een collectie beelden is 60 MB. Base64 codering maakt het resultaat 37% groter.

==== Toelichting ====
De patiënt kan per beeld en/of per collectie beelden een begeleidende tekst meegeven. Dit gaat middels de 'toelichting' meta-informatie elementen.

==== Meta-informatie ====
Het beeld dient te worden voorzien van voldoende meta-informatie om door het ontvangende systeem goed te kunnen worden geïnterpreteerd. De specificatie van de meta-informatie wordt gegeven in de dataset en transactiebeschrijving. Daarnaast kent het FHIR profiel, verwezen vanuit het technisch ontwerp, nog een aantal verplichte concepten.
Deze use case houdt rekening met zelfstandige XIS-sen en met XIS-sen die zijn aangesloten op een XDS-netwerk door het bericht te voorzien van voldoende meta-informatie voor indexatie. Het correct indexeren van beelden in een XDS netwerk is de verantwoordelijkheid van het ontvangende XIS. Het technische ontwerp geeft een niet-normatieve implemenatierichtlijn middels een mapping van het FHIR bericht naar XDS concepten en het IHE MHD profiel.

=== Bedrijfsrollen ===
Deze use case onderscheidt twee bedrijfsrollen, namelijk de ''Patiënt'' en de ''Zorgaanbieder'' zoals te zien in onderstaande tabel.

{| class="wikitable" "cellpadding="10" width="100%"
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil beelden sturen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Wil beelden ontvangen
|}
'''Bedrijfsrollen sturen beelden'''

Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd.

[[Image:Activity_Diagram_-_Sturen_Beelden.png|Activiteitendiagram sturen beelden]]

'''Activiteitendiagram sturen beelden'''

=== Procesbeschrijving ===
==== Patient Journey – Thomas van Beek ====
Een voorbeeldsituatie die de meerwaarde van het sturen van beelden vanuit het PGO schetst is de patiënt journey van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Thomas_van_Beek_MedMij.pdf Thomas van Beek].
<blockquote>De afgelopen periode heeft Thomas wisselend last van eczeem. De vorige keer dat Thomas een dergelijke aanval had, waren de klachten al afgenomen op het moment dat de afspraak met de huisarts plaatsvond. Om de ernst van de klachten te kunnen inschatten heeft de huisarts gevraagd of Thomas in het vervolg een foto kan maken van de eczeem wanneer deze in alle ernst aanwezig zijn.
Vandaag is het weer zover. Bij het maken van de afspraak met de huisarts verzoekt de assistente of Thomas direct een foto kan maken en deze de huisarts wil toesturen. Thomas maakt foto's van onder andere zijn gezicht en upload deze naar zijn PGO. Een paar dagen na het versturen van de foto heeft hij een afspraak bij de huisarts. De foto's komen tijdens het consult ter sprake en een passende behandeling wordt gekozen.</blockquote>

==== Patient Journey – Kenneth van Someren ====
Een tweede voorbeeld waarbij de meerwaarde van het sturen van beelden vanuit het PGO geschetst kan worden is de patiënt journey van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Kenneth_van_Someren_MedMij.pdf Kenneth van Someren].

<blockquote>De grote antieke stoel in de woonkamer is het plekje waar Kenneth thuis graag te vinden is. De stoel begon echter de laatste tijd steeds minder lekker te zitten. De zuster adviseert regelmatig af te wisselen met de bank, maar de televisie is lang niet zo interessant als het dorpsplein aan de overkant van de straat. Het begon met enkel een klein rood plekje op zijn ruggengraat, maar inmiddels begon dit vormen aan te nemen die ook dochter Debby zorgen baarde. Na kort overleg met de thuiszorg besluit ze telefonisch contact op te nemen met de wondverpleegkundige van de organisatie. Deze vraagt om een duidelijke foto te maken en via het PGO te sturen voor beoordeling. De wondverpleegkundige ziet de foto en vind het ook zorgelijk. Daarom maak ze direct een afspraak met Kenneth om de plek zelf te beoordelen. De volgende ochtend lukt dat al en die middag komt de thuiszorg met de juiste kennis en materialen om de wond te behandelen.</blockquote>

==== Proces ====
Het stuk van het proces waar het in deze use case omgaat is:
* Patiënt en zorgverlener maken de afspraak dat de patient een beeld kan sturen aan de zorgverlener.
* Patiënt maakt, ontvangt of downloadt één of meerdere beelden en uploadt deze naar zijn PGO. De beelden kunnen gemaakt zijn door de patiënt, een zorgaanbieder of iemand anders.
* Patiënt heeft de mogelijkheid om een begeleidende tekst van maximaal 1 MB toe te voegen aan het beeld en/of beelden.
* Het PGO stuurt de beelden naar het systeem van de zorgaanbieder.
** Mogelijk moet of kan de patiënt metagegevens behorende bij de beelden aanvullen of invullen.
* De zorgaanbieder raadpleegt de beelden in zijn eigen dossier (XIS).
* De zorgverlener bespreekt het beeld buiten het PGO om met de patiënt. Deze use-case ondersteunt geen interactie met de patiënt middels het PGO.

Deze paragraaf vervolgt met een beschrijving van precondities, processtappen, en postcondities.

===== Preconditie =====
* De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van beelden tussen het eigen PGO en de betreffende XIS.
* De patiënt en zorgaanbieder hebben onderling afspraken gemaakt over het sturen van beelden.
* Het XIS van de zorgaanbieder is in staat afbeeldingen van de patient te ontvangen.
* De beelden bevinden zich in of zijn toegankelijk voor, het PGO

===== Processtappen =====
* Het systeem van de patiënt (PGO) stuurt de beelden naar het systeem van de zorgaanbieder (XIS).
* Het systeem van de zorgaanbieder (XIS) ontvangt de beelden van het PGO.

===== Postconditie =====
* Indien het systeem van de zorgaanbieder (XIS) gebruik maakt van een XDS-omgeving zal dit systeem de beelden op gepaste wijze in het netwerk registreren.
* De zorgaanbieder gebruikt het systeem (XIS) om de beelden te kunnen zien en/of beoordelen.

=== Systemen & Systeemrollen ===
Zowel de patiënt als de zorgaanbieder maken ieder gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om beelden van de patiënt naar de zorgaanbieder.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| Sturen van Beelden
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Beelden}}-BES-FHIR
| style="background-color: white;"| Sturen van beelden naar zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| Ontvangen van Beelden
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Beelden}}-BEO-FHIR
| style="background-color: white;"| Ontvangen van beelden vanuit het PGO
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:Component_Diagram_-_Sturen_Beelden_(Totaal).png|Componenten diagram]]

'''Componenten diagram van systemen en systeemrollen'''

=== Transacties & Transactiegroepen ===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een stuur- en ontvangstbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:middle;" rowspan="2"|Beelden (PUSH)
|style="background-color: white;vertical-align:top;"|Sturen Beelden
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Beelden}}-BES-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_Images |Beelden in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Ontvangen Beelden
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Beelden}}-BEO-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:Use_Case_Diagram_-_Sturen_Beelden.png|Use case diagram Sturen Beelden]]

'''Use case diagram sturen beelden

=Functionaliteit=

== Eisen en wensen ==
*'''Afstemming vooraf''': Tijdens de ontwikkeling van de informatiestandaard is er nagedacht over het opnemen van een verplichte checkbox die de patiënt moet aanvinken om aan te geven dat er afstemming is geweest met de zorgverlener. Uiteindelijk is besloten om deze eis niet op te nemen in de standaard omdat in de praktijk patiënt en zorgverlener altijd een context hebben waarin het sturen van de beelden past. Daarnaast is het uitgangspunt om de patiënt zo min mogelijk te laten invullen bij het sturen van een beeld.

== Niet functionele eisen en wensen ==
Het technisch ontwerp bevat een aantal verplichte (technische) data elementen die niet zijn opgenomen in de functionele dataset. Een aantal van deze velden zijn verplicht gesteld om compatibiliteit met XDS-netwerken te ondersteunen. Het gaat om de volgende elementen:

* Indentificatie van het beeld en collectie beelden
* Een hash van de data van het beeld

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="text-align:left;"|Auteur(s)
!style="text-align:left;"|Titel
!style="text-align:left;"|Versie
!style="text-align:left;"|Datum
!style="text-align:left;"|Bron
!style="text-align:left;"|Organisatie
|-
| style="background-color: white;"| -
| style="background-color: white;"| Persoonlijke Gezondheidsomgeving
| style="background-color: white;"|
| style="background-color: white;"| 06-12-2018
| style="background-color: white;"| https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/
| style="background-color: white;"| Patiëntenfederatie Nederland
|-
| style="background-color: white;"| -
| style="background-color: white;"| Rendered Media Types
| style="background-color: white;"|
| style="background-color: white;"| 10-12-2018
| style="background-color: white;"| http://dicom.nema.org/medical/dicom/2017d/output/html/part18.html#table_6.1.1-3
| style="background-color: white;"| NEMA (DICOM)
|-
| style="background-color: white;"| -
| style="background-color: white;"| Exif
| style="background-color: white;"|
| style="background-color: white;"| 10-12-2018
| style="background-color: white;"| https://en.wikipedia.org/wiki/Exif
| style="background-color: white;"| Wikipedia
|}

'''Referenties

=Bijlage: Documenthistorie=

==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:V2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

{| class="wikitable" "cellpadding="10" style="background-color: white;"
!style="text-align:left;"|Release
!style="text-align:left;"|Versie
!style="text-align:left;"|BITS issue
!style="width:850px; text-align:left;"|Omschrijving

{{ReleaseNotes|package=2019.01 - April|release=1.0.5|issues=2|MM-1032|MM-954}}
{{ReleaseNotes|package=2019.01 - Maart|release=1.0.4|issues=1|MM-1007}}
|-
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
|-
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
|}

==Paginahistorie==
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Datum
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor april 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Maart 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Wijzigingen voor maart 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Februari 2020
| style="background-color: white; | 27-02-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Januari 2020
| style="background-color: white; | 27-01-2020
| style="background-color: white;"|
* Wijzigingen voor januari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 28-11-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 13-05-2019
| style="background-color: white;"|
* Versie 1.0.0 gepubliceerd.
|}

MedMij:Vprepub-2019.01 OntwerpBeelden

2020-05-01T07:33:59Z

Stephan Opdenberg: versie package verhoogd

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp Beelden {{VersieInfo|V2019.01|Beelden}}}}

[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:beeldenIcoon.png|link=|87px |links||media]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_Images|Technisch]]
desc none
</imagemap>

=Inleiding=
==Algemeen==
Deze pagina beschrijft het functioneel ontwerp voor de uitwisseling van beelden binnen MedMij. De algemene inleiding van de MedMij functionele ontwerpen kan [[MedMij:V2019.01_Ontwerpen| hier]] gevonden worden.

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de MedMij functionele ontwerpen, die [[MedMij:V2019.01_Ontwerpen#Doelgroep| hier]] gevonden kan worden.

==Kaders en uitgangspunten==
===Richtlijn===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Richtlijn| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

=Use Cases=
==Use case 1: Sturen beelden vanuit een PGO==
=== Doel en relevantie ===
*Het voor patiënten/ personen mogelijk maken regie op hun eigen gezondheid te nemen door beelden te sturen naar (verschillende) zorgaanbieders.
*Deze use case ondersteunt geen interactie met de patiënt middels het PGO. De zorgverlener kan niet online reageren op de gestuurde beelden. De zorgverlener dient buiten deze use case om de beelden te bespreken met de patiënt.

=== Domein ===
Beelden in het domein van zorgaanbieders en patiënten/ personen.

=== Context ===
Het gaat om het elektronisch en gestructureerd sturen van beelden vanuit een [[#persoonlijke-gezondheidsomgeving|persoonlijke gezondheidsomgeving]] (PGO) naar een zorgaanbiederssysteem (XIS). Deze pagina bevat (verwijzingen naar) beschrijvingen van:
* informatie,
* bedrijfsrollen (actoren),
* proces,
* systemen,
* systeemrollen,
* transactiegroepen en transacties, inclusief de inhoud van deze transacties.

De beschrijving is infrastructuur-onafhankelijk.

=== Informatie ===
Bij het sturen van beelden gaat het om de volgende informatie die uitgewisseld wordt: de beelden, bijbehorende meta-informatie per beeld en een mogelijk toelichting/ begeleidende tekst.

De informatie-elementen voor sturen en ontvangen van een beeld of collectie beelden staan in [http://decor.nictiz.nl/pub/beelden/bd-html-20190512T171559/tr-2.16.840.1.113883.2.4.3.11.60.54.4.2-2019-02-25T131649.html ART-DECOR Sturen Beelden].

==== Beeldformaat ====
*De ontvangende systemen dienen de volgende gegevensformaten te ondersteunen: JPEG, PNG, GIF en JP2. De PGO bepaalt zelf in welke van deze ondersteunende beeldformaten, de beelden worden verstuurd. De genoemde beeldformaten zijn ook de gegevensformaten, bestaande uit één frame, die door [[#DICOM-beeldformaten|DICOM standaard]] worden gespecificeerd voor gebruik bij DICOM web-services. Binnen deze use case zijn dit de enige gebruikte gegevensformaten voor beelden. Beeldformaat DICOM is niet in scope voor deze use case.
*Beelden mogen extra (meta)informatie bevatten in bijvoorbeeld de [[#Exif|Exif standaard]]. Een voorbeeld is het opslaan van patiëntgegevens binnen het beeldformaat JPEG. Hier wordt in deze use case echter geen gebruik van gemaakt.

==== Frequentie sturen beeld(en) ====
*Met het oog op bijvoorbeeld een ''denial of service attack'' is de overweging geweest om de frequentie waarmee de patiënt beelden kan versturen te beperken. Besloten is om voorlopig geen beperkingen op te nemen in de standaard.

==== Grootte van beeld(en) ====
De maximale grootte van een beeld is 20 MB (voordat het Base64 encoded is). Een PGO kan één tot maximaal 3 beelden tegelijk sturen. De maximale grootte van een collectie beelden is 60 MB. Base64 codering maakt het resultaat 37% groter.

==== Toelichting ====
De patiënt kan per beeld en/of per collectie beelden een begeleidende tekst meegeven. Dit gaat middels de 'toelichting' meta-informatie elementen.

==== Meta-informatie ====
Het beeld dient te worden voorzien van voldoende meta-informatie om door het ontvangende systeem goed te kunnen worden geïnterpreteerd. De specificatie van de meta-informatie wordt gegeven in de dataset en transactiebeschrijving. Daarnaast kent het FHIR profiel, verwezen vanuit het technisch ontwerp, nog een aantal verplichte concepten.
Deze use case houdt rekening met zelfstandige XIS-sen en met XIS-sen die zijn aangesloten op een XDS-netwerk door het bericht te voorzien van voldoende meta-informatie voor indexatie. Het correct indexeren van beelden in een XDS netwerk is de verantwoordelijkheid van het ontvangende XIS. Het technische ontwerp geeft een niet-normatieve implemenatierichtlijn middels een mapping van het FHIR bericht naar XDS concepten en het IHE MHD profiel.

=== Bedrijfsrollen ===
Deze use case onderscheidt twee bedrijfsrollen, namelijk de ''Patiënt'' en de ''Zorgaanbieder'' zoals te zien in onderstaande tabel.

{| class="wikitable" "cellpadding="10" width="100%"
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil beelden sturen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Wil beelden ontvangen
|}
'''Bedrijfsrollen sturen beelden'''

Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd.

[[Image:Activity_Diagram_-_Sturen_Beelden.png|Activiteitendiagram sturen beelden]]

'''Activiteitendiagram sturen beelden'''

=== Procesbeschrijving ===
==== Patient Journey – Thomas van Beek ====
Een voorbeeldsituatie die de meerwaarde van het sturen van beelden vanuit het PGO schetst is de patiënt journey van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Thomas_van_Beek_MedMij.pdf Thomas van Beek].
<blockquote>De afgelopen periode heeft Thomas wisselend last van eczeem. De vorige keer dat Thomas een dergelijke aanval had, waren de klachten al afgenomen op het moment dat de afspraak met de huisarts plaatsvond. Om de ernst van de klachten te kunnen inschatten heeft de huisarts gevraagd of Thomas in het vervolg een foto kan maken van de eczeem wanneer deze in alle ernst aanwezig zijn.
Vandaag is het weer zover. Bij het maken van de afspraak met de huisarts verzoekt de assistente of Thomas direct een foto kan maken en deze de huisarts wil toesturen. Thomas maakt foto's van onder andere zijn gezicht en upload deze naar zijn PGO. Een paar dagen na het versturen van de foto heeft hij een afspraak bij de huisarts. De foto's komen tijdens het consult ter sprake en een passende behandeling wordt gekozen.</blockquote>

==== Patient Journey – Kenneth van Someren ====
Een tweede voorbeeld waarbij de meerwaarde van het sturen van beelden vanuit het PGO geschetst kan worden is de patiënt journey van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Kenneth_van_Someren_MedMij.pdf Kenneth van Someren].

<blockquote>De grote antieke stoel in de woonkamer is het plekje waar Kenneth thuis graag te vinden is. De stoel begon echter de laatste tijd steeds minder lekker te zitten. De zuster adviseert regelmatig af te wisselen met de bank, maar de televisie is lang niet zo interessant als het dorpsplein aan de overkant van de straat. Het begon met enkel een klein rood plekje op zijn ruggengraat, maar inmiddels begon dit vormen aan te nemen die ook dochter Debby zorgen baarde. Na kort overleg met de thuiszorg besluit ze telefonisch contact op te nemen met de wondverpleegkundige van de organisatie. Deze vraagt om een duidelijke foto te maken en via het PGO te sturen voor beoordeling. De wondverpleegkundige ziet de foto en vind het ook zorgelijk. Daarom maak ze direct een afspraak met Kenneth om de plek zelf te beoordelen. De volgende ochtend lukt dat al en die middag komt de thuiszorg met de juiste kennis en materialen om de wond te behandelen.</blockquote>

==== Proces ====
Het stuk van het proces waar het in deze use case omgaat is:
* Patiënt en zorgverlener maken de afspraak dat de patient een beeld kan sturen aan de zorgverlener.
* Patiënt maakt, ontvangt of downloadt één of meerdere beelden en uploadt deze naar zijn PGO. De beelden kunnen gemaakt zijn door de patiënt, een zorgaanbieder of iemand anders.
* Patiënt heeft de mogelijkheid om een begeleidende tekst van maximaal 1 MB toe te voegen aan het beeld en/of beelden.
* Het PGO stuurt de beelden naar het systeem van de zorgaanbieder.
** Mogelijk moet of kan de patiënt metagegevens behorende bij de beelden aanvullen of invullen.
* De zorgaanbieder raadpleegt de beelden in zijn eigen dossier (XIS).
* De zorgverlener bespreekt het beeld buiten het PGO om met de patiënt. Deze use-case ondersteunt geen interactie met de patiënt middels het PGO.

Deze paragraaf vervolgt met een beschrijving van precondities, processtappen, en postcondities.

===== Preconditie =====
* De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van beelden tussen het eigen PGO en de betreffende XIS.
* De patiënt en zorgaanbieder hebben onderling afspraken gemaakt over het sturen van beelden.
* Het XIS van de zorgaanbieder is in staat afbeeldingen van de patient te ontvangen.
* De beelden bevinden zich in of zijn toegankelijk voor, het PGO

===== Processtappen =====
* Het systeem van de patiënt (PGO) stuurt de beelden naar het systeem van de zorgaanbieder (XIS).
* Het systeem van de zorgaanbieder (XIS) ontvangt de beelden van het PGO.

===== Postconditie =====
* Indien het systeem van de zorgaanbieder (XIS) gebruik maakt van een XDS-omgeving zal dit systeem de beelden op gepaste wijze in het netwerk registreren.
* De zorgaanbieder gebruikt het systeem (XIS) om de beelden te kunnen zien en/of beoordelen.

=== Systemen & Systeemrollen ===
Zowel de patiënt als de zorgaanbieder maken ieder gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om beelden van de patiënt naar de zorgaanbieder.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| Sturen van Beelden
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Beelden}}-BES-FHIR
| style="background-color: white;"| Sturen van beelden naar zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| Ontvangen van Beelden
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Beelden}}-BEO-FHIR
| style="background-color: white;"| Ontvangen van beelden vanuit het PGO
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:Component_Diagram_-_Sturen_Beelden_(Totaal).png|Componenten diagram]]

'''Componenten diagram van systemen en systeemrollen'''

=== Transacties & Transactiegroepen ===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een stuur- en ontvangstbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:middle;" rowspan="2"|Beelden (PUSH)
|style="background-color: white;vertical-align:top;"|Sturen Beelden
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Beelden}}-BES-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_Images |Beelden in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Ontvangen Beelden
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Beelden}}-BEO-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:Use_Case_Diagram_-_Sturen_Beelden.png|Use case diagram Sturen Beelden]]

'''Use case diagram sturen beelden

=Functionaliteit=

== Eisen en wensen ==
*'''Afstemming vooraf''': Tijdens de ontwikkeling van de informatiestandaard is er nagedacht over het opnemen van een verplichte checkbox die de patiënt moet aanvinken om aan te geven dat er afstemming is geweest met de zorgverlener. Uiteindelijk is besloten om deze eis niet op te nemen in de standaard omdat in de praktijk patiënt en zorgverlener altijd een context hebben waarin het sturen van de beelden past. Daarnaast is het uitgangspunt om de patiënt zo min mogelijk te laten invullen bij het sturen van een beeld.

== Niet functionele eisen en wensen ==
Het technisch ontwerp bevat een aantal verplichte (technische) data elementen die niet zijn opgenomen in de functionele dataset. Een aantal van deze velden zijn verplicht gesteld om compatibiliteit met XDS-netwerken te ondersteunen. Het gaat om de volgende elementen:

* Indentificatie van het beeld en collectie beelden
* Een hash van de data van het beeld

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="text-align:left;"|Auteur(s)
!style="text-align:left;"|Titel
!style="text-align:left;"|Versie
!style="text-align:left;"|Datum
!style="text-align:left;"|Bron
!style="text-align:left;"|Organisatie
|-
| style="background-color: white;"| -
| style="background-color: white;"| Persoonlijke Gezondheidsomgeving
| style="background-color: white;"|
| style="background-color: white;"| 06-12-2018
| style="background-color: white;"| https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/
| style="background-color: white;"| Patiëntenfederatie Nederland
|-
| style="background-color: white;"| -
| style="background-color: white;"| Rendered Media Types
| style="background-color: white;"|
| style="background-color: white;"| 10-12-2018
| style="background-color: white;"| http://dicom.nema.org/medical/dicom/2017d/output/html/part18.html#table_6.1.1-3
| style="background-color: white;"| NEMA (DICOM)
|-
| style="background-color: white;"| -
| style="background-color: white;"| Exif
| style="background-color: white;"|
| style="background-color: white;"| 10-12-2018
| style="background-color: white;"| https://en.wikipedia.org/wiki/Exif
| style="background-color: white;"| Wikipedia
|}

'''Referenties

=Bijlage: Documenthistorie=

==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:V2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

{| class="wikitable" "cellpadding="10" style="background-color: white;"
!style="text-align:left;"|Release
!style="text-align:left;"|Versie
!style="text-align:left;"|BITS issue
!style="width:850px; text-align:left;"|Omschrijving

{{ReleaseNotes|package=2019.01 - April|release=1.0.5|issues=2|MM-1032|MM-954}}
{{ReleaseNotes|package=2019.01 - Maart|release=1.0.4|issues=1|MM-1007}}
|-
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
|-
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
|}

==Paginahistorie==
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Datum
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor april 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Maart 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Wijzigingen voor maart 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Februari 2020
| style="background-color: white; | 27-02-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Januari 2020
| style="background-color: white; | 27-01-2020
| style="background-color: white;"|
* Wijzigingen voor januari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 28-11-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 13-05-2019
| style="background-color: white;"|
* Versie 1.0.0 gepubliceerd.
|}

MedMij:V2019.01 OntwerpGGZ

2020-05-01T07:32:50Z

Stephan Opdenberg: versie package verhoogd

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp Basisgegevens GGZ {{VersieInfo|V2019.01|BgGGZ}} (op basis van zibs release 2017)}}

[[Bestand:MedMij-GGZ-63.png |link=|links|80px|Use case GGZ|GGZ]]
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_GGZ|Technisch]]
desc none
</imagemap>

=Inleiding=

==Algemeen==
Deze pagina beschrijft het functioneel ontwerp voor de uitwisseling van Basisgegevens GGZ op basis van een selectie zorginformatiebouwstenen (zibs) binnen MedMij. De algemene inleiding van de MedMij functionele ontwerpen kan [[MedMij:V2019.01_Ontwerpen| hier]] gevonden worden.

Binnen het [https://www.vippggz.nl/regeling/doelstellingen.html VIPP GZZ programma] zijn een drietal modules opgenomen:
* Module "Patiënt & Informatie": de Basisgegevens GGZ is bedoeld voor deze module.
* Module "Patiënt & Medicatie": hiervoor wordt verwezen naar het [[MedMij:V2019.01_OntwerpMedicatie| functioneel ontwerp]] voor [https://www.nictiz.nl/programmas/medicatieproces Medicatieproces 9.0].
* Module "Patiënt & eHealth".

Voor de module "Patiënt & Informatie" is een [https://zoek.officielebekendmakingen.nl/stcrt-2018-60877.html#d17e2089 lijst van verplichte zorginformatiebouwstenen (zibs)] vastgesteld die geschikt zijn verklaard voor de GGZ sector, de Basisgegevens GGZ. Deze lijst omvat momenteel alleen de reeds beschikbare zibs (publicatie 2017) met minimale inhoud en structuur als opmaat naar een volwaardige GGZ informatiestandaard (in ontwikkeling door GGZ Nederland en Nictiz). De lijst van zibs en hierop gebaseerd specificaties vertoont enige overlap met de [https://www.nictiz.nl/standaardisatie/informatiestandaarden/basisgegevensset-zorg-bgz Basisgegevensset Zorg (BgZ)] maar is zeker niet hetzelfde: zie [[MedMij:V2019.01_OntwerpGGZ#Informatie| Informatie]] voor een nadere toelichting over het samenstellen van de inhoud.

De use cases voor de toekomstige GGZ informatiestandaard zijn nog niet omschreven, echter staat voor het VIPP GGZ programma het perspectief van de patiënt centraal. Het doel van deze pagina is dan ook om de uitwisseling van de Basisgegevens GGZ met de patiënt te omschrijven.

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de MedMij functionele ontwerpen, die [[MedMij:V2019.01_Ontwerpen#Doelgroep| hier]] gevonden kan worden.

==Kaders en uitgangspunten==
===Richtlijn===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Richtlijn| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

===Specifieke informatie over deze kwalificatie===
Specifieke informatie over de kwalificatie van de transacties 'Raadplegen GGZ' en 'Beschikbaarstellen GGZ' is [[MedMij:V2019.01_ToelichtingKwalificatieGGZ| hier]] te vinden.

=Use Cases=
==Use case 1: Raadplegen Basisgegevens GGZ in persoonlijke gezondheidsomgeving==
=== Doel en relevantie ===
Het voor patiënten mogelijk maken regie op hun eigen gezondheid te nemen door inzicht te geven in de Basisgegevens GGZ die over henzelf gaan.

=== Domein ===
Basisgegevens GGZ in het domein van zorgaanbieders en patiënten.

=== Context ===
Het gaat om het elektronisch en gestructureerd beschikbaar maken van de Basisgegevens GGZ vanuit een zorgaanbiederssysteem (XIS) naar een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO).
Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie,
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.

De beschrijving is infrastructuur-onafhankelijk.

=== Informatie ===
De Basisgegevens GGZ bestaat uit een selectie van 24 zibs. Deze zibs vormen samen een verzameling van gegevens die binnen de GGZ sector toepasbaar zijn. Hierbij bestaat de selectie voorlopig alleen uit reeds bestaande zibs (publicatie 2017) die voor de GGZ sector geschikt zijn met een minimale inhoud en structuur zoals te vinden in dit [[MedMij:V2019.01_InhoudGGZ|overzicht]]. Bij de ontwikkeling van de volwaardige GGZ informatiestandaard wordt dit nader gespecificeerd, met nadere uitwerking van GGZ-specifieke gegevens die nog niet gedekt worden door bestaande zibs. De Basisgegevens GGZ zal in de toekomst hiermee worden aangevuld. De huidige lijst aan geselecteerde zibs komt voor een deel overeen met de [https://www.nictiz.nl/standaardisatie/informatiestandaarden/basisgegevensset-zorg-bgz/ Basisgegevensset Zorg (BgZ)], maar voor een deel ook niet: het gaat om twee aparte sets. Zie het [[MedMij:V2019.01_InhoudGGZ|overzicht van de inhoud]] voor een nadere toelichting.

Medicatiegegevens vallen buiten de Basisgegevens GGZ, omdat hiervoor gebruik wordt gemaakt van het reeds bestaande [https://www.nictiz.nl/programmas/medicatieproces Medicatieproces 9.0] (zie [[MedMij:V2019.01_OntwerpMedicatie| hier]] voor uitwisseling medicatiegegevens in PGO).

In de bestaande zibs valt de zogenaamde juridische status en vertegenwoordiging binnen de zib VrijheidsbeperkendeMaatregelen. Voor de GGZ sector is het loskoppelen van dit gegeven (als losstaande zib) van groot belang, omdat deze ook relevant is buiten de toepassing van vrijheidsbeperkende maatregelen. In de verdere uitwerking van de Basisgegevens GGZ is het element JuridischeStatus losgekoppeld van de verdere zib VrijheidsbeperkendeMaatregelen. Deze loskoppeling wordt tevens als wijzigingsverzoek behandeld bij de nieuwe publicatie zibs: de huidige uitwerking loopt op deze toekomstige ontwikkeling vooruit.

In de MedMij FHIR implementatie gids staat de technische representatie van de betreffende zibs in zogenaamde FHIR profielen. In dit [[MedMij:V2019.01_FHIR_GGZ#List_of_StructureDefinitions|overzicht]] is te zien welk FHIR profiel bij welke zib hoort.

=== Bedrijfsrollen ===
Deze use case onderscheidt twee bedrijfsrollen, namelijk de ''Patiënt'' en de ''Zorgaanbieder'' zoals te zien in onderstaande tabel.

{| class="wikitable" "cellpadding="10" width="100%"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Bedrijfsrol'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil de eigen Basisgegevens GGZ raadplegen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Stelt de Basisgegevens GGZ beschikbaar
|}
'''Bedrijfsrollen Basisgegevens GGZ'''

Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd.

[[Image:InzienGGZ_activity.png|Activiteitendiagram Raadplegen GGZ]]

'''Activiteitendiagram Raadplegen GGZ'''

=== Procesbeschrijving ===
==== Patient journey - Jelmer Postma ====
De 'patient journey' van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Jelmer_Postma_MedMij.pdf Jelmer Postma] beschrijft enkele momenten waarop je als patiënt zijnde inzicht kan of zou willen hebben in zijn/haar Basisgegevens GGZ.

<blockquote>In zijn PGO kan Jelmer doorlezen wat de huisarts voorgeschreven heeft en vindt hij de verwijzing voor een psycholoog. Hij zoekt een psycholoog uit en maakt een afspraak waarbij hij de verwijzing bijvoegt.</blockquote>

<blockquote>‘Pling’, Jelmer krijgt van zijn PGO een reminder dat hij morgen om 10.00 zijn eerste afspraak heeft bij de psycholoog. Tevens kan hij vanuit zijn PGO een vragenlijst invullen voor de psycholoog over zijn klachten, gezondheid en verwachtingen. Wat zijn huisarts al vermoedde, wordt door de psycholoog bevestigd.</blockquote>

<blockquote>Gedurende de sessie komen er onverwerkte zaken uit zijn jeugd boven. Deze zijn zo heftig dat Jelmer in een acute depressie belandt. Zijn vriendin Karin geeft aan dat Jelmer op het moment niet thuis kan wonen en samen met de huisarts nemen ze het besluit dat Jelmer voor korte duur opgenomen wordt bij een GGZ-instelling in de buurt. Hier wordt een nieuw behandelplan opgesteld waarin groepstherapie een onderdeel gaat worden. Jelmer heeft Karin gemachtigd om in zijn PGO te kijken zodat ze onder andere het behandelplan in kan zien en ze goed betrokken wordt.</blockquote>

<blockquote>De opname in de GGZ-instelling is van korte duur. Vanaf nu wordt Jelmer ambulant behandeld door een reguliere GGZ-instelling. Gelukkig is deze met 5 minuten fietsen van huis lekker dichtbij. De psychiater van de instelling schrijft een overdracht voor zijn nieuwe hoofdbehandelaar. Zowel Karin als Jelmer kunnen via het PGO inzien wat daarin staat. Daarom weten ze nu dat de medicatie is aangepast.</blockquote>

==== Proces ====
Het stuk van het proces waar het in deze use case om gaat is:
* Het systeem van een zorgaanbieder (XIS) stelt de Basisgegevens GGZ van de patiënt beschikbaar aan het systeem van een patiënt (PGO).

Deze paragraaf vervolgt met een beschrijving van precondities, proces stappen, en post condities.

===== Preconditie =====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van de Basisgegevens GGZ tussen het betreffende XIS en het eigen PGO.

De Basisgegevens GGZ, of een gedeelte van de Basisgegevens GGZ, welke de persoon wil inzien, bestaat en de zorgaanbieder wil deze beschikbaar stellen.
:Soms zijn er valide redenen om de Basisgegevens GGZ, of gedeeltes daarvan, tijdelijk nog niet beschikbaar te stellen aan de patiënt. Bijvoorbeeld omdat de zorgverlener deze eerst zelf wil interpreteren en/of er eerst met de patiënt over wil spreken.
:Een patiënt kan steeds zelf het initiatief nemen om de Basisgegevens GGZ op te halen, maar het is ook mogelijk dat een PGO geconfigureerd is om dit 'automatisch' te doen. Dit maakt voor de scope van deze use case beschrijving geen verschil.

===== Proces stappen =====
* Het systeem van de patiënt (PGO) raadpleegt het systeem van de zorgaanbieder (XIS) voor de Basisgegevens GGZ van de patiënt.
* Het systeem van de zorgaanbieder (XIS) maakt (een deel van) de Basisgegevens GGZ beschikbaar voor de patiënt.
* De patiënt gebruikt de persoonlijke gezondheidsomgeving om de Basisgegevens GGZ in te zien.

===== Post conditie =====
De persoon kan de Basisgegevens GGZ inzien via een persoonlijke gezondheidsomgeving.

=== Systemen & Systeemrollen ===
Zowel de persoon als de zorgaanbieder maken ieder gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om de Basisgegevens GGZ van zorgaanbieder naar de persoon.

{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Systeem
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Naam systeemrol
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Systeemrolcode
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| GGZRaadplegend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|BgGGZ}}-GGR-FHIR
| style="background-color: white;"| Raadplegen Basisgegevens GGZ bij zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| GGZBeschikbaarstellend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|BgGGZ}}-GGB-FHIR
| style="background-color: white;"| Beschikbaarstellen Basisgegevens GGZ aan de patiënt
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:InzienGGZ_componenten.png.PNG|Componenten diagram]]

'''Componenten diagram van systemen en systeemrollen'''

=== Transacties & Transactiegroepen ===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Transactiegroep'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Transactie'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Systeemrolcode'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Systeem'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Bedrijfsrol'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:middle;" rowspan="2"|GGZ (PULL)
|style="background-color: white;vertical-align:top;"|[https://decor.nictiz.nl/decor/services/RetrieveTransaction?id=2.16.840.1.113883.2.4.3.11.60.57.4.2&effectiveDate=2019-03-05T17:07:53&language=nl-NL&ui=nl-NL&format=html&hidecolumns=34567 Raadplegen GGZ]
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|BgGGZ}}-GGR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_GGZ |GGZ in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|[https://decor.nictiz.nl/decor/services/RetrieveTransaction?id=2.16.840.1.113883.2.4.3.11.60.57.4.3&effectiveDate=2019-03-05T17:07:53&language=nl-NL&ui=nl-NL&format=html&hidecolumns=34567 Beschikbaarstellen GGZ]
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|BgGGZ}}-GGB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:InzienGGZ_useCase.png|Use case diagram raadplegen Basisgegevens GGZ]]

'''Use case diagram raadplegen Basisgegevens GGZ

=Functionaliteit=
Er zijn geen aanwijzingen/eisen voor functionaliteit van de systemen.

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Auteur(s)
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Titel
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Versie
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Datum
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Bron
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Organisatie
|-
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
|}
'''Referenties

=Bijlage: Documenthistorie=

==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:V2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

{| class="wikitable" "cellpadding="10" style="background-color: white;"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Release
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Versie
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|BITS issue
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black; width:850px;"|Omschrijving

{{ReleaseNotes|package=2019.01 - April|release=1.1.12|issues=3|MM-1025|MM-1003|MM-939}}
{{ReleaseNotes|package=2019.01 - Maart|release=1.1.10|issues=4|MM-997|MM-953|MM-931|MM-657}}
|-
| rowspan = 2 style="background-color: white; | 2019.01 - November
| style="background-color: white; | 1.1.7
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-806 MM-806]
| style="background-color: white;"| Fixed MM-430: adjusted incorrect FHIRPath constraints, moved extension to Consent.extension and moved mappings in extension from extension.value[x].reference to extension.value[x] in zib TreatmentDirective profile.
|-
| style="background-color: white; | 1.1.6
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-430 MM-430]
| style="background-color: white;"| The TreatmentDirective profile allowed at most 1 reference to an AdvanceDirective resource, because of restrictions in the FHIR base. There is now an extension inside the source element to allow referencing additional AdvanceDirective resources.
|-
| style="background-color: white; | 2019.01 - Oktober
| style="background-color: white; | 1.1.5
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-594 MM-594]
| style="background-color: white;"| Updated date time example in profile to include timezone as required by the FHIR specification.
|-
| rowspan = 4 style="background-color: white;"| 2019.01 - September
| rowspan = 4 style="background-color: white;"| 1.1.4
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-358 MM-358]
| style="background-color: white;"| Tekstcorrectie op de kwalificatie pagina ToelichtingKwalificatieGGZ.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-336 MM-336]
| style="background-color: white;"| Aanpassen ConceptMap InterpretatieVlaggenCodelijst-to-observation-interpretation
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-327 MM-327]
| style="background-color: white;"|
Fixed reference to generalPractitioner in examples nl-core-patient-languageProficiency - example.xml and nl-core-patient-legalStatus - example.xml.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-322 MM-322]
| style="background-color: white;"| Aanpassen conceptnaam ResultaatVlaggen naar InterpretatieVlaggen in FHIR profiel voor LaboratoryResults.
|-
| rowspan = 10; style="background-color: white;"| 2019.01
|-
| rowspan = 3; style="background-color: white;"| 1.1.3
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-346 MM-346]
| style="background-color: white;"| Ongeldig discriminator pad in code slicing in zib Verrichting
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-294 MM-294]
| style="background-color: white;"| Naam mapping binnen div. FHIR profielen aangepast conform zib: HCIM LaboratoryTestResult-v4.1(2017EN).
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-252 MM-252]
| style="background-color: white;"| FreedomRestrictingMeasures incorrecte terminologie in profiel en technisch ontwerp pagina
|-
| style="background-color: white;"| 1.1.1
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-206 MM-206]
| style="background-color: white;"| Reference vanuit Observation naar Specimen Isolate onjuist.
|-
| rowspan = 5; style="background-color: white;"| 1.1.0
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-143 MM-143]
| style="background-color: white;"| Aanpassing modellering Procedure.performer in het profiel voor HCIM Verrichting.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-118 MM-118]
| style="background-color: white;"| Profiel naam zib-Product niet passend bij zib FarmaceutischProduct.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-100 MM-100]
| style="background-color: white;"| Mapping CBV naar SNOMED codes.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-99 MM-99]
| style="background-color: white;"| Interval heeft Period maar geen PeriodUnit op simplifier.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-50 MM-50]
| style="background-color: white;"| Contact ondersteunt geen klinische contacten.
|-
| rowspan = 4; style="background-color: white;"| 2018.06
| rowspan = 4; style="background-color: white;"| 1.0.0
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-128 MM-128]
| style="background-color: white;"| CanceledIndicator possible values.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-66 MM-66]
| style="background-color: white;"| Update mappings LaboratoriumUitslag in DiagnosticReport en Observation.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-55 MM-55]
| style="background-color: white;"| Profile for HCIM TobaccoUse was missing a specification for PackYears unit - profile updated to 2.0.1.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-54 MM-54]
| style="background-color: white;"| Wrong SNOMED code in search URL for FunctionalOrMentalStatus in BgZ and GGZ.
|}

==Paginahistorie==
{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Release
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Datum
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor april 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Maart 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Wijzigingen voor maart 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Februari 2020
| style="background-color: white; | 27-02-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Januari 2020
| style="background-color: white; | 27-01-2020
| style="background-color: white;"|
* Wijzigingen voor januari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 10-12-2019
| style="background-color: white;"|
* Wijzigingen voor november patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 28-11-2019
| style="background-color: white;"|
* Wijzigingen voor november patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Oktober
| style="background-color: white; | 30-10-2019
| style="background-color: white;"|
* Wijzigingen voor oktober patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 27-06-2019
| style="background-color: white;"|
* Toevoeging release notes voor patches. Ophogen versie nummers naar 1.1.3.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-04-2019
| style="background-color: white;"|
* Toelichting over de verschillende modules van het VIPP GGZ programma, waarvan de Basisgegevens GGZ 1 module beslaat.
* Toevoeging transactie specificaties op ART-DECOR.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 28-03-2019
| style="background-color: white;"|
* Plaatsen release notes behorende bij patch 1.
* Versienummer systeemrol codes ophogen met 1 patch nummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"|
*Wijzigingen gepubliceerd in versie 2019.01, zie release notes.
*Verplaatsing release notes naar functionele pagina.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 01-11-2018
| style="background-color: white;"|
* Toevoeging verwijzing naar gepubliceerde VIPP GGZ regeling en uitgangspunten voor kwalificatie.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 15-10-2018
| style="background-color: white;"|
* Aanpassing versienummer in titel.
* Toevoeging documenthistorie.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 26-09-2018
| style="background-color: white;"|
* Toevoeging toelichting over de inhoud m.b.t. overlap en verschillen met de Basisgegevensset Zorg (BgZ).
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 10-09-2018
| style="background-color: white;"|
* Eerste conceptversie.
|}

MedMij:Vprepub-2019.01 OntwerpGGZ

2020-05-01T07:32:50Z

Stephan Opdenberg: versie package verhoogd

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp Basisgegevens GGZ {{VersieInfo|V2019.01|BgGGZ}} (op basis van zibs release 2017)}}

[[Bestand:MedMij-GGZ-63.png |link=|links|80px|Use case GGZ|GGZ]]
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_GGZ|Technisch]]
desc none
</imagemap>

=Inleiding=

==Algemeen==
Deze pagina beschrijft het functioneel ontwerp voor de uitwisseling van Basisgegevens GGZ op basis van een selectie zorginformatiebouwstenen (zibs) binnen MedMij. De algemene inleiding van de MedMij functionele ontwerpen kan [[MedMij:V2019.01_Ontwerpen| hier]] gevonden worden.

Binnen het [https://www.vippggz.nl/regeling/doelstellingen.html VIPP GZZ programma] zijn een drietal modules opgenomen:
* Module "Patiënt & Informatie": de Basisgegevens GGZ is bedoeld voor deze module.
* Module "Patiënt & Medicatie": hiervoor wordt verwezen naar het [[MedMij:V2019.01_OntwerpMedicatie| functioneel ontwerp]] voor [https://www.nictiz.nl/programmas/medicatieproces Medicatieproces 9.0].
* Module "Patiënt & eHealth".

Voor de module "Patiënt & Informatie" is een [https://zoek.officielebekendmakingen.nl/stcrt-2018-60877.html#d17e2089 lijst van verplichte zorginformatiebouwstenen (zibs)] vastgesteld die geschikt zijn verklaard voor de GGZ sector, de Basisgegevens GGZ. Deze lijst omvat momenteel alleen de reeds beschikbare zibs (publicatie 2017) met minimale inhoud en structuur als opmaat naar een volwaardige GGZ informatiestandaard (in ontwikkeling door GGZ Nederland en Nictiz). De lijst van zibs en hierop gebaseerd specificaties vertoont enige overlap met de [https://www.nictiz.nl/standaardisatie/informatiestandaarden/basisgegevensset-zorg-bgz Basisgegevensset Zorg (BgZ)] maar is zeker niet hetzelfde: zie [[MedMij:V2019.01_OntwerpGGZ#Informatie| Informatie]] voor een nadere toelichting over het samenstellen van de inhoud.

De use cases voor de toekomstige GGZ informatiestandaard zijn nog niet omschreven, echter staat voor het VIPP GGZ programma het perspectief van de patiënt centraal. Het doel van deze pagina is dan ook om de uitwisseling van de Basisgegevens GGZ met de patiënt te omschrijven.

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de MedMij functionele ontwerpen, die [[MedMij:V2019.01_Ontwerpen#Doelgroep| hier]] gevonden kan worden.

==Kaders en uitgangspunten==
===Richtlijn===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Richtlijn| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

===Specifieke informatie over deze kwalificatie===
Specifieke informatie over de kwalificatie van de transacties 'Raadplegen GGZ' en 'Beschikbaarstellen GGZ' is [[MedMij:V2019.01_ToelichtingKwalificatieGGZ| hier]] te vinden.

=Use Cases=
==Use case 1: Raadplegen Basisgegevens GGZ in persoonlijke gezondheidsomgeving==
=== Doel en relevantie ===
Het voor patiënten mogelijk maken regie op hun eigen gezondheid te nemen door inzicht te geven in de Basisgegevens GGZ die over henzelf gaan.

=== Domein ===
Basisgegevens GGZ in het domein van zorgaanbieders en patiënten.

=== Context ===
Het gaat om het elektronisch en gestructureerd beschikbaar maken van de Basisgegevens GGZ vanuit een zorgaanbiederssysteem (XIS) naar een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO).
Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie,
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.

De beschrijving is infrastructuur-onafhankelijk.

=== Informatie ===
De Basisgegevens GGZ bestaat uit een selectie van 24 zibs. Deze zibs vormen samen een verzameling van gegevens die binnen de GGZ sector toepasbaar zijn. Hierbij bestaat de selectie voorlopig alleen uit reeds bestaande zibs (publicatie 2017) die voor de GGZ sector geschikt zijn met een minimale inhoud en structuur zoals te vinden in dit [[MedMij:V2019.01_InhoudGGZ|overzicht]]. Bij de ontwikkeling van de volwaardige GGZ informatiestandaard wordt dit nader gespecificeerd, met nadere uitwerking van GGZ-specifieke gegevens die nog niet gedekt worden door bestaande zibs. De Basisgegevens GGZ zal in de toekomst hiermee worden aangevuld. De huidige lijst aan geselecteerde zibs komt voor een deel overeen met de [https://www.nictiz.nl/standaardisatie/informatiestandaarden/basisgegevensset-zorg-bgz/ Basisgegevensset Zorg (BgZ)], maar voor een deel ook niet: het gaat om twee aparte sets. Zie het [[MedMij:V2019.01_InhoudGGZ|overzicht van de inhoud]] voor een nadere toelichting.

Medicatiegegevens vallen buiten de Basisgegevens GGZ, omdat hiervoor gebruik wordt gemaakt van het reeds bestaande [https://www.nictiz.nl/programmas/medicatieproces Medicatieproces 9.0] (zie [[MedMij:V2019.01_OntwerpMedicatie| hier]] voor uitwisseling medicatiegegevens in PGO).

In de bestaande zibs valt de zogenaamde juridische status en vertegenwoordiging binnen de zib VrijheidsbeperkendeMaatregelen. Voor de GGZ sector is het loskoppelen van dit gegeven (als losstaande zib) van groot belang, omdat deze ook relevant is buiten de toepassing van vrijheidsbeperkende maatregelen. In de verdere uitwerking van de Basisgegevens GGZ is het element JuridischeStatus losgekoppeld van de verdere zib VrijheidsbeperkendeMaatregelen. Deze loskoppeling wordt tevens als wijzigingsverzoek behandeld bij de nieuwe publicatie zibs: de huidige uitwerking loopt op deze toekomstige ontwikkeling vooruit.

In de MedMij FHIR implementatie gids staat de technische representatie van de betreffende zibs in zogenaamde FHIR profielen. In dit [[MedMij:V2019.01_FHIR_GGZ#List_of_StructureDefinitions|overzicht]] is te zien welk FHIR profiel bij welke zib hoort.

=== Bedrijfsrollen ===
Deze use case onderscheidt twee bedrijfsrollen, namelijk de ''Patiënt'' en de ''Zorgaanbieder'' zoals te zien in onderstaande tabel.

{| class="wikitable" "cellpadding="10" width="100%"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Bedrijfsrol'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil de eigen Basisgegevens GGZ raadplegen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Stelt de Basisgegevens GGZ beschikbaar
|}
'''Bedrijfsrollen Basisgegevens GGZ'''

Onderstaande afbeelding toont de verschillende activiteiten uit de procesbeschrijving die door de bedrijfsrollen worden uitgevoerd.

[[Image:InzienGGZ_activity.png|Activiteitendiagram Raadplegen GGZ]]

'''Activiteitendiagram Raadplegen GGZ'''

=== Procesbeschrijving ===
==== Patient journey - Jelmer Postma ====
De 'patient journey' van [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Jelmer_Postma_MedMij.pdf Jelmer Postma] beschrijft enkele momenten waarop je als patiënt zijnde inzicht kan of zou willen hebben in zijn/haar Basisgegevens GGZ.

<blockquote>In zijn PGO kan Jelmer doorlezen wat de huisarts voorgeschreven heeft en vindt hij de verwijzing voor een psycholoog. Hij zoekt een psycholoog uit en maakt een afspraak waarbij hij de verwijzing bijvoegt.</blockquote>

<blockquote>‘Pling’, Jelmer krijgt van zijn PGO een reminder dat hij morgen om 10.00 zijn eerste afspraak heeft bij de psycholoog. Tevens kan hij vanuit zijn PGO een vragenlijst invullen voor de psycholoog over zijn klachten, gezondheid en verwachtingen. Wat zijn huisarts al vermoedde, wordt door de psycholoog bevestigd.</blockquote>

<blockquote>Gedurende de sessie komen er onverwerkte zaken uit zijn jeugd boven. Deze zijn zo heftig dat Jelmer in een acute depressie belandt. Zijn vriendin Karin geeft aan dat Jelmer op het moment niet thuis kan wonen en samen met de huisarts nemen ze het besluit dat Jelmer voor korte duur opgenomen wordt bij een GGZ-instelling in de buurt. Hier wordt een nieuw behandelplan opgesteld waarin groepstherapie een onderdeel gaat worden. Jelmer heeft Karin gemachtigd om in zijn PGO te kijken zodat ze onder andere het behandelplan in kan zien en ze goed betrokken wordt.</blockquote>

<blockquote>De opname in de GGZ-instelling is van korte duur. Vanaf nu wordt Jelmer ambulant behandeld door een reguliere GGZ-instelling. Gelukkig is deze met 5 minuten fietsen van huis lekker dichtbij. De psychiater van de instelling schrijft een overdracht voor zijn nieuwe hoofdbehandelaar. Zowel Karin als Jelmer kunnen via het PGO inzien wat daarin staat. Daarom weten ze nu dat de medicatie is aangepast.</blockquote>

==== Proces ====
Het stuk van het proces waar het in deze use case om gaat is:
* Het systeem van een zorgaanbieder (XIS) stelt de Basisgegevens GGZ van de patiënt beschikbaar aan het systeem van een patiënt (PGO).

Deze paragraaf vervolgt met een beschrijving van precondities, proces stappen, en post condities.

===== Preconditie =====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van de Basisgegevens GGZ tussen het betreffende XIS en het eigen PGO.

De Basisgegevens GGZ, of een gedeelte van de Basisgegevens GGZ, welke de persoon wil inzien, bestaat en de zorgaanbieder wil deze beschikbaar stellen.
:Soms zijn er valide redenen om de Basisgegevens GGZ, of gedeeltes daarvan, tijdelijk nog niet beschikbaar te stellen aan de patiënt. Bijvoorbeeld omdat de zorgverlener deze eerst zelf wil interpreteren en/of er eerst met de patiënt over wil spreken.
:Een patiënt kan steeds zelf het initiatief nemen om de Basisgegevens GGZ op te halen, maar het is ook mogelijk dat een PGO geconfigureerd is om dit 'automatisch' te doen. Dit maakt voor de scope van deze use case beschrijving geen verschil.

===== Proces stappen =====
* Het systeem van de patiënt (PGO) raadpleegt het systeem van de zorgaanbieder (XIS) voor de Basisgegevens GGZ van de patiënt.
* Het systeem van de zorgaanbieder (XIS) maakt (een deel van) de Basisgegevens GGZ beschikbaar voor de patiënt.
* De patiënt gebruikt de persoonlijke gezondheidsomgeving om de Basisgegevens GGZ in te zien.

===== Post conditie =====
De persoon kan de Basisgegevens GGZ inzien via een persoonlijke gezondheidsomgeving.

=== Systemen & Systeemrollen ===
Zowel de persoon als de zorgaanbieder maken ieder gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om de Basisgegevens GGZ van zorgaanbieder naar de persoon.

{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Systeem
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Naam systeemrol
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Systeemrolcode
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| GGZRaadplegend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|BgGGZ}}-GGR-FHIR
| style="background-color: white;"| Raadplegen Basisgegevens GGZ bij zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| GGZBeschikbaarstellend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|BgGGZ}}-GGB-FHIR
| style="background-color: white;"| Beschikbaarstellen Basisgegevens GGZ aan de patiënt
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:InzienGGZ_componenten.png.PNG|Componenten diagram]]

'''Componenten diagram van systemen en systeemrollen'''

=== Transacties & Transactiegroepen ===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Transactiegroep'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Transactie'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Systeemrolcode'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Systeem'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Bedrijfsrol'''
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:middle;" rowspan="2"|GGZ (PULL)
|style="background-color: white;vertical-align:top;"|[https://decor.nictiz.nl/decor/services/RetrieveTransaction?id=2.16.840.1.113883.2.4.3.11.60.57.4.2&effectiveDate=2019-03-05T17:07:53&language=nl-NL&ui=nl-NL&format=html&hidecolumns=34567 Raadplegen GGZ]
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|BgGGZ}}-GGR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_GGZ |GGZ in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|[https://decor.nictiz.nl/decor/services/RetrieveTransaction?id=2.16.840.1.113883.2.4.3.11.60.57.4.3&effectiveDate=2019-03-05T17:07:53&language=nl-NL&ui=nl-NL&format=html&hidecolumns=34567 Beschikbaarstellen GGZ]
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|BgGGZ}}-GGB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:InzienGGZ_useCase.png|Use case diagram raadplegen Basisgegevens GGZ]]

'''Use case diagram raadplegen Basisgegevens GGZ

=Functionaliteit=
Er zijn geen aanwijzingen/eisen voor functionaliteit van de systemen.

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Auteur(s)
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Titel
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Versie
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Datum
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Bron
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Organisatie
|-
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
| style="background-color: white;"|
|}
'''Referenties

=Bijlage: Documenthistorie=

==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:V2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

{| class="wikitable" "cellpadding="10" style="background-color: white;"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Release
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Versie
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|BITS issue
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black; width:850px;"|Omschrijving

{{ReleaseNotes|package=2019.01 - April|release=1.1.12|issues=3|MM-1025|MM-1003|MM-939}}
{{ReleaseNotes|package=2019.01 - Maart|release=1.1.10|issues=4|MM-997|MM-953|MM-931|MM-657}}
|-
| rowspan = 2 style="background-color: white; | 2019.01 - November
| style="background-color: white; | 1.1.7
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-806 MM-806]
| style="background-color: white;"| Fixed MM-430: adjusted incorrect FHIRPath constraints, moved extension to Consent.extension and moved mappings in extension from extension.value[x].reference to extension.value[x] in zib TreatmentDirective profile.
|-
| style="background-color: white; | 1.1.6
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-430 MM-430]
| style="background-color: white;"| The TreatmentDirective profile allowed at most 1 reference to an AdvanceDirective resource, because of restrictions in the FHIR base. There is now an extension inside the source element to allow referencing additional AdvanceDirective resources.
|-
| style="background-color: white; | 2019.01 - Oktober
| style="background-color: white; | 1.1.5
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-594 MM-594]
| style="background-color: white;"| Updated date time example in profile to include timezone as required by the FHIR specification.
|-
| rowspan = 4 style="background-color: white;"| 2019.01 - September
| rowspan = 4 style="background-color: white;"| 1.1.4
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-358 MM-358]
| style="background-color: white;"| Tekstcorrectie op de kwalificatie pagina ToelichtingKwalificatieGGZ.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-336 MM-336]
| style="background-color: white;"| Aanpassen ConceptMap InterpretatieVlaggenCodelijst-to-observation-interpretation
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-327 MM-327]
| style="background-color: white;"|
Fixed reference to generalPractitioner in examples nl-core-patient-languageProficiency - example.xml and nl-core-patient-legalStatus - example.xml.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-322 MM-322]
| style="background-color: white;"| Aanpassen conceptnaam ResultaatVlaggen naar InterpretatieVlaggen in FHIR profiel voor LaboratoryResults.
|-
| rowspan = 10; style="background-color: white;"| 2019.01
|-
| rowspan = 3; style="background-color: white;"| 1.1.3
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-346 MM-346]
| style="background-color: white;"| Ongeldig discriminator pad in code slicing in zib Verrichting
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-294 MM-294]
| style="background-color: white;"| Naam mapping binnen div. FHIR profielen aangepast conform zib: HCIM LaboratoryTestResult-v4.1(2017EN).
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-252 MM-252]
| style="background-color: white;"| FreedomRestrictingMeasures incorrecte terminologie in profiel en technisch ontwerp pagina
|-
| style="background-color: white;"| 1.1.1
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-206 MM-206]
| style="background-color: white;"| Reference vanuit Observation naar Specimen Isolate onjuist.
|-
| rowspan = 5; style="background-color: white;"| 1.1.0
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-143 MM-143]
| style="background-color: white;"| Aanpassing modellering Procedure.performer in het profiel voor HCIM Verrichting.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-118 MM-118]
| style="background-color: white;"| Profiel naam zib-Product niet passend bij zib FarmaceutischProduct.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-100 MM-100]
| style="background-color: white;"| Mapping CBV naar SNOMED codes.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-99 MM-99]
| style="background-color: white;"| Interval heeft Period maar geen PeriodUnit op simplifier.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-50 MM-50]
| style="background-color: white;"| Contact ondersteunt geen klinische contacten.
|-
| rowspan = 4; style="background-color: white;"| 2018.06
| rowspan = 4; style="background-color: white;"| 1.0.0
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-128 MM-128]
| style="background-color: white;"| CanceledIndicator possible values.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-66 MM-66]
| style="background-color: white;"| Update mappings LaboratoriumUitslag in DiagnosticReport en Observation.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-55 MM-55]
| style="background-color: white;"| Profile for HCIM TobaccoUse was missing a specification for PackYears unit - profile updated to 2.0.1.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-54 MM-54]
| style="background-color: white;"| Wrong SNOMED code in search URL for FunctionalOrMentalStatus in BgZ and GGZ.
|}

==Paginahistorie==
{| class="wikitable" "cellpadding="10"
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Release
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Datum
!style="background-color: #4AB8A7;; color: white; font-weight: bold; text-align:left; border: 1px solid black;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor april 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Maart 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Wijzigingen voor maart 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Februari 2020
| style="background-color: white; | 27-02-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Januari 2020
| style="background-color: white; | 27-01-2020
| style="background-color: white;"|
* Wijzigingen voor januari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 10-12-2019
| style="background-color: white;"|
* Wijzigingen voor november patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 28-11-2019
| style="background-color: white;"|
* Wijzigingen voor november patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Oktober
| style="background-color: white; | 30-10-2019
| style="background-color: white;"|
* Wijzigingen voor oktober patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 27-06-2019
| style="background-color: white;"|
* Toevoeging release notes voor patches. Ophogen versie nummers naar 1.1.3.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-04-2019
| style="background-color: white;"|
* Toelichting over de verschillende modules van het VIPP GGZ programma, waarvan de Basisgegevens GGZ 1 module beslaat.
* Toevoeging transactie specificaties op ART-DECOR.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 28-03-2019
| style="background-color: white;"|
* Plaatsen release notes behorende bij patch 1.
* Versienummer systeemrol codes ophogen met 1 patch nummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"|
*Wijzigingen gepubliceerd in versie 2019.01, zie release notes.
*Verplaatsing release notes naar functionele pagina.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 01-11-2018
| style="background-color: white;"|
* Toevoeging verwijzing naar gepubliceerde VIPP GGZ regeling en uitgangspunten voor kwalificatie.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 15-10-2018
| style="background-color: white;"|
* Aanpassing versienummer in titel.
* Toevoeging documenthistorie.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 26-09-2018
| style="background-color: white;"|
* Toevoeging toelichting over de inhoud m.b.t. overlap en verschillen met de Basisgegevensset Zorg (BgZ).
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 10-09-2018
| style="background-color: white;"|
* Eerste conceptversie.
|}

MedMij:V2019.01 OntwerpHuisartsgegevens

2020-05-01T07:31:43Z

Stephan Opdenberg: versie package verhoogd

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp Huisartsgegevens {{VersieInfo|V2019.01|Huisartsgegevens}}}}
{{MedMij:V2019.01_Issuebox}}

[[Bestand:Huisartsgegevens.png|link=|links|Huisartsgegevens|85px]]
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR GP Data|Technisch]]
desc none
</imagemap>

=Inleiding=
==Algemeen==
De basis voor de inhoud van dit ontwerp is de "[[#richtlijn-huisarts-patient|Richtlijn online inzage in het H-EPD door patiënt]]". Op basis van deze richtlijn wordt de patiënt in staat gesteld gegevens van zijn huisartsdossier online op te vragen.

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de MedMij functionele ontwerpen, die [[MedMij:V2019.01_Ontwerpen#Doelgroep| hier]] gevonden kan worden.

==Kaders en uitgangspunten==
===Richtlijn===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Richtlijn| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

=Use Cases=
==Use case: Raadplegen Huisartsgegevens door patiënt==
===Doel en relevantie===
Online inzage door de patiënt in het elektronisch patiëntendossier bij de huisarts (H-EPD) heeft als doel om de zorg beter te maken. De patiënt krijgt door online inzage meer overzicht en is beter geïnformeerd. Hierdoor heeft de patiënt meer begrip van en regie over de eigen gezondheid en het stimuleert zelfzorg. Ook kan het de kwaliteit van het dossier helpen verhogen.

===Domein===
Huisartsgegevens in het domein van zorgaanbieders en patiënten.

===Context===
Het gaat om het elektronisch en gestructureerd beschikbaar maken van een huisartsgegevens vanuit een zorgaanbiederssysteem (XIS) naar een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO).
Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.
De beschrijving is infrastructuur-onafhankelijk.

===Informatie===
De gegevens zoals deze door de huisarts worden aangeboden voor online inzage aan de patiënt bestaan uit 10 secties (zie bijlage 1 van de richtlijn). Een aantal daarvan overlappen met de [[MedMij:V2019.01 OntwerpBGZ_2017|Basisgegevensset Zorg]] (BgZ) en een aantal daarvan zijn uniek voor het huisartsdossier. De richtlijn baseert zich op het [[#his-referentiemodel-2016|HIS referentiemodel]]. Die richtlijn heeft geen relatie met de [http://www.zibs.nl Zorginformatiebouwstenen] (zibs). Voor een aantal secties is deze relatie wel te leggen en voor een aantal ook niet (goed). De discrepanties zullen in de toekomst, in het Nictiz/NHG project "Huisartsoverdrachten", nog verder onderzocht en geslecht worden. Dit ontwerp Huisartsgegevens loopt daarop vooruit, omdat alle FHIR-profielen zich baseren op de zibs. Dit ontwerp en de technische uitwerking zal worden bijgewerkt, zodra de geharmoniseerde zorginformatiebouwstenen beschikbaar zijn. Dit zal naar verwachting niet vóór 2019 plaatsvinden.

In de MedMij FHIR implementatiegids staat de technische representatie van de betreffende zibs in zogenaamde FHIR profielen. In onderstaand overzicht is te zien welk FHIR profiel bij welke zib hoort.

{| class="wikitable collapsible collapsed" cellpadding="10" width="80%"
! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:center; border: 1px solid black;" colspan="4" | Bijlage 1 Richtlijn Online inzage in het H-EPD door patiënt
! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:center; border: 1px solid black;" colspan="2" | (Voorlopige) mapping naar zibs
|-
! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"| #
! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"| Onderdelen uit het Huisarts‑EPD
! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"| Beschrijving
! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"| Uitleg met voorbeelden
! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"| Zorginformatiebouwsteen
! style="background-color: #4AB8A7; color: white; font-weight: bold; text-align:left; background-color: #E3E3E3 width:10px"| Opmerking
|-
| style="background-color: white;vertical-align:top;"| 1
| style="background-color: white;vertical-align:top;"|Huisarts/Huisartsenpraktijk
| style="background-color: white;vertical-align:top;"|De huisarts en/of de huisartsenpraktijk waar de gegevens van afkomstig zijn.
| style="background-color: white;vertical-align:top;"|
| style="background-color: white;vertical-align:top;"| [https://zibs.nl/wiki/Zorgverlener-v3.1(2017NL) Zorgverlener v3.1 (2017)] [https://zibs.nl/wiki/Zorgaanbieder-v3.1(2017NL) Zorgaanbieder v3.1 (2017)]
| style="background-color: white;vertical-align:top;"|
|-
| style="vertical-align:top;"| 2
| style="vertical-align:top;"|Patiënt
| style="vertical-align:top;"|De patiëntgegevens van de patiënt waarvoor de gegevens zijn.
| style="vertical-align:top;"|
| style="vertical-align:top;"| [https://zibs.nl/wiki/Patient-v3.1(2017NL) Patient v3.1 (2017)]
| style="vertical-align:top;"|
|-
| style="background-color: white;vertical-align:top;"| 3
| style="background-color: white;vertical-align:top;"|Episodes
| style="background-color: white;vertical-align:top;"|Een gezondheidsprobleem zoals een klacht of een aandoening, waarvan de aard in de loop der tijd kan veranderen door voortschrijdend inzicht of door het beloop van de aandoening.
| style="background-color: white;vertical-align:top;"|Ziekten, aandoeningen, klachten en symptomen. Bijvoorbeeld: blaasontsteking of droge hoest.
| style="background-color: white;" rowspan="3"| [https://zibs.nl/wiki/OverdrachtConcern-v1.2(2015NL) OverdrachtConcern v1.2 (2015)] [https://zibs.nl/wiki/Alert-v3.1(2017EN) Alert v3.1 (2017)]
| style="background-color: white;" rowspan="3"| Na 2015 is nog een versie 3.0 in 2016 uitgebracht die alleen in versie, niet in inhoud veranderd is. De versie van 2017 echter heeft expliciet gebruik voor episodes geschrapt.
|-
| style="vertical-align:top;"| 4
| style="vertical-align:top;"|Episodes met een attentievlag
| style="vertical-align:top;"|Episodes kunnen een attentievlag hebben om extra aandacht voor de episode te vragen. De attentievlag kan aanwezig blijven als een episode afgesloten wordt/is, wanneer de gebruiker het belangrijk vindt dit probleem in beeld te houden.
| style="vertical-align:top;"|Belangrijke ziekten, aandoeningen, klachten en symptomen. Bijvoorbeeld: reuma, suikerziekte, kanker, erfelijke ziekten.
|-
| style="background-color: white;vertical-align:top;"| 5
| style="background-color: white;vertical-align:top;"|Open en gesloten episodes
| style="background-color: white;vertical-align:top;"|Episodes kunnen open (actueel) of gesloten (niet langer actueel) zijn.
| style="background-color: white;vertical-align:top;"|Open/actueel: ziekten, aandoeningen, klachten en symptomen waarvoor nog zorg wordt verleend. Gesloten/niet actueel: ziekten, aandoeningen, klachten en symptomen waarvoor in het verleden zorg is verleend.
|-
| style="vertical-align:top;"| 6
| style="vertical-align:top;"|Behandeling
| style="vertical-align:top;"|Handeling aan de patiënt, die invloed heeft op de gezondheidstoestand van de patiënt.
| style="vertical-align:top;"|Operaties en (zware) behandelingen zoals bestraling of chemotherapie.
| style="vertical-align:top;"| ''[https://zibs.nl/wiki/Verrichting-v4.0(2017NL) Verrichting v4.0 (2017)]''
| style="vertical-align:top;"| zib ondersteunt alleen de DHD Verrichtingenthesaurus waarmee het huisartssysteem niet werkt.
|-
| style="background-color: white;vertical-align:top;"| 7
| style="background-color: white;vertical-align:top;"| Profylaxe en voorzorg
| style="background-color: white;vertical-align:top;"| In Profylaxe en voorzorg worden voorzorgsmaatregelen vastgelegd die nodig zijn bij of vanwege bepaalde medische aandoeningen.
| style="background-color: white;vertical-align:top;"| Bijvoorbeeld voorzorgen bij ooit doorgemaakte endocarditis (ontsteking van de binnenbekleding van het hart en de hartkleppen) of na een miltverwijdering.
| style="background-color: white;vertical-align:top;"|
| style="background-color: white;vertical-align:top;"| Er is in principe slechts een type uit NHG tabel 56
|-
| style="vertical-align:top;"| 8
| style="vertical-align:top;"| Actuele medicatie
| style="vertical-align:top;"| Medicatie-afspraak Het voorstel van een voorschrijver tot gebruik van medicatie waarmee de patiënt akkoord is. De afspraak kan zowel starten, herhalen, wijzigen als stoppen van medicatie betreffen.
| style="vertical-align:top;"| '''De actuele medicatie''' is het overzicht van de medicatieafspraken. Het is de lijst van geneesmiddelen die de patiënt nu gebruikt.
| style="vertical-align:top;"| [https://zibs.nl/wiki/Medicatieafspraak-v1.0(2017NL) Medicatieafspraak v1.0 (2017)]
| style="vertical-align:top;"|
|-
| style="background-color: white;vertical-align:top;"| 9
| style="background-color: white;vertical-align:top;"| Medicatie-overgevoeligheid
| style="background-color: white;vertical-align:top;"| Een medicatie-overgevoeligheid beschrijft een overgevoeligheid van een patiënt voor een geneesmiddel, een stof of een geneesmiddelengroep, waarmee rekening gehouden moet worden bij het voorschrijven van medicatie.
| style="background-color: white;vertical-align:top;"| Lijst van geneesmiddelen waarop in het verleden een overgevoeligheid of levensbedreigende allergische reactie is opgetreden. Bijvoorbeeld: allergie voor aspirine.
| style="background-color: white;vertical-align:top;"| [https://zibs.nl/wiki/AllergieIntolerantie-v3.1(2017NL) AllergieIntolerantie v3.1 (2017)]
| style="background-color: white;vertical-align:top;"|
|-
| style="vertical-align:top;"| 10
| style="vertical-align:top;"|Correspondentie
| style="vertical-align:top;"|Inkomend: Een binnengekomen brief betreffende een patiënt, die als zodanig is vastgelegd in het medisch dossier van de patiënt. Uitgaand: Een brief die opgesteld is door een praktijkmedewerker en naar een externe zorgverlener verstuurd is.
| style="vertical-align:top;"|Inkomende = brieven uit het ziekenhuis, polikliniek, zorginstelling. Uitgaande = verwijsbrieven.
| style="vertical-align:top;"| ''[https://zibs.nl/wiki/TekstUitslag-v4.0(2017NL) TekstUitslag v4.0 (2017)]''
| style="vertical-align:top;"| Correspondentie kan een binair bestand zijn zoals PDF/A, typen in de zib zijn niet toereikend voor alle typen correspondentie
|-
| style="background-color: white;vertical-align:top;"| 11
| style="background-color: white;vertical-align:top;"|Resultaten van bepalingen – ''laatste veertien maanden''
| style="background-color: white;vertical-align:top;"|Een bepaling is een objectiveerbare diagnostische verrichting. Het resultaat is de (uitkomst) van een bepaling.
| style="background-color: white;vertical-align:top;"|Uitslagen van fysieke metingen, zoals bloeddruk, gewicht en laboratoriumtesten, zoals ijzergehalte in het bloed.
| style="background-color: white;vertical-align:top;"|[https://zibs.nl/wiki/LaboratoriumUitslag-v4.0(2017NL) LaboratoriumUitslag v4.0 (2017)] 
[https://zibs.nl/wiki/Bloeddruk-v3.1(2017NL) Bloeddruk v3.1 (2017)] 
[https://zibs.nl/wiki/Lichaamsgewicht-v3.1(2017NL) Lichaamsgewicht v3.1 (2017)] 
[https://zibs.nl/wiki/Lichaamslengte-v3.1(2017NL) Lichaamslengte v3.1 (2017)] 
[https://zibs.nl/wiki/Lichaamstemperatuur-v3.1(2017NL) Lichaamstemperatuur v3.1 (2017)] 
[https://zibs.nl/wiki/AlgemeneMeting-v3.0(2017NL) AlgemeneMeting v3.0 (2017)] 
[https://zibs.nl/wiki/Hartfrequentie-v3.1(2017NL) Hartfrequentie v3.1 (2017)] 
[https://zibs.nl/wiki/O2Saturatie-v3.1(2017NL) O2Saturatie v3.1(2017)] 
[https://zibs.nl/wiki/Polsfrequentie-v3.1(2017NL) Polsfrequentie v3.1(2017)]
| style="background-color: white;vertical-align:top;"|
|-
| style="vertical-align:top;"| 12
| style="vertical-align:top;"|E- en P-regels van de SOEP- structuur - ''vastgelegd na invoering van online inzage''
| style="vertical-align:top;"|Informatie uit een deelcontact dat in vrije tekst wordt geregistreerd volgens de SOEP-structuur. Het acroniem SOEP staat voor Subjectief, Objectief, Evaluatie en Plan.
| style="vertical-align:top;"|In de E(valuatie)-regel staat de conclusie van het consult. In de P(lan)-regel staan de afgesproken zaken en eventuele vervolgstappen.
| style="vertical-align:top;"| ''[https://zibs.nl/wiki/TekstUitslag-v4.0(2017NL) TekstUitslag v4.0 (2017)]''
| style="vertical-align:top;"| Journaalregeltype en ICPC-codering, extra t.o.v. in zib
|}

====Raadplegen huisartsgegevens ====
De vraag wordt gesteld aan de huisarts of huisartsenpraktijk. Er zijn geen verdere parameters bekend. Zie de [[#richtlijn-huisarts-patient|richtlijn]] voor de verdere context van de vraag naar de huisartsgegevens.

Dit betreft de filtermogelijkheden (parameters) in de vraag om huisartsgegevens.

====Beschikbaar stellen huisartsgegevens====
Zie voor de Informatie-elementen in huisartsgegevens de [[#richtlijn-huisarts-patient|richtlijn]].

Dit betreft de inhoud van de transactie met huisartsgegevens.

=== Bedrijfsrollen ===
Deze use case kent twee bedrijfsrollen.

{| class="wikitable" cellpadding="10" width="50%
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil huisartsgegevens raadplegen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Stelt huisartsgegevens beschikbaar
|}
'''Bedrijfsrollen huisartsgegevens'''

Onderstaande afbeelding toont de bedrijfsrollen en de activiteiten die zij uitvoeren.

[[Bestand:Activity_Diagram_-_Huisartspatientsamenvatting.jpg|Activiteitendiagram Raadplegen huisartsgegevens]]

'''Activiteitendiagram Raadplegen huisartsgegevens'''

===Procesbeschrijving===
===='Patient journey' - Roos Dalstra ====
Het verhaal van de 'patient journey' van Roos Dalstra vindt u in de [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Roos_Dalstra_MedMij.pdf casus Roos Dalstra].

Hieronder een voor Roos relevante situatie waarbij het raadplegen van de huisartsgegevens een rol speelt.

<blockquote></blockquote>

====Proces====
Het stuk van het proces waar het in deze use case om gaat is:
*Het systeem van een zorgaanbieder (XIS) stelt huisartsgegevens beschikbaar aan het systeem van een patiënt (PGO).
Deze paragraaf vervolgt met een beschrijving van precondities, processtappen, en postcondities.
=====Preconditie=====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van huisartsgegevens tussen het betreffende XIS en de eigen persoonlijke gezondheidsomgeving.

De patiënt wil de huisartsgegevens inzien en de zorgaanbieder stelt deze ook beschikbaar.
Een patiënt kan steeds zelf het initiatief nemen om een huisartsgegevens op te halen, maar het is ook mogelijk dat een PGO geconfigureerd is om dit 'automatisch' te doen. Dit maakt voor de beschrijving van deze use case geen verschil.

=====Processtappen=====
*Het systeem van de patiënt (PGO) vraagt om de beschikbare huisartsgegevens bij een XIS.
*Het systeem van de zorgaanbieder (XIS) levert de huisartsgegevens op voor de patiënt.
*Patiënt gebruikt de persoonlijke gezondheidsomgeving om de huisartsgegevens in te zien.

=====Postconditie=====
De patiënt kan de huisartsgegevens inzien via de persoonlijke gezondheidsomgeving.

=== Systemen & Systeemrollen ===
Zowel zorgaanbieder als patiënt maken gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om de huisartsgegevens van zorgaanbieder naar de patiënt.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| HuisartsgegevensRaadplegend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Huisartsgegevens}}-HGR-FHIR
| style="background-color: white;"| Raadplegen huisartsgegevens bij zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| HuisartsgegevensBeschikbaarstellend
| style="background-color: white;"| MM-{{VersieInfo|V2019.01|Huisartsgegevens}}-HGB-FHIR
| style="background-color: white;"| Beschikbaarstellen huisartsgegevens aan de patiënt
|-
|}
Zie ook onderstaande afbeelding.

[[Bestand:Component_Diagram_-_Huisartspatientsamenvatting_(Totaal).jpg|Componentendiagram]]

'''Componentendiagram'''

De kwalificatie van informatiesystemen vindt plaats op basis van systeemrollen.

=== Transacties, Transactiegroepen en systeemrollen===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Link naar technische specificatie'''
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|Huisartsgegevens (PULL)
|style="background-color: white;vertical-align:top;"|Raadplegen huisartsgegevens
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Huisartsgegevens}}-HGR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR GP Data|Huisartsgegevens in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen huisartsgegevens
|style="background-color: white;vertical-align:top;"|MM-{{VersieInfo|V2019.01|Huisartsgegevens}}-HGB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:Use_Case_Diagram_-_Huisartspatientsamenvatting.jpg|Use case diagram raadplegen Huisartsgegevens]]

'''Use case diagram

=Functionaliteit=
Er zijn geen aanwijzingen/eisen voor functionaliteit van de systemen.

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="text-align:left;"|Auteur(s)
!style="text-align:left;"|Titel
!style="text-align:left;"|Versie
!style="text-align:left;"|Datum
!style="text-align:left;"|Bron
!style="text-align:left;"|Organisatie
|-
| style="background-color: white;"| -
| style="background-color: white;"| Richtlijn Online inzage in het H-EPD door patiënt
| style="background-color: white;"|
| style="background-color: white;"| 2017
| style="background-color: white;"| https://www.nhg.org/themas/publicaties/richtlijn-online-inzage-het-h-epd-door-patient of de [https://www.nhg.org/sites/default/files/content/nhg_org/images/richtlijn_online_inzage_in_het_h-epd_door_patient_web_2017.pdf directe link (PDF)]
| style="background-color: white;"| NHG / Patiëntenfederatie
|-
| style="background-color: white;"| -
| style="background-color: white;"| HIS referentiemodel Publieksversie (Utrecht 2016)
| style="background-color: white;"|
| style="background-color: white;"| 2016
| style="background-color: white;"| https://referentiemodel.nhg.org/inhoud/themas/publieksversie/published
| style="background-color: white;"| NHG
|}

=Bijlage: Documenthistorie=

==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:V2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

{| class="wikitable" "cellpadding="10" style="background-color: white;"
!style="text-align:left;"|Release
!style="text-align:left;"|Versie
!style="text-align:left;"|BITS issue
!style="width:850px; text-align:left;"|Omschrijving
{{ReleaseNotes|release=1.1.11|package=2019.01 - Maart 2020|packageIssues=2|issues=2|MM-940|MM-926}}
|-
| rowspan = 2; style="background-color: white; | 2019.01 - Januari 2020
| rowspan = 2; style="background-color: white; | 1.1.9
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-492 MM-492]
| style="background-color: white;"| Added comment to AllergyIntolerance.comment in the HCIM Allergyintolerance FHIR profile to explain the mapping for ValueSet AllergieStatusCodelijst to AllergyIntolerance.clinicalStatus and AllergyIntolerance.verificationStatus. Added dataAbsentReason extension to AllergyIntolerance.verificationStatus.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-467 MM-467]
| style="background-color: white;"| Added comment on MedicationRequest.reasonCode in HCIM MedicationAgreement profile to to explain mising HCIM mapping.
|-
| rowspan = 2; style="background-color: white;"| 2019.01 - November
| rowspan = 2; style="background-color: white;"| 1.1.8
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-655 MM-655]
| style="background-color: white;"| Cardinality of Observation.subject in the gp-journalEntry profile has been changed from 0..1 to 1..1. In addition, this profile is now based on the nl-core-observation profile to ensure consistency.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-618 MM-618]
| style="background-color: white;"| Changed faulty 'include:' to 'include=' in Search URL on TO for GP Data #8.
|-
| rowspan = 3; style="background-color: white;"| 2019.01 - Oktober
| rowspan = 3; style="background-color: white;"| 1.1.7
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-601 MM-601]
| style="background-color: white;"| Search parameters op codesysteem moeten eindigen op <nowiki>|</nowiki>.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-530 MM-530]
| style="background-color: white;"| Duiding toegevoegd bij het opvragen van contactverslagen ten aanzien van de samenstelregels voor Composition resources
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-528 MM-528]
| style="background-color: white;"| Parameter periodofuse is a required parameter for MedicationAgreements. Removed ''This may or may not be populated. If it is not, the Medicationagreement is assumed to be current.''
|-
| rowspan = 2; style="background-color: white; | 2019.01 - September
| rowspan = 2; style="background-color: white; | 1.1.6
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-436 MM-436]
| style="background-color: white;"| Aanpassen ConceptMap InterpretatieVlaggenCodelijst-to-observation-interpretation.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-422 MM-422]
| style="background-color: white;"| Aanpassen conceptnaam ResultaatVlaggen naar InterpretatieVlaggen in FHIR profiel voor LaboratoryResults.
|-
| rowspan = 11; style="background-color: white;"| 2019.01
| rowspan = 5; style="background-color: white;"| 1.1.5
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-308 MM-308]
| style="background-color: white;"| List of StructureDefinitions has been updated to reflect profiles that are currently implementable. As not the whole guideline is implementable at this point in time as reflected in the List of Invocations, this makes the List of StructureDefinitions smaller than it was. The Corresponce section is thus no longer present and this solves the dead link.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-307 MM-307]
| style="background-color: white;"| Aanpassen mapping van "Reden wijzigen of staken" en "Reden wijzigen of stoppen gebruik" van HCIM naar MP9.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-258 MM-258]
| style="background-color: white;"| HCIM PharmaceuticalProduct: Added ValueSet 'IngredientCodeGTINCodeLijst' + correct reference url to ValueSet.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-255 MM-255]
| style="background-color: white;"| Extensies DateLastEncounter, DateFirstEncounter en EpisodeOfCareTitle toegevoegd aan nl-core-episodeofcare profiel.
|-
| style="background-color: white;"| 1.1.4
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-269 MM-269]
| style="background-color: white;"| Huisartsgegevens: Discrepantie Technisch ontwerp en Kwalificatie
|-
| style="background-color: white;"| 1.1.3
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-251 MM-251]
| style="background-color: white;"| Fout in voorbeeld sectie Treatment van Huisartsgegevens
|-
| style="background-color: white;"| 1.1.1
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-206 MM-206]
| style="background-color: white;"| Reference vanuit Observation naar Specimen Isolate onjuist.
|-
| rowspan = 3; style="background-color: white;"| 1.1.0
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-144 MM-144]
| style="background-color: white;"| Problem zib ClinicalStatus can take on values which are not defined by the HCIM.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-118 MM-118]
| style="background-color: white;"| Profiel naam zib-Product niet passend bij zib FarmaceutischProduct.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-100 MM-100]
| style="background-color: white;"| Mapping CBV naar SNOMED codes.
|-
| rowspan = 3; style="background-color: white;"| 2018.06
| rowspan = 3; style="background-color: white;"| 1.0.0
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-66 MM-66]
| style="background-color: white;"| Update mappings LaboratoriumUitslag in DiagnosticReport en Observation.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/projects/MM/issues/MM-64 MM-64]
| style="background-color: white;"| Koppelen van meetinstrument aan relevante profielen.
|-
| style="background-color: white;"| [https://bits.nictiz.nl/projects/MM/issues/MM-51 MM-51]
| style="background-color: white;"| Extend query for AllergyIntolerance with parameter <code>code</code>. This parameter allows querying specifically medication intolerances.
|}

==Paginahistorie==
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Datum
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor april 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Maart 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Wijzigingen voor maart 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Februari 2020
| style="background-color: white; | 27-02-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Januari 2020
| style="background-color: white; | 27-01-2020
| style="background-color: white;"|
* Wijzigingen voor januari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 10-12-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 28-11-2019
| style="background-color: white;"|
* Wijzigingen voor november patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Oktober
| style="background-color: white;"| 30-10-2019
| style="background-color: white;"|
* Wijzigingen voor oktober patch release.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 15-07-2019
| style="background-color: white;"|
* Cosmetische correctie: structuur Inleiding rechtgetrokken.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 27-06-2019
| style="background-color: white;"|
* Toevoeging van release notes voor patches. Ophogen versienummer naar 1.1.5.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 28-03-2019
| style="background-color: white;"|
* Plaatsen release notes behorende bij patch 1.
* Versienummer systeemrol codes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"|
*Wijzigingen gepubliceerd in versie 2019.01, zie release notes.
*Verplaatsing release notes naar functionele pagina.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 15-10-2018
| style="background-color: white;"|
* Aanpassing versienummer in titel.
* Toevoeging documenthistorie.
|}

MedMij:Vprepub-2019.01 OntwerpHuisartsgegevens

2020-05-01T07:31:43Z

Stephan Opdenberg: versie package verhoogd

MedMij:V2019.01 OntwerpeAfspraak

2020-05-01T07:30:38Z

Stephan Opdenberg: versie package verhoogd

__NUMBEREDHEADINGS__
{{#customtitle:Functioneel Ontwerp eAfspraak {{VersieInfo|V2019.01|eAfspraak}}}}
{{MedMij:V2019.01_Issuebox}}

[[Bestand:EAfspraak_icoon_zonder_tekst.png |link=|links |87px|eAfspraak]]
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
<imagemap>Bestand:Leeswijzer-technisch-banner 02 white.png|center|400px|alt=Afspraken-Functioneel-Technisch
circle 241 216 211 [https://www.medmij.nl/afsprakenstelsel Afsprakenstelsel]
circle 1013 224 212 [[MedMij:V2019.01_Ontwerpen|Functioneel]]
circle 1787 230 212 [[MedMij:V2019.01_FHIR_eAfspraak|Tecnical]]
desc none
</imagemap>

=Inleiding=

==Algemeen==
Deze pagina beschrijft use cases waarbij een patiënt afspraken kan raadplegen, maken, annuleren of wijzigen met behulp van een persoonlijke gezondheidsomgeving. Algemene informatie betreffende deze use cases kan gevonden worden op deze [https://informatiestandaarden.nictiz.nl/wiki/MedMij:V2019.01_Ontwerpen wiki pagina].

==Doelgroep==
De doelgroep voor deze pagina wijkt niet af van de algemene doelgroep van de MedMij functionele ontwerpen, die [[MedMij:V2019.01_Ontwerpen#Doelgroep| hier]] gevonden kan worden.

==Kaders en uitgangspunten==
===Richtlijn===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Richtlijn| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Infrastructuur===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Infrastructuur| de algemene inleiding]] van de MedMij functionele ontwerpen.

===Geografische reikwijdte===
Geen nadere specificatie, anders dan genoemd in [[MedMij:V2019.01_Ontwerpen#Geografische_reikwijdte| de algemene inleiding]] van de MedMij functionele ontwerpen.

==Kwalificatie==
===Introductie===
{{#lst:MedMij:V2019.01_Kwalificatie|medmij_kwalificatie_introductie}}

=Use Cases=
Deze sectie vervolgt met de volgende use cases:
*[[#Use_case:_Afspraak_raadplegen_door_pati.C3.ABnt|Afspraak raadplegen]]
*[[#Use_case:_Afspraak_maken_door_pati.C3.ABnt|Afspraak maken]] [*]
*[[#Use_case:_Afspraak_annuleren_door_pati.C3.ABnt|Afspraak annuleren]] [*]
*[[#Use_case:_Afspraak_wijzigen_door_pati.C3.ABnt|Afspraak wijzigen]] [*]

[*] Indien u voornemens bent dit deel van de standaard (Afspraak maken, annuleren en wijzigen) te gaan inbouwen, vragen wij u om eerst contact op te nemen met MedMij standaarden via mailadres standaarden@medmij.nl

Buiten scope van deze use cases vallen:
*Abonnementsservice
*Notificaties

==Use case: Afspraak raadplegen door patiënt==
===Doel en relevantie===
Inzicht in afspraken biedt patiënten overzicht en gebruiksgemak. Dit draagt bij aan meer grip op de eigen gezondheidsgegevens en daarmee ook meer regie over de eigen gezondheid.

===Domein===
Afspraken met zorggebruikers (patiënten / cliënten) in het domein van de zorg.

===Context===
Het gaat om het elektronisch en gestructureerd beschikbaar maken van afspraken vanuit een zorgaanbiederssysteem (XIS) naar een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO).
Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.
De beschrijving is infrastructuur-onafhankelijk.

===Informatie===

====Raadplegen afspraak ====
Het raadplegen van een afspraak gaat van een specifieke patiënt naar een specifieke organisatie in de zorg (bijvoorbeeld een zorgaanbieder).

Verdere informatie-elementen in de vraag om afspraken zijn:
*periode (startdatum - einddatum) waarin de afspraak plaats heeft gehad / heeft / zal hebben
Dit betreft dus de filtermogelijkheden (query parameters) in de vraag om afspraken.

====Beschikbaarstellen afspraak ====
De informatie-elementen voor beschikbaarstellen afspraak staan in [https://decor.nictiz.nl/art-decor/decor-scenarios--eafspraken-?id=2.16.840.1.113883.2.4.3.11.60.61.4.3&effectiveDate=2017-10-10T14%3A19%3A43&datasetId=2.16.840.1.113883.2.4.3.11.60.61.1.1&datasetEffectiveDate=2017-08-01T14%3A56%3A38&conceptId=2.16.840.1.113883.2.4.3.11.60.61.2.1&conceptEffectiveDate=2017-08-01T14%3A56%3A38&language=nl-NL&scenariotree=true ART-DECOR eAfspraak]

=== Bedrijfsrollen ===
Deze use case kent twee bedrijfsrollen.

{| class="wikitable" "cellpadding="10" width="50%"
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Wil afspraken raadplegen
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Stelt afspraken beschikbaar
|}
'''Bedrijfsrollen afspraak inzien'''

Onderstaande afbeelding toont de bedrijfsrollen en de activiteiten die zij uitvoeren.

[[Bestand:Activity Diagram - Afspraak raadplegen-v2.png|Activiteitendiagram afspraak raadplegen]]

'''Activiteitendiagram afspraak raadplegen'''

===Procesbeschrijving===
===='Patient journey' - Thomas van Beek ====
Het verhaal van de 'patient journey' van Thomas vindt u [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Thomas_van_Beek_MedMij.pdf hier].

Hieronder een aantal voor Thomas relevante situaties waarbij het raadplegen van afspraken een rol speelt.

<blockquote>Thomas heeft iedere drie maanden een controle in het ziekenhuis in verband met zijn Diabetes aandoening. De eerstkomende afspraak is op vrijdag 6 oktober 2017 om 10:30u met internist Janssen bij het Antonius Ziekenhuis in Rotterdam en duurt een uur. Het ziekenhuisinformatiesysteem heeft deze afspraak beschikbaar gemaakt voor de persoonlijke gezondheidsomgeving van Thomas. Thomas kan deze afspraak dan ook inzien via zijn persoonlijke gezondheidsomgeving.
----
Op 6 september belt de afdelingssecretaresse van het ziekenhuis. Zij heeft het verzoek aan Thomas of de afspraak verzet kan worden naar dinsdag 3 oktober om 16:00 uur. Dat komt hem prima uit, dus hij gaat akkoord. Het ziekenhuisinformatiesysteem maakt deze nieuwe afspraakinformatie beschikbaar voor de persoonlijke gezondheidsomgeving. Wanneer Thomas later die dag kijkt, ziet hij ook de bijgewerkte afspraakinformatie in zijn persoonlijke gezondheidsomgeving. Wel zo makkelijk, want hij was het eerder die dag vergeten op te schrijven.
</blockquote>

====Proces====
Het stuk van het proces waar het in deze use case om gaat is:
*Het systeem van een zorgaanbieder (XIS) stelt de afspraak beschikbaar aan het systeem van een patiënt (PGO).
Deze paragraaf vervolgt met een beschrijving van precondities, proces stappen, en post condities.
=====Preconditie=====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van afspraken tussen het betreffende XIS en de eigen persoonlijke gezondheidsomgeving.

De patiënt wil afspraken inzien en de zorgaanbieder stelt dit ook beschikbaar.
Een patiënt neemt steeds zelf het initiatief om zijn afspraken te raadplegen.

=====Proces stappen=====
*Het systeem van de patiënt (PGO) vraagt om beschikbare afspraken bij een XIS.
*Het systeem van de zorgaanbieder (XIS) levert de afspraken op voor de patiënt.
*Patiënt gebruikt de persoonlijke gezondheidsomgeving om afspraken in te zien.

=====Post conditie=====
De patiënt heeft afspraken geraadpleegd via de persoonlijke gezondheidsomgeving.

=== Systemen & Systeemrollen ===
Zowel zorgaanbieder als patiënt maken gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen kennen ieder verschillende systeemrollen, die het uitwisselen van gegevens tussen deze systemen mogelijk maken. Hier gaat het om de afspraken van zorgaanbieder naar de patiënt.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| PGO
| style="background-color: white;"| AfspraakRaadplegend
| style="background-color: white;"| EA-{{VersieInfo|V2019.01|eAfspraak}}-AFR-FHIR
| style="background-color: white;"| Raadplegen afspraak bij zorgaanbieder
|-
| style="background-color: white;"| XIS
| style="background-color: white;"| AfspraakBeschikbaarstellend
| style="background-color: white;"| EA-{{VersieInfo|V2019.01|eAfspraak}}-AFB-FHIR
| style="background-color: white;"| Beschikbaarstellen afspraak aan de patiënt
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:Component Diagram - Afspraak raadplegen (Totaal)-v2.png |Componenten diagram afspraak raadplegen]]

'''Componenten diagram afspraak raadplegen'''

=== Transacties, Transactiegroepen en systeemrollen===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|Afspraken (PULL)
|style="background-color: white;vertical-align:top;"|Raadplegen afspraak
|style="background-color: white;vertical-align:top;"|EA-{{VersieInfo|V2019.01|eAfspraak}}-AFR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="2"|[[MedMij:V2019.01_FHIR_eAfspraak|eAfspraak in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen afspraak
|style="background-color: white;vertical-align:top;"|EA-{{VersieInfo|V2019.01|eAfspraak}}-AFB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:Use Case Diagram - Afspraak raadplegen-v2.png|Use case diagram afspraak raadplegen]]

'''Use case diagram afspraak raadplegen

==Use case: Afspraak maken door patiënt==
===Doel en relevantie===
Het maken van afspraken via een persoonlijke gezondheidsomgeving biedt patiënten gebruiksgemak. Dit draagt bij aan meer grip op de eigen gezondheidsgegevens en daarmee ook meer regie over de eigen gezondheid.

===Domein===
Afspraken met zorggebruikers (patiënten / cliënten) in het domein van de zorg.

===Context===
Het gaat om het elektronisch en gestructureerd afspraken kunnen maken vanuit een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO) naar een zorgaanbiederssysteem (XIS).

Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.
De beschrijving is infrastructuur-onafhankelijk.

===Informatie===
De informatie-elementen die van toepassing zijn, zijn vastgelegd in [https://decor.nictiz.nl/art-decor/decor-scenarios--eafspraken-?id=2.16.840.1.113883.2.4.3.11.60.61.4.3&effectiveDate=2017-10-10T14%3A19%3A43&datasetId=2.16.840.1.113883.2.4.3.11.60.61.1.1&datasetEffectiveDate=2017-08-01T14%3A56%3A38&conceptId=2.16.840.1.113883.2.4.3.11.60.61.2.1&conceptEffectiveDate=2017-08-01T14%3A56%3A38&language=nl-NL&scenariotree=true ART-DECOR eAfspraak].

=== Bedrijfsrollen ===
Deze use case kent twee bedrijfsrollen.

{| class="wikitable" "cellpadding="10" width="50%"
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Raadplegen afspraak slots

Sturen afspraakverzoek
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen afspraak slots

Ontvangen afspraak verzoek
|}
'''Bedrijfsrollen Afspraak inzien'''

Onderstaande afbeelding toont de bedrijfsrollen en de activiteiten die zij uitvoeren.

[[Bestand:Activity Diagram - Afspraak maken-v2.png|Activiteitendiagram afspraak maken]]

'''Activiteitendiagram maken afspraak'''

===Procesbeschrijving===
===='Patient journey' - Thomas van Beek ====
Het verhaal van de 'patient journey' van Thomas vindt u [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Thomas_van_Beek_MedMij.pdf hier].

Hieronder een voor Thomas relevante situatie waarbij het maken van afspraken een rol speelt.

<blockquote>De persoonlijke gezondheidsomgeving van Thomas en het ziekenhuisinformatiesysteem (ZIS) van het Noorderziekenhuis in Groningen zijn verbonden vanwege een eerder bezoek van Thomas in het ziekenhuis.

Thomas wil een afspraak maken voor de driemaandelijkse controle met een diabetesverpleegkundige. Hij wil dit ergens in de tweede week van januari. Zijn persoonlijke gezondheidsomgeving haalt de beschikbare tijden voor deze afspraak op uit het Groningse ziekenhuisinformatiesysteem. Thomas kiest voor woensdag 10 januari van 14:00 – 15:00 uur. Dit verzoek gaat via zijn persoonlijke gezondheidsomgeving naar het ziekenhuisinformatiesysteem, dat de ontvangst van dit verzoek bevestigt. De afspraak is door Thomas te raadplegen via zijn persoonlijke gezondheidsomgeving.
</blockquote>

====Proces====
Het deel van het proces waar het hier om gaat betreft:
*Een persoonlijke gezondheidsomgeving kan voor een bepaalde periode én een bepaald type afspraak de beschikbare tijden ophalen uit het XIS. Dit betreft het raadplegen van beschikbare afspraak slots. Een XIS stelt deze beschikbaar.
*Een persoonlijke gezondheidsomgeving kan - op basis van beschikbare slots - een verzoek tot het maken van een concrete afspraak doen aan het XIS. Een XIS kan een dergelijk afspraakverzoek wel/niet in behandeling nemen en stuurt daarvan een bevestiging.

=====Preconditie=====
De patiënt heeft toestemming gegeven voor het elektronisch maken van afspraken tussen het betreffende XIS en de eigen persoonlijke gezondheidsomgeving.
De patiënt wil bepaalde typen afspraken maken en de zorgaanbieder ondersteunt het maken van deze afspraken.

=====Proces stappen=====
*Het systeem van de zorgaanbieder (XIS) levert de beschikbare afspraak slots op basis van de filter criteria uit de persoonlijke gezondheidsomgeving.
*Het systeem van de patiënt (PGO) stuurt een verzoek om een bepaald type afspraak te maken in een bepaalde slot.
*Het systeem van de zorgaanbieder (XIS) ontvangt het afspraakverzoek en geeft een technisch antwoord. Het antwoord geeft aan of het verzoek wel of niet in behandeling genomen kan worden.

Indien een verzoek in behandeling genomen kan worden door XIS, dan kan verwerking enige tijd vergen. Het verzoek wordt niet altijd direct afgehandeld.

Bij een eventueel negatief antwoord van het XIS kan een patiënt ervoor kiezen het opnieuw proberen, bijvoorbeeld met een ander (opnieuw opgevraagd) slot.

=====Post conditie=====
Een persoonlijke gezondheidsomgeving heeft antwoord ontvangen van een XIS over een afspraakverzoek.

=== Systemen & Systeemrollen ===
Zowel zorgaanbieder als patiënt maken gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen hebben één of meer systeemrollen. Een systeemrol maakt het uitwisselen van bepaalde gegevens mogelijk. Hier gaat het om afspraken van zorgaanbieder naar patiënt. De kwalificatie van informatiesystemen vindt plaats op basis van systeemrollen.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Syteem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;vertical-align:top;" rowspan="2"| PGO
| style="background-color: white;"| AfspraakSlotsRaadplegend
| style="background-color: white;"| EA-1.1.3-ASR-FHIR
| style="background-color: white;"| Raadplegen afspraak slots bij de zorgaanbieder
|-
| style="background-color: white;"| AfspraakverzoekSturend
| style="background-color: white;"| EA-1.1.3-AVS-FHIR
| style="background-color: white;"| Sturen afspraakverzoek naar zorgaanbieder
|-
| style="background-color: white;vertical-align:top;" rowspan="2"| XIS
| style="background-color: white;"| AfspraakSlotsBeschikbaarstellend
| style="background-color: white;"| EA-1.1.3-ASB-FHIR
| style="background-color: white;"| Beschikbaar stellen afspraak slots
|-
| style="background-color: white;"| AfspraakverzoekOntvangend
| style="background-color: white;"| EA-1.1.3-AVO-FHIR
| style="background-color: white;"| Ontvangen afspraakverzoek van de patiënt
|-
|}
Zie ook onderstaande afbeelding.

[[Bestand:Component Diagram - Afspraak maken (Totaal)-v2.png|Componenten diagram afspraak maken]]

'''Componenten diagram afspraak maken'''

=== Transacties, Transactiegroepen en systeemrollen===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|AfspraakSlots (PULL)
|style="background-color: white;vertical-align:top;"|Raadplegen afspraak slots
|style="background-color: white;vertical-align:top;"|EA-1.1.3-ASR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="6"|[[MedMij:V2019.01_FHIR_eAfspraak|eAfspraak in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen afspraak slots
|style="background-color: white;vertical-align:top;"|EA-1.1.3-ASB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|AfspraakVerzoek (PUSH)
|style="background-color: white;vertical-align:top;"|Sturen afspraakverzoek
|style="background-color: white;vertical-align:top;"|EA-1.1.3-AVS-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|-
|style="background-color: white;vertical-align:top;"|Ontvangen afspraakverzoek
|style="background-color: white;vertical-align:top;"|EA-1.1.3-AVO-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:Use Case Diagram - Afspraak maken-v2.png|Use case diagram afspraak maken]]

'''Use case diagram afspraak maken

==Use case: Afspraak annuleren door patiënt==
===Doel en relevantie===
Inzicht in afspraken biedt patiënten overzicht en gebruiksgemak. Dat is een functionaliteit die voorwaardelijk is voor deze use case: 'annuleren van afspraken'. Een patiënt is verder geholpen door ook afspraken te kunnen annuleren vanuit een persoonlijke gezondheidsomgeving. Dit draagt bij aan meer grip op de eigen gezondheidsgegevens en daarmee ook meer regie over de eigen gezondheid.

===Domein===
Afspraken met zorggebruikers (patiënten / cliënten) in het domein van de zorg.

===Context===
Het gaat om het kunnen annuleren van een afspraak vanuit een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO) naar een zorgaanbiederssysteem (XIS).

Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.
De beschrijving is infrastructuur-onafhankelijk.

===Informatie===
De informatie-elementen die van toepassing zijn, zijn gedefinieerd in [https://decor.nictiz.nl/art-decor/decor-scenarios--eafspraken-?id=2.16.840.1.113883.2.4.3.11.60.61.4.3&effectiveDate=2017-10-10T14%3A19%3A43&datasetId=2.16.840.1.113883.2.4.3.11.60.61.1.1&datasetEffectiveDate=2017-08-01T14%3A56%3A38&conceptId=2.16.840.1.113883.2.4.3.11.60.61.2.1&conceptEffectiveDate=2017-08-01T14%3A56%3A38&language=nl-NL&scenariotree=true ART-DECOR eAfspraak].

=== Bedrijfsrollen ===
Deze use case kent twee bedrijfsrollen.

{| class="wikitable" "cellpadding="10" width="50%"
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Raadplegen afspraak
Sturen afspraak annulering
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen afspraak
Ontvangen afspraak annulering
|}
'''Bedrijfsrollen afspraken inzien'''

Onderstaande afbeelding toont de bedrijfsrollen en de activiteiten die zij uitvoeren.

[[Bestand:Activity Diagram - Afspraak annuleren-v2.png|Activiteitendiagram afspraak annuleren]]

'''Activiteitendiagram afspraak annuleren'''

===Procesbeschrijving===
===='Patient journey' - Thomas van Beek ====
Het verhaal van de 'patient journey' van Thomas vindt u [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Thomas_van_Beek_MedMij.pdf hier].

Hieronder een voor Thomas relevante situatie waarbij het annuleren van afspraken een rol speelt.

<blockquote>Thomas verhuist halverwege oktober 2017 voor zijn afstuderen naar Groningen. De afspraak voor de driemaandelijkse controle was al gemaakt in Rotterdam voor vrijdag 5 januari 2018. Thomas wil nu die afspraak afzeggen omdat hij die dag bezet is vanwege zijn afstudeerstage. Een nieuwe afspraak maakt hij liever in Groningen, dat is voor hem nu veel handiger.
Hij gebruikt zijn PGO om een verzoek te doen de afspraak in Rotterdam te annuleren. Een aantal uren later bevestigt de medisch secretaresse deze annulering. Thomas kan de afspraken weer raadplegen via zijn PGO.
</blockquote>

====Proces====
Het deel van het proces waar het hier om gaat betreft:
*Een persoonlijke gezondheidsomgeving kan achterhalen welk afspraken het verbonden XIS heeft voor de patiënt. Dit betreft het raadplegen van afspraken. Een XIS stelt deze beschikbaar.
*Een persoonlijke gezondheidsomgeving kan voor een bestaande afspraak een verzoek doen tot annulering. Een XIS ontvangt, behandelt en beantwoordt een dergelijk verzoek.

Een PGO heeft afspraken geraadpleegd en opvolging verzoek beoordeeld. Mocht het verzoek niet verwerkt zijn, kan een patiënt ervoor kiezen het opnieuw te proberen, of op een andere manier de zorgaanbieder te benaderen. Indien het verzoek verwerkt is, stelt XIS bij raadpleging door PGO de afspraak met status ‘geannuleerd’ beschikbaar.

=====Preconditie=====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van informatie over afspraken tussen het betreffende XIS en de eigen persoonlijke gezondheidsomgeving.
De patiënt wil bepaalde afspraken kunnen annuleren en de zorgaanbieder ondersteunt dit.

=====Proces stappen=====
*Het systeem van de patiënt (PGO) raadpleegt de beschikbare afspraken bij een XIS.
*Het systeem van de zorgaanbieder (XIS) levert de afspraken op voor de patiënt.
*Het systeem van de patiënt (PGO) stuurt een verzoek om de bestaande afspraak te annuleren.
*Het systeem van de zorgaanbieder (XIS) ontvangt de annulering en geeft een technisch antwoord. Het antwoord kan positief of negatief zijn voor het doorvoeren van de annulering.
*Het systeem van de patiënt (PGO) raadpleegt de beschikbare afspraken bij een XIS.
*Het systeem van de zorgaanbieder (XIS) levert de afspraken (waaronder de geannuleerde afspraak met status 'geannuleerd') op voor de patiënt.

Indien het verzoek verwerkt kan worden, stelt XIS de afspraak met status 'geannuleerd' beschikbaar, na raadpleging door patiënt vanuit zijn PGO.

=====Post conditie=====
Een persoonlijke gezondheidsomgeving heeft antwoord ontvangen van een XIS over een verzoek tot annulering van een afspraak.

=== Systemen & Systeemrollen ===
Zowel zorgaanbieder als patiënt maken gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen hebben één of meer systeemrollen. Een systeemrol maakt het uitwisselen van bepaalde gegevens mogelijk. Hier gaat het om afspraken annuleren van zorgaanbieder naar patiënt. De kwalificatie van informatiesystemen vindt plaats op basis van systeemrollen.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;" rowspan="2"| PGO
| style="background-color: white;"| AfsprakenRaadplegend
| style="background-color: white;"| EA-1.1.3-AFR-FHIR
| style="background-color: white;"| Raadplegen afspraken bij de zorgaanbieder
|-
| style="background-color: white;"| AfspraakAnnuleringSturend
| style="background-color: white;"| EA-1.1.3-AAS-FHIR
| style="background-color: white;"| Sturen afspraak annulering naar de zorgaanbieder
|-
| style="background-color: white;" rowspan="2"| XIS
| style="background-color: white;"| AfsprakenBeschikbaarstellend
| style="background-color: white;"| EA-1.1.3-AFB-FHIR
| style="background-color: white;"| Beschikbaarstellen afspraken aan de patiënt
|-
| style="background-color: white;"| AfspraakAnnuleringOntvangend
| style="background-color: white;"| EA-1.1.3-AAO-FHIR
| style="background-color: white;"| Ontvangen afspraak annulering van de patiënt
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:Component Diagram - Afspraak annuleren (Totaal)-v2.png |Componenten diagram afspraak annuleren]]

'''Componenten diagram afspraak annuleren'''

=== Transacties, Transactiegroepen en systeemrollen===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|Afspraken (PULL)
|style="background-color: white;vertical-align:top;"|Raadplegen afspraak
|style="background-color: white;vertical-align:top;"|EA-1.1.3-AFR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="4"|[[MedMij:V2019.01_FHIR_eAfspraak|eAfspraak in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen afspraak
|style="background-color: white;vertical-align:top;"|EA-1.1.3-AFB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|AfspraakAnnulering (PUSH)
|style="background-color: white;vertical-align:top;"|Sturen afspraak annulering
|style="background-color: white;vertical-align:top;"|EA-1.1.3-AAS-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|-
|style="background-color: white;vertical-align:top;"|Ontvangen afspraak annulering
|style="background-color: white;vertical-align:top;"|EA-1.1.3-AAO-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:Use Case Diagram - Afspraak annuleren-v2.png |Use case diagram afspraak annuleren]]

'''Use case diagram afspraak annuleren

==Use case: Afspraak wijzigen door patiënt==
===Doel en relevantie===
Inzicht in en het maken van afspraken biedt patiënten overzicht en gebruiksgemak. Dat zijn functionaliteiten die voorwaardelijk zijn voor deze use case: 'wijzigen van afspraken'. Een patiënt is verder geholpen door ook afspraken te kunnen wijzigen vanuit een persoonlijke gezondheidsomgeving. Een wijziging kan ook een annulering betreffen. Dit draagt verder bij aan meer grip op de eigen gezondheidsgegevens en daarmee ook meer regie over de eigen gezondheid.

===Domein===
Afspraken met zorggebruikers (patiënten / cliënten) in het domein van de zorg.

===Context===
Het gaat om het kunnen wijzigen van een afspraak vanuit een [https://www.patientenfederatie.nl/themas/persoonlijke-gezondheidsomgeving/ persoonlijke gezondheidsomgeving] (PGO) naar een zorgaanbiederssysteem (XIS).

Deze pagina bevat (verwijzingen naar) beschrijvingen van:
*informatie
*bedrijfsrollen (actoren),
*proces,
*systemen,
*systeemrollen,
*transactiegroepen en transacties, inclusief de inhoud van deze transacties.
De beschrijving is infrastructuur-onafhankelijk.

===Informatie===
De informatie-elementen die van toepassing zijn, zijn gedefinieerd in [https://decor.nictiz.nl/art-decor/decor-scenarios--eafspraken-?id=2.16.840.1.113883.2.4.3.11.60.61.4.3&effectiveDate=2017-10-10T14%3A19%3A43&datasetId=2.16.840.1.113883.2.4.3.11.60.61.1.1&datasetEffectiveDate=2017-08-01T14%3A56%3A38&conceptId=2.16.840.1.113883.2.4.3.11.60.61.2.1&conceptEffectiveDate=2017-08-01T14%3A56%3A38&language=nl-NL&scenariotree=true ART-DECOR eAfspraak].

=== Bedrijfsrollen ===
Deze use case kent twee bedrijfsrollen.

{| class="wikitable" "cellpadding="10" width="50%"
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Activiteit'''
|-
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:top;"|Raadplegen afspraak

Raadplegen afspraak slots

Sturen afspraakverzoek
|-
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen afspraak

Beschikbaarstellen afspraak slots

Ontvangen afspraakverzoek
|}
'''Bedrijfsrollen afspraken inzien'''

Onderstaande afbeelding toont de bedrijfsrollen en de activiteiten die zij uitvoeren.

[[Bestand:Activity Diagram - Afspraak wijzigen-v2.png|Activiteitendiagram afspraak wijzigen]]

'''Activiteitendiagram afspraak wijzigen'''

===Procesbeschrijving===
===='Patient journey' - Thomas van Beek ====
Het verhaal van de 'patient journey' van Thomas vindt u [https://www.nictiz.nl/wp-content/uploads/2018/05/Casus_Thomas_van_Beek_MedMij.pdf hier].

Hieronder een voor Thomas relevante situatie waarbij het wijzigen van afspraken een rol speelt.

<blockquote>In de loop van december krijgt Thomas een buitenkansje. Een aantal van zijn vrienden gaan met skivakantie van zaterdag 5 t/m 12 januari en er is een plekje vrijgekomen. Voor een zacht prijsje kan hij mee. Daar heeft hij veel zin in!

Thomas zet de skivakantie ‘s avonds laat in zijn agenda en ziet dat dit conflicteert met zijn controle-afspraak in het Noorderziekenhuis op 10 januari. Hij moet die afspraak gaan verzetten. Het is 23:15 en dus te laat om het ziekenhuis hiervoor direct te bellen.

Via zijn PGO kijkt hij daarom naar beschikbare tijden in de derde week van januari. Er blijkt gelukkig nog een gaatje te zijn op vrijdag 19 januari om 11:30 – 12:30. Het verzoek om te wijzigen gaat via zijn PGO naar het ZIS, dat de ontvangst van het verzoek bevestigt. Bij raadpleging van de afspraken vanuit PGO, stelt XIS de nieuwe afspraak beschikbaar, alsmede de oorspronkelijke afspraak met status ‘ geannuleerd’.
</blockquote>

====Proces====
Het deel van het proces waar het hier om gaat betreft:
*Het systeem van een zorgaanbieder (XIS) stelt afspraken beschikbaar aan het systeem van een patiënt (PGO).
*Een persoonlijke gezondheidsomgeving kan voor een bepaalde periode én een bepaald type afspraak de beschikbare tijden ophalen uit het XIS. Dit betreft het raadplegen van beschikbare afspraak slots. Een XIS stelt deze beschikbaar.
*Een persoonlijke gezondheidsomgeving kan - op basis van beschikbare slots - een verzoek tot het wijzigen van een concrete afspraak doen aan het XIS. Een XIS kan een dergelijk afspraak wijzigingsverzoek behandelen en ontvangst van het verzoek bevestigen.

=====Preconditie=====
De patiënt heeft toestemming gegeven voor het elektronisch uitwisselen van informatie over afspraken tussen het betreffende XIS en de eigen persoonlijke gezondheidsomgeving.
De patiënt wil een afspraak wijzigen en de zorgaanbieder ondersteunt het wijzigen van afspraken.

=====Proces stappen=====
*Het systeem van de patiënt (PGO) vraagt om beschikbare afspraken bij een XIS.
*Het systeem van de zorgaanbieder (XIS) levert de afspraken op voor de patiënt.
*Patiënt gebruikt de persoonlijke gezondheidsomgeving om afspraken in te zien en er één te selecteren die hij wil wijzigen.
*Het systeem van de patiënt (PGO) vraagt om beschikbare slots voor een bepaald type afspraak in een bepaalde tijdsperiode bij een XIS.
*Het systeem van de zorgaanbieder (XIS) levert de beschikbare afspraak slots op basis van de filter criteria uit de persoonlijke gezondheidsomgeving.
*Patiënt gebruikt de persoonlijke gezondheidsomgeving om beschikbare slots in te zien en er één te selecteren.
*Het systeem van de patiënt (PGO) stuurt een verzoek om de bestaande afspraak te wijzigen.
*Het systeem van de zorgaanbieder (XIS) ontvangt het afspraak wijzigingsverzoek en geeft een technisch antwoord. Het antwoord kan positief of negatief zijn voor de wijziging.

Patiënt raadpleegt opnieuw de afspraken vanuit zijn PGO + XIS stelt de nieuwe afspraak beschikbaar, alsmede de oorspronkelijke afspraak met status ‘geannuleerd’.

=====Post conditie=====
Een persoonlijke gezondheidsomgeving heeft antwoord ontvangen van een XIS over een afspraak wijzigingsverzoek.

Bij een eventueel negatief antwoord van het XIS kan een patiënt ervoor kiezen het opnieuw proberen, bijvoorbeeld met een ander (opnieuw opgevraagd) slot.
Bij een positief antwoord is de afspraak gewijzigd en inzichtelijk in zowel XIS als PGO.

=== Systemen & Systeemrollen ===
Zowel zorgaanbieder als patiënt maken gebruik van een informatiesysteem:
* PGO (patiënt)
* XIS (zorgaanbieder)

Deze systemen hebben één of meer systeemrollen. Een systeemrol maakt het uitwisselen van bepaalde gegevens mogelijk. De kwalificatie van informatiesystemen vindt plaats op basis van systeemrollen.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Systeem
!style="text-align:left;"|Naam systeemrol
!style="text-align:left;"|Systeemrolcode
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;" rowspan="3"| PGO
| style="background-color: white;"| AfspraakRaadplegend
| style="background-color: white;"| EA-1.1.3-AFO-FHIR
| style="background-color: white;"| Raadplegen afspraak bij zorgaanbieder
|-
| style="background-color: white;"| AfspraakSlotsRaadplegend
| style="background-color: white;"| EA-1.1.3-ASR-FHIR
| style="background-color: white;"| Raadplegen afspraak slots bij de zorgaanbieder
|-
| style="background-color: white;"| AfspraakWijzigingsverzoekSturend
| style="background-color: white;"| EA-1.1.3-AWS-FHIR
| style="background-color: white;"| Sturen afspraak wijzigingsverzoek
|-
| style="background-color: white;" rowspan="3"| XIS
| style="background-color: white;"| AfspraakBeschikbaarstellend
| style="background-color: white;"| EA-1.1.3-AFB-FHIR
| style="background-color: white;"| Beschikbaarstellen afspraak aan de patiënt
|-
| style="background-color: white;"| AfspraakSlotsBeschikbaarstellend
| style="background-color: white;"| EA-1.1.3-ASB-FHIR
| style="background-color: white;"| Beschikbaarstellen afspraak slots
|-
| style="background-color: white;"| AfspraakWijzigingsverzoekOntvangend
| style="background-color: white;"| EA-1.1.3-AWO-FHIR
| style="background-color: white;"| Ontvangen afspraak wijzigingsverzoek van de patiënt.
|-
|}

Zie ook onderstaande afbeelding.

[[Bestand:Component Diagram - Afspraak wijzigen (Totaal)-v2.png|Componenten diagram afspraak wijzigen]]

'''Componenten diagram afspraak wijzigen'''

=== Transacties, Transactiegroepen en systeemrollen===
Het uitwisselen van gegevens tussen de verschillende systeemrollen gebeurt op basis van transacties. Een transactiegroep is een verzameling van bij elkaar horende transacties (bijvoorbeeld een vraag- en antwoordbericht). Onderstaande tabel biedt een overzicht voor deze use case.

{| class="wikitable" "cellpadding="10"
! style="text-align:left;"| '''Transactiegroep'''
! style="text-align:left;"| '''Transactie'''
! style="text-align:left;"| '''Systeemrolcode'''
! style="text-align:left;"| '''Systeem'''
! style="text-align:left;"| '''Bedrijfsrol'''
! style="text-align:left;"| '''Technisch'''
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|Afspraken (PULL)
|style="background-color: white;vertical-align:top;"|Raadplegen afspraak
|style="background-color: white;vertical-align:top;"|EA-1.1.3-AFR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|style="background-color: white;vertical-align:middle;" rowspan="8"|[[MedMij:V2019.01_FHIR_eAfspraak|eAfspraak in FHIR]]
|-
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen afspraak
|style="background-color: white;vertical-align:top;"|EA-1.1.3-AFB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|AfspraakSlots (PULL)
|style="background-color: white;vertical-align:top;"|Raadplegen afspraak slots
|style="background-color: white;vertical-align:top;"|EA-1.1.3-ASR-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|-
|style="background-color: white;vertical-align:top;"|Beschikbaarstellen afspraak slots
|style="background-color: white;vertical-align:top;"|EA-1.1.3-ASB-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|-
|style="background-color: white;vertical-align:top;" rowspan="2"|AfspraakWijziging (PUSH)
|style="background-color: white;vertical-align:top;"|Sturen afspraak wijzigingsverzoek
|style="background-color: white;vertical-align:top;"|EA-1.1.3-AWS-FHIR
|style="background-color: white;vertical-align:top;"|PGO
|style="background-color: white;vertical-align:top;"|Patiënt
|-
|style="background-color: white;vertical-align:top;"|Ontvangen afspraak wijzigingsverzoek
|style="background-color: white;vertical-align:top;"|EA-1.1.3-AWO-FHIR
|style="background-color: white;vertical-align:top;"|XIS
|style="background-color: white;vertical-align:top;"|Zorgaanbieder
|}

===Use case diagram===
Onderstaande afbeelding toont bedrijfsrollen, activiteiten, systeemrollen, transacties en transactiegroep in samenhang.

[[Bestand:Use Case Diagram - Afspraak wijzigen-v2.png|Use case diagram afspraak wijzigen]]

'''Use case diagram afspraak wijzigen

=Functionaliteit=
-

=Verantwoordelijkheid voor informatie=
Er zijn geen specifieke toevoegingen over verantwoordelijkheden voor informatie.

=Afschermen van gegevens=
Er zijn geen afspraken over het afschermen van gegevens.

=Infrastructuur=
Er zijn geen afspraken over een specifieke infrastructuur waarop de informatie wordt uitgewisseld.

=Referenties=

{| class="wikitable" "cellpadding="10" width="100%"
!style="text-align:left;"|Auteur(s)
!style="text-align:left;"|Titel
!style="text-align:left;"|Versie
!style="text-align:left;"|Datum
!style="text-align:left;"|Bron
!style="text-align:left;"|Organisatie
|-
| style="background-color: white;"| AUTEUR(S)
| style="background-color: white;"| TITEL
| style="background-color: white;"| VERSIE
| style="background-color: white;"| DATUM
| style="background-color: white;"| BRON
| style="background-color: white;"| ORGANISATIE
|}
'''Referenties

=Bijlage: Documenthistorie=

==Release notes==

In onderstaande tabel staan de wijzigingen voor deze informatiestandaard. Zie de [[MedMij:V2019.01_Ontwerpen#Release_Notes|Ontwerpen landingspagina]] voor wijzigingen die op alle informatiestandaarden van toepassing zijn.

{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Versie
!style="text-align:left;"|BITS issue
!style="width:850px; text-align:left;"|Omschrijving

{{ReleaseNotes|release=1.1.9|package=2019.01 - Maart 2020|packageIssues=1|issues=1|MM-979}}
|-
| style="background-color: white; | 2019.01 - Oktober
| style="background-color: white; |
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-600 MM-600]
| style="background-color: white;"| Added missing (but required) identifier to eAfspraak-Appointment example instance.
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 1.1.3
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-214 MM-214]
| style="background-color: white;"|
* URI van mapping naar eAfspraak dataset aangepast binnen eAfspraak-Appointment en eAfspraak-Slot FHIR profielen.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 1.1.0
| style="background-color: white;"| [https://bits.nictiz.nl/browse/MM-104 MM-104]
| style="background-color: white;"| XIS kan wijzigingen en annuleringen niet naar PGO pushen. Scope van informatiestandaard aangepast.
|}

==Paginahistorie==
{| class="wikitable" "cellpadding="10"
!style="text-align:left;"|Release
!style="text-align:left;"|Datum
!style="text-align:left;"|Omschrijving
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 01-05-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 29-04-2020
| style="background-color: white;"|
* Nieuw package gegenereerd voor de april 2020 patchrelease
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - April 2020
| style="background-color: white;"| 28-04-2020
| style="background-color: white;"|
* Wijzigingen voor april 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Maart 2020
| style="background-color: white;"| 25-03-2020
| style="background-color: white;"|
* Wijzigingen voor maart 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Februari 2020
| style="background-color: white; | 27-02-2020
| style="background-color: white;"|
* Wijzigingen voor februari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - Januari 2020
| style="background-color: white; | 27-01-2020
| style="background-color: white;"|
* Wijzigingen voor januari 2020 patchrelease.
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 10-12-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white; | 2019.01 - November
| style="background-color: white; | 28-11-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - Oktober
| style="background-color: white;"| 30-10-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01 - September
| style="background-color: white;"| 30-09-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 18-06-2019
| style="background-color: white;"|
* Voetnoot geplaatst bij eAfspraak use cases maken, annuleren en wijzigen.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 28-03-2019
| style="background-color: white;"|
* Versienummer systeemrolcodes ophogen met 1 patchnummer.
|-
| style="background-color: white;"| 2019.01
| style="background-color: white;"| 11-03-2019
| style="background-color: white;"|
* Wijzigingen gepubliceerd in versie 2019.01, zie release notes.
* Verplaatsing release notes naar functionele pagina.
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 10-01-2019
| style="background-color: white;"|
* Aanpassing kwalificatieparagraaf
|-
| style="background-color: white;"| 2018.06
| style="background-color: white;"| 15-10-2018
| style="background-color: white;"|
* Aanpassing versienummer in titel.
* Toevoeging documenthistorie.
|}

MedMij:Vprepub-2019.01 OntwerpeAfspraak

2020-05-01T07:30:38Z

Stephan Opdenberg: versie package verhoogd