gz:V1.0 FHIR IG use cases 2.3: verschil tussen versies

Uit informatiestandaarden
Naar navigatie springen Naar zoeken springen
Lilian Minne (overleg | bijdragen)
Lilian Minne (overleg | bijdragen)
Geen bewerkingssamenvatting
Regel 43: Regel 43:


{{#lst:Gebz:V2.3_transaction_voorgaande_zwangerschap_samenvatting_23|transaction}}
{{#lst:Gebz:V2.3_transaction_voorgaande_zwangerschap_samenvatting_23|transaction}}
=Use case: Publish pregnancy file (integrale zwangerschapskaart)=
==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:V2.3_transaction_medmij_beschikbaarstellen_integrale_zwangerschapskaart|transaction}}

Versie van 16 jul 2021 12:30

1 Use case: Register Prio1 data[bewerken]

1.1 List of StructureDefinitions[bewerken]

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.

1.1.1 Prio 1 huidig[bewerken]

1.1.2 Prio 1 vorig[bewerken]

2 Use case: Register Birthcare Core Dataset data[bewerken]

2.1 List of StructureDefinitions[bewerken]

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.


3 Use case: Register Midwife Record data[bewerken]

3.1 List of StructureDefinitions[bewerken]

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.


4 Use case: Register Parturition Record[bewerken]

4.1 List of StructureDefinitions[bewerken]

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.


5 Use case: Register Pregnancy Ultrasound data[bewerken]

5.1 List of StructureDefinitions[bewerken]

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.


6 Use case: Register Previous Pregnancy Summary data[bewerken]

6.1 List of StructureDefinitions[bewerken]

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.