Brontekst bekijken van Gebz:V1.2 FHIR IG use cases 3.2

==Use case: Client collects data from healthcare providers about her pregnancy in her personal health environment==

This is a patient's use case, in a personal health record (PHR) context, for exchanging pregnancy data. Functional specification of this use case is described in the [[Gebz:V3.2_Ontwerpen#Use_case:_Client_vraagt_via_PGO_Integrale_Zwangerschapskaart_op_.28MedMij_0.1.29|functional design wiki pages]].

Note: This implementation guide builds on the general guidelines described in the [[MedMij:V2020.01/FHIR_IG#Use_case_overarching_principles|use case overarching principles]]. 

===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.
===Collect client-related data from health care providers (MedMij 0.1 integrale zwangerschapskaart)===
{{#lst:Gebz:V1.2_FHIR_IG_V3.2_transaction_medmij_beschikbaarstellen_integrale_zwangerschapskaart|transaction}}

==Use case: Midwife data==

This is health provider use case for exchanging midwife data. Functional specification of this use case is described in the [[Gebz:V3.2_Ontwerpen#Use_case:_Verloskunde_gegevens|functional design wiki pages]].

===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.
===Midwife data===
{{#lst:Gebz:V3.2_transaction_verloskundegegevens|transaction}}

==Use case: Maternity data==

This is health provider use case for exchanging maternity data. Functional specification of this use case is described in the [[Gebz:V3.2_Ontwerpen#Use_case:_Kraamzorg_gegevens|functional design wiki pages]].

===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.
===Maternity data===
{{#lst:Gebz:V1.2_FHIR_IG_V3.2_transaction_kraamzorg|transaction}}

==Use case: Neonatology ==
{{IssueBox|De Use case moet nog ontwikkeld worden!}}

==Use case: Youth care ==
{{IssueBox|De Use case moet nog ontwikkeld worden!}}

==Use case: Minimum data set (Perined) ==
{{IssueBox|De Use case is nog niet gepubliceerd!}}

==Use case: Ultrasound data==

This is a health provider use case for exchanging ultrasound data. Functional specification of this use case is described in the [[Gebz:V3.2_Ontwerpen#Use_case:_Echoscopie|functional design wiki pages]].

===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.
===Ultrasound data===
{{#lst:Gebz:V1.2_FHIR_IG_V3.2_transaction_zwangerschapsecho|transaction}}

==Use case: Screening (RIVM): counseling ==
==Use case: Screening (RIVM): Non-invasive prenatal screening (NIPT) request ==
==Use case: Screening (RIVM): Non-invasive prenatal screening (NIPT) result ==
==Use case: Screening (RIVM): Ultrasound scan (SEO) request 1st term ==
==Use case: Screening (RIVM): Ultrasound scan (SEO) result 1st term ==
==Use case: Screening (RIVM): Ultrasound scan (SEO) result 2nd term ==