Source | swiss.mednet.fhir#0.15.0:MedNet interface implementation guide (v4.0.1) |
resourceType | StructureDefinition |
id | mni-serviceRequest |
canonical | https://mednet.swiss/fhir/StructureDefinition/mni-serviceRequest |
version | 0.15.0 |
status | active |
publisher | novcom AG |
name | MNIServiceRequest |
title | MedNet Interface (MNI) - ServiceRequest |
date | 2021-02-19T00:00:00+00:00 |
description | MedNet Interface (MNI) - ServiceRequest Profile |
copyright | novcom AG |
fhirVersion | 4.0.1 |
kind | resource |
abstract | false |
sdTtype | ServiceRequest |
derivation | constraint |
base | http://hl7.org/fhir/StructureDefinition/ServiceRequest |
Usages |
|
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
ServiceRequest | ServiceRequest | MedNet Interface (MNI) - ServiceRequest | ||
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.) | ||
contained | S | It is possible to include the requester and performer as embedded resource in this contained object. This way it is not needed to include it in the Bundle | ||
Slices for identifier | S | Slice: Unordered, Open by pattern:$this | ||
identifier:orderNr | S | 0..1 |
The orderNr of the calling system Required Pattern: At least the following |
|
type | 1..1 | CodeableConcept |
Description of identifier Fixed Value: (complex) |
|
coding | 1..* | Coding |
Code defined by a terminology system Fixed Value: (complex) |
|
system | 1..1 | uri |
Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/v2-0203 |
|
code | 1..1 | code |
Symbol in syntax defined by the system Fixed Value: MR |
|
display | 1..1 | string |
Representation defined by the system Fixed Value: Medical record number |
|
system | S | Uri that defines the Software that delivers the orderNr. If possible this uri should be unique for each order database for example https://mysoftware.ch/orderDB/123456 | ||
value | S | 1.. | The calling system order number | |
status | S | Recommended value : active | ||
intent | S |
order Fixed Value: order |
||
priority | S | |||
code | S |
Allow specifing the kind of form that should be prefilled by MedNet, like laboratory order, radiologiy order, hospital admission Binding: MedNet Interface (MNI) - ServiceRequest Code ValueSet ( extensible ) |
||
Slices for coding | S |
Used to categorize the service request type. Could be used to filter the forms proposed by mednet to the user
Slice: Unordered, Open by value:system, value:code |
||
coding:snomed | S | 0..1 | ||
system | S | 1..1 | Fixed Value: http://snomed.info/sct | |
code | S | 1..1 | 721965002 (Laboratory order) | 721964003 (Radiologiy order) | 721964003 (Hospital admission) | |
display | S | |||
orderDetail:requestCodes | S | Allow specifing element codes like laboratory analyse codes that should be preselected in the form | ||
coding | S | 1..1 | Allow specifing element codes like laboratory analyse codes that should be preselected in the form | |
system | S | Fixed Value: https://mednet.swiss/fhir/serviceRequest/orderDetail | ||
code | S | 1..1 | The element code that should be preselected | |
subject | S | Reference (MedNet Interface (MNI) - Patient) | Link to the Patient | |
requester | S | Reference (MedNet Interface (MNI) - PractitionerRole) | The MedNet practitioner that request to fill a document. MedNet will link the GLN of the practitionner with its own account id. MedNet will pre-select the account used to fill the document | |
performer | S | Reference (MedNet Interface (MNI) - PractitionerRole) | The MedNet institution, for which the document should be filled. This can be used to filter the forms proposed by mednet to the user. MedNet will only show the ones of this institution. MedNet will link the GLN of the institution with its own account ids. Multiple performer can be specified | |
Documentation for this format |
Produced 06 Apr 2023