StructureDefinition-mni-encounter

Sourceswiss.mednet.fhir#0.15.0:MedNet interface implementation guide (v4.0.1)
resourceTypeStructureDefinition
idmni-encounter
canonicalhttps://mednet.swiss/fhir/StructureDefinition/mni-encounter
version0.15.0
statusactive
publishernovcom AG
nameMNIEncounter
titleMedNet Interface (MNI) - Encounter
date2020-11-06T00:00:00+00:00
descriptionMedNet Interface (MNI) - Encounter Profile. An encounter will provide information about the context in which the form will be filled It is mainly used to deliver MedNet the Visit Nr (or Case Nr), and/or the orderNr from the calling System. The goal of those values is to allow saving the copy of the form and/or the later resulting report in the calling system to an internal event. It can also include informations about the priority of the request (if it is urgent or not), or the type of form that should be filled.
copyrightnovcom AG
fhirVersion4.0.1
kindresource
abstractfalse
sdTtypeEncounter
derivationconstraint
basehttp://hl7.org/fhir/StructureDefinition/Encounter
Usages
Name Flags Card. Type Description & Constraints doco
. . Encounter Encounter MedNet Interface (MNI) - Encounter
. . . id S The id is unique within the space of all resources of the same type on the same server It can be any combination of upper- or lower-case ASCII letters 'A'..'Z', and 'a'..'z', numerals ('0'..'9'), '-' and '.' with a length limit of 64 characters. (This might be an integer, an un-prefixed OID, UUID or any other identifier pattern that meets these constraints.)
. . . identifier S The visit or case Number
. . . . system S
. . . . value S 1.. The local visit or case number
. . . status S Recommended value : in-progress
. . . class S Recommended value : AMB
. . . subject S Reference (MedNet Interface (MNI) - Patient) Link to the Patient
. . . basedOn S Reference (MedNet Interface (MNI) - ServiceRequest) The ServiceRequest that initiated this encounter. It will provide the local order number

doco Documentation for this format

Produced 06 Apr 2023