Brontekst bekijken van Gebz:V1.1 FHIR IG use cases 2.3

{{DISPLAYTITLE:FHIR Implementation Guide BirthCare use cases 2.3| FHIR Implementation Guide BirthCare}}
=Use case: Register Prio1 data=

==List of StructureDefinitions==
Please note that many birth care specific profiles are derived from nl-core profiles (e.g. bc-PregnancyObservation is derived from nl-core-observation) to support (re)use of profiles in multiple use cases. The meta.profile element of FHIR instances conforming these profiles should at least include the generic nl-core profile and preferably the specific birth care profile.
===Prio 1 huidig===
{{#lst:Gebz:V1.1_FHIR_IG_V2.3_transaction_prio1_huidige_zwangerschap|transaction}}
===Prio 1 vorig===
{{#lst:Gebz:V1.1_FHIR_IG_V2.3_transaction_prio1_vorige_zwangerschap|transaction}}

=Use case: Register Birthcare Core Dataset data=

==List of StructureDefinitions==
Please note that many birth care specific profiles are derived from nl-core profiles (e.g. bc-PregnancyObservation is derived from nl-core-observation) to support (re)use of profiles in multiple use cases. The meta.profile element of FHIR instances conforming these profiles should at least include the generic nl-core profile and preferably the specific birth care profile.

{{#lst:Gebz:V1.1_FHIR_IG_V2.3_transaction_kernset_geboortezorg|transaction}}

=Use case: Register Midwife Record data=

==List of StructureDefinitions==
Please note that many birth care specific profiles are derived from nl-core profiles (e.g. bc-PregnancyObservation is derived from nl-core-observation) to support (re)use of profiles in multiple use cases. The meta.profile element of FHIR instances conforming these profiles should at least include the generic nl-core profile and preferably the specific birth care profile.

{{#lst:Gebz:V1.1_FHIR_IG_V2.3_transaction_verloskundig_dossier_23|transaction}}

=Use case: Register Parturition Record=

==List of StructureDefinitions==
Please note that many birth care specific profiles are derived from nl-core profiles (e.g. bc-PregnancyObservation is derived from nl-core-observation) to support (re)use of profiles in multiple use cases. The meta.profile element of FHIR instances conforming these profiles should at least include the generic nl-core profile and preferably the specific birth care profile.

{{#lst:Gebz:V1.1_FHIR_IG_V2.3_transaction_bevallingsgegevens_23|transaction}}

=Use case: Register Pregnancy Ultrasound data=

==List of StructureDefinitions==
Please note that many birth care specific profiles are derived from nl-core profiles (e.g. bc-PregnancyObservation is derived from nl-core-observation) to support (re)use of profiles in multiple use cases. The meta.profile element of FHIR instances conforming these profiles should at least include the generic nl-core profile and preferably the specific birth care profile.

{{#lst:Gebz:V1.1_FHIR_IG_V2.3_transaction_zwangerschapsecho|transaction}}

=Use case: Register Previous Pregnancy Summary data=

==List of StructureDefinitions==
Please note that many birth care specific profiles are derived from nl-core profiles (e.g. bc-PregnancyObservation is derived from nl-core-observation) to support (re)use of profiles in multiple use cases. The meta.profile element of FHIR instances conforming these profiles should at least include the generic nl-core profile and preferably the specific birth care profile.

{{#lst:Gebz:V1.1_FHIR_IG_V2.3_transaction_voorgaande_zwangerschap_samenvatting_23|transaction}}