Gebz:FHIR Guidelines: verschil tussen versies

Uit informatiestandaarden
Naar navigatie springen Naar zoeken springen
Marc (overleg | bijdragen)
Marc (overleg | bijdragen)
 
(70 tussenliggende versies door 2 gebruikers niet weergegeven)
Regel 1: Regel 1:
{{IssueBox|Dit materiaal is in ontwikkeling en nog niet geschikt voor gebruik!}}
=FHIR Guidelines Geboortezorg=
FHIR Recipes Geboortezorg v2.3
==Pattern legend==
=bc-child-observation=
For several FHIR resource types we follow generic patterns in Birthcare. A pattern contains:
<syntaxhighlight lang="xml" heading="measurement_message.xml">
* an XML and/or JSON fragment
<Observation xmlns="http://hl7.org/fhir">
** all non-bracketed code is fixed
    <id value="[[! a unique id]]"/>
** parts in <nowiki>[[</nowiki>square brackets<nowiki>]]</nowiki> are variable and contain instructions on how to populate those
    <meta>
** a pipeline | separates text from example value
        <profile value="http://nictiz.nl/fhir/StructureDefinition/bc-BirthWeight"/>
** <nowiki>[[!</nowiki>comments<nowiki>]]</nowiki> are bracketed with exclamation mark
    </meta>
** bracketed blocks start with <nowiki>[[# text]]</nowiki> and end with <nowiki>[[/ text]]</nowiki>, text will contain information on how to populate the block in instances
    <status value="final"/>
** for instance: [http://hl7.org/fhir/STU3/observation.html#resource Observation.value[x]], if 'x' can vary, information about the content is provided
    <code>
** (square brackets do not clash too much with either XML or JSON syntax, other than that we follow Mustache syntax very loosely)
        <coding>
** (fragments are not intended to be machine-processable, but are for documentation, do not rely on fragments syntax to be faultless)
            <system value="[[system, see below | http://loinc.org]]"/>
** (not are recipes intended to replace StructureDefinitions, just to provide more readable documentation for implementers)
            <code value="[[code, see below | 8339-4"/>
* a valuation table
            <display value="[[display, see below | Birth weight Measured]]"/>
** with a dataset concept id
        </coding>
** fixed values for the valuation of bracketed elements of the fragment (i.e. those are fixed for that particular concept)
    </code>
** bracketed values for per-instance variable data (i.e. those are not fixed for that particular concept, usually the actual values that are exchanged)
    <subject>
        <reference value="[[reference to the Child Patient | Patient/XXX-KIND2VDWOUDEN" />
        <display value="[[display of reference | Kind 2 van der Wouden]]" />
    </subject>
    <context>
        <reference value="[[reference to the EpisodeOfCare | EpisodeOfCare/wouden-dossier-zwanger1]]"/>
    </context>
    [[#observation, see below]]
    <valueQuantity>
        <value value="2845"/>
        <system value="http://unitsofmeasure.org"/>
        <code value="gram"/>
    </valueQuantity>
    [[/observation]]
</Observation>
</syntaxhighlight>
 
{| class="wikitable"
|-
! pwd id !! system !! code !! display !! datatype !! value !! value-system !! value-code
|-
| peri23-dataelement-40060 || http://loinc.org || 8339-4 || Birth weight Measured || valueQuantity || <nowiki>[[Meting van het lichaamsgewicht zo kort mogelijk na de geboorte.]]<nowiki> || http://unitsofmeasure.org || gram
|}

Huidige versie van 13 jul 2020 om 15:16

FHIR Guidelines Geboortezorg

Pattern legend

For several FHIR resource types we follow generic patterns in Birthcare. A pattern contains:

  • an XML and/or JSON fragment
    • all non-bracketed code is fixed
    • parts in [[square brackets]] are variable and contain instructions on how to populate those
    • a pipeline | separates text from example value
    • [[!comments]] are bracketed with exclamation mark
    • bracketed blocks start with [[# text]] and end with [[/ text]], text will contain information on how to populate the block in instances
    • for instance: Observation.value[x], if 'x' can vary, information about the content is provided
    • (square brackets do not clash too much with either XML or JSON syntax, other than that we follow Mustache syntax very loosely)
    • (fragments are not intended to be machine-processable, but are for documentation, do not rely on fragments syntax to be faultless)
    • (not are recipes intended to replace StructureDefinitions, just to provide more readable documentation for implementers)
  • a valuation table
    • with a dataset concept id
    • fixed values for the valuation of bracketed elements of the fragment (i.e. those are fixed for that particular concept)
    • bracketed values for per-instance variable data (i.e. those are not fixed for that particular concept, usually the actual values that are exchanged)