diff --git a/README.md b/README.md index b349a2b..9fbbeb7 100644 --- a/README.md +++ b/README.md @@ -1 +1,2 @@ -# EHMI Endpoint Register +# EER Endpoint Register (EER-0.8) + diff --git a/input/fsh/eerAliases.fsh b/input/fsh/eerAliases.fsh new file mode 100644 index 0000000..1f52ab0 --- /dev/null +++ b/input/fsh/eerAliases.fsh @@ -0,0 +1,82 @@ +Alias: $EdsAuditEventTypes = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-auditevent-types +Alias: $EdsAuditEventSubTypes = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-auditevent-sub-types +Alias: $EdsAuditEventSubTypesValueset = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-auditevent-sub-types +Alias: $EdsAuditEventOutcome = http://hl7.org/fhir/audit-event-outcome +Alias: $EdsAuditEventSourceType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-auditevent-source-type +Alias: $EdsAuditEventParticipationRoleType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-auditevent-participationroletype +Alias: $EerAuditEventAgentWhoIdentifierTypes = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-auditevent-agent-who-identifier-types +Alias: $EdsAuditEventEntityType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-auditevent-entity-type +Alias: $EdsAuditEventEntityDetailType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-auditevent-entity-detail-type +Alias: $EdsAuditEventValueSet = http://medcomfhir.dk/fhir/ehmi/CodeSystem/EHMIAuditEventValueSet +Alias: $AuditEventAgentNetworkType = http://hl7.org/fhir/R4/valueset-network-type.html +Alias: $AuditEventEntityType = http://hl7.org/fhir/R4/valueset-audit-entity-type.html +Alias: $AuditEventAgentWhoTypes = http://hl7.org/fhir/R4/valueset-participation-role-type.html +Alias: $AuditEventSubTypes = http://hl7.org/fhir/restful-interaction +Alias: $AuditEventSubTypesValueset = http://hl7.org/fhir/R4/valueset-audit-event-sub-type.html +Alias: $AuditEventTypes = http://terminology.hl7.org/CodeSystem/audit-event-type +Alias: $AuditEventTypes2 = http://dicom.nema.org/resources/ontology/DCM +Alias: $EdsAuditEventEntityMessageType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-auditevent-entity-message-type + +Alias: $mCSDEndpointConnectionType = http://hl7.org/fhir/R4/valueset-endpoint-connection-type.html + + +Alias: $EerSorOrganizationIdentierType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-sor-organization-identier-type +Alias: $EerSorOrganizationIdentierTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/eer-sor-organization-identier-type-valueset + +Alias: $EerMessageDefinitionIdentifierSystem = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-messagedefinition-identifier-system +Alias: $EerMessageDefinitionIdentifierSystemVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/eer-messagedefinition-identifier-system-valueset + +Alias: $EerEndpointConnectionType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-endpoint-connection-type +Alias: $EerEndpointConnectionTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/eer-endpoint-connection-type-valueset + +Alias: $EerEndpointPayloadType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-payload-type +Alias: $EerEndpointPayloadTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-payload-type-valueset + +Alias: $EerSorOrganizationType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-sor-organization-type +Alias: $EerSorOrganizationTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/eer-sor-organization-type-valueset + +Alias: $EerSorIOOrganizationType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-sor-io-organization-type +Alias: $EerSorIOOrganizationTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/eer-sor-io-organization-type-valueset + +Alias: $EerEerMedComMessageDefinitionUri = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-medcom-message-definition-uri +Alias: $EerEerMedComMessageDefinitionUriVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/eer-medcom-message-definition-uri-valueset + +Alias: $EerMedComMessageDefinitionType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-medcom-message-definition-type +Alias: $EerMedComMessageDefinitionTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/eer-medcom-message-definition-type-valueset + +Alias: $EerSorUnitType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-sor-unit-type +Alias: $EerSorUnitTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/eer-sor-unit-type-valueset + +Alias: $EerSorClinicalAdministrativeHierarchy = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-sor-clinical-administrative-hierarchy +Alias: $EerSorClinicalAdministrativeHierarchyVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/eer-sor-clinical-administrative-hierarchy-valueset + +//Alias: $EerSorMunicipalityCode = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-sor-municipality-type +Alias: $EerSorMunicipalityCode = http://hl7.dk/fhir/core/CodeSystem/dk-core-municipality-codes +Alias: $EerSorMunicipalityCodeVS = http://hl7.dk/fhir/core/ValueSet/dk-core-MunicipalityCodes + +Alias: $EerSorRegionalCode = http://hl7.dk/fhir/core/CodeSystem/dk-core-regional-subdivision-codes +Alias: $EerSorRegionalCodeVS = http://hl7.dk/fhir/core/ValueSet/dk-core-RegionalSubDivisionCodes + +Alias: $MessageEvents = http://medcomfhir.dk/ig/terminology/CodeSystem/medcom-messaging-eventCodes + +Alias: $EerUsageContextCodeSystem = http://terminology.hl7.org/CodeSystem/usage-context-type +Alias: $EerUsageContextCodeSystemVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/eer-messagedefinition-use-context-code-valueset + +Alias: $EerDigSigCS = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-digital-signature-type +Alias: $EerDigSigVS = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-digital-signature-type-valueset + +/* +Alias: $StatusCodes = http://hl7.org/fhir/encounter-status +Alias: $ActCodes = http://terminology.hl7.org/CodeSystem/v3-ActCode +Alias: $EventStatus = http://hl7.org/fhir/event-status +Alias: $CategoryCodes = http://medcomfhir.dk/fhir/carecommunication/CodeSystem/medcom-careCommunication-categoryCodes +Alias: $ServerityCode = http://hl7.org/fhir/issue-severity +Alias: $CodeCode = http://hl7.org/fhir/issue-type +Alias: $AcknowledgementCode = http://hl7.org/fhir/ValueSet/Acknowledgement-code +Alias: $BundleType = http://hl7.org/fhir/bundle-type +Alias: $Use = http://medcomfhir.dk/fhir/messaging/CodeSystem/medcom-messaging-destinationUse +Alias: $MessageEvents = http://medcomfhir.dk/fhir/messaging/CodeSystem/medcom-messaging-eventCodes +Alias: $SORCode = urn:oid:1.2.208.176.1.1 +Alias: $EANCode = urn:oid:1.3.88 +Alias: $activityCodes = http://medcomfhir.dk/fhir/messaging/CodeSystem/medcom-messaging-activityCodes +*/ \ No newline at end of file diff --git a/input/fsh/ehmiCoreDeviceExtension.fsh b/input/fsh/eerCoreDeviceExtension.fsh similarity index 58% rename from input/fsh/ehmiCoreDeviceExtension.fsh rename to input/fsh/eerCoreDeviceExtension.fsh index 90f26f8..729b1c7 100644 --- a/input/fsh/ehmiCoreDeviceExtension.fsh +++ b/input/fsh/eerCoreDeviceExtension.fsh @@ -1,21 +1,31 @@ -Extension: EHMICoreSystemExtension -Id: ehmi-core-system-extension -Title: "ehmi Core System Extension" -Description: "Reference to a Device that is used to specify one or more systems which an Endpoint uses" +Extension: EerEUASystemExtension +Id: eer-dk-eua-system-extension +Title: "EER System Extension - EUA" +Description: "Reference to a Device that is used to specify one or more systems which an Endpoint uses +This is equivalent to the SOR-element" +//* value[x] Reference +* value[x] 0.. +* value[x] only Reference(EerDeviceEUA) + +Extension: EerMSHSystemExtension +Id: eer-dk-msh-system-extension +Title: "EER System Extension - MSH" +Description: "Reference to a Device that is used to specify one or more systems which an Endpoint uses +This is equivalent to the SOR-element" //* value[x] Reference * value[x] 0.. -* value[x] only Reference(Device) +* value[x] only Reference(EerDeviceMSH) -Extension: EHMICoreNetworkSupplySystemExtension -Id: ehmi-dk-core-network-supply-system-extension -Title: "ehmiCoreDeviceExtension" +Extension: EerCoreNetworkSupplySystemExtension +Id: eer-dk-network-supply-system-extension +Title: "EER System Extension - AP" Description: "Reference to a Device that is used to specify one or more systems which an Endpoint uses" * value[x] 0.. -* value[x] only Reference(Device) +* value[x] only Reference(EerDeviceAP) /* -Profile: ehmiCoreSystemExtension -Parent: ehmiCoreDeviceExtension +Profile: EerCoreDeviceExtension +Parent: EerCoreSystemExtension Id: ehmi.dk.core.system.extension Title: "ehmi Core System Extension" Description: """ diff --git a/input/fsh/eerDevice.fsh b/input/fsh/eerDevice.fsh new file mode 100644 index 0000000..fd5f723 --- /dev/null +++ b/input/fsh/eerDevice.fsh @@ -0,0 +1,42 @@ +Profile: EerDevice +Parent: Device +Title: "EER EndpointDevice - General" +Description: "An EHMI profile of the Device resource." +* udiCarrier 0..0 +* identifier 1..1 MS +* definition 1..1 MS +* status 1..1 MS +* manufacturer 1..1 MS +* lotNumber 0..0 +* serialNumber 0..0 +* deviceName 1..1 MS +* modelNumber 0..0 +* partNumber 0..0 +* type 0..0 +* specialization 0..0 +* property 0..0 +* patient 0..0 +* owner MS +* contact 0..0 +* location 0..0 +* url 0..0 +* safety 0..0 +* parent 0..0 + +Profile: EerDeviceAP +Parent: EerDevice +Title: "EER EndpointDevice - AP" +Description: "An EerDeviceAP profile of the EerDevice resource." +//* definition = Reference(EerEndpointDeviceDefinitionAP) + +Profile: EerDeviceMSH +Parent: EerDevice +Title: "EER EndpointDevice - MSH" +Description: "An EerDeviceMSH profile of the EerDevice resource." +//* definition = Reference(EerEndpointDeviceDefinitionMSH) + +Profile: EerDeviceEUA +Parent: EerDevice +Title: "EER EndpointDevice - EUA" +Description: "An EerDeviceEUA profile of the EerDevice resource." +//* definition = Reference(EerEndpointDeviceDefinitionEUA) diff --git a/input/fsh/eerDeviceDefinition.fsh b/input/fsh/eerDeviceDefinition.fsh index d87e6f9..693d738 100644 --- a/input/fsh/eerDeviceDefinition.fsh +++ b/input/fsh/eerDeviceDefinition.fsh @@ -1,22 +1,44 @@ -Profile: EerDeviceDefinition +Profile: EerEndpointDeviceDefinition Parent: DeviceDefinition +Title: "EER EndpointDeviceDefinition" Description: "An EER profile of the DeviceDefinition resource." * identifier 1..1 MS -* manufacturerString 1..1 MS // bør være manufacturerReference, men for nu ok +* udiDeviceIdentifier 0..0 +//* manufacturerString 1..1 MS // bør være manufacturerReference, men for nu ok // * manufacturerReference -* deviceName 1..1 -* deviceName.name MS -* deviceName.type = http://hl7.org/fhir/device-nametype#manufacturer-name "Manufacturer name" (exactly) +//* deviceName 1..1 +//* deviceName.name MS +//* deviceName.type = http://hl7.org/fhir/device-nametype#manufacturer-name "Manufacturer name" (exactly) * type from EerDeviceTypeVS * type 1..1 MS -* specialization.systemType 1..1 MS +//* specialization.systemType 1..1 MS -Profile: EerDeviceDefinitionLPS -Parent: EerDeviceDefinition -Description: "An EerDeviceDefinition-LPS profile of the EerDeviceDefinition resource." +Profile: EerEndpointDeviceDefinitionAP +Parent: EerEndpointDeviceDefinition +Title: "EER EndpointDeviceDefinition - AP" +Description: "An EerEndpointDeviceDefinition-EOJ profile of the EerEndpointDeviceDefinition resource." +* type = EerDeviceType#AP "eDelivery Access Point" (exactly) + +Profile: EerEndpointDeviceDefinitionMSH +Parent: EerEndpointDeviceDefinition +Title: "EER EndpointDeviceDefinition - MSH" +Description: "An EerEndpointDeviceDefinition-EOJ profile of the EerEndpointDeviceDefinition resource." +* type = EerDeviceType#MSH "Message Service Handler" (exactly) + +Profile: EerEndpointDeviceDefinitionEUA +Parent: EerEndpointDeviceDefinition +Title: "EER EndpointDeviceDefinition - EUA" +Description: "An EerEndpointDeviceDefinition-EOJ profile of the EerEndpointDeviceDefinition resource." +* type = EerDeviceType#EUA "End User Application" (exactly) + +/* +Profile: EerEndpointDeviceDefinitionLPS +Parent: EerEndpointDeviceDefinition +Description: "An EerEndpointDeviceDefinition-LPS profile of the EerEndpointDeviceDefinition resource." * type = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-device-type#LPS "General Practitioner System" -Profile: EerDeviceDefinitionEOJ -Parent: EerDeviceDefinition -Description: "An EerDeviceDefinition-EOJ profile of the EerDeviceDefinition resource." +Profile: EerEndpointDeviceDefinitionEOJ +Parent: EerEndpointDeviceDefinition +Description: "An EerEndpointDeviceDefinition-EOJ profile of the EerEndpointDeviceDefinition resource." * type = EerDeviceType#EOJ "EOJ" +*/ \ No newline at end of file diff --git a/input/fsh/eerDeviceValueSets.fsh b/input/fsh/eerDeviceValueSets.fsh index edb30c0..94d75e0 100644 --- a/input/fsh/eerDeviceValueSets.fsh +++ b/input/fsh/eerDeviceValueSets.fsh @@ -9,11 +9,13 @@ Description: "CodeSystem containing codes for EER-Device-Type" * ^caseSensitive = true * #EOJ "Electronical Homecare Journal" "EOJ" * #LPS "General Practitioner System" "LPS" - +* #AP "eDelivery Access Point" "AP" +* #MSH "Message Service Handler" "MSH" +* #EUA "End User Application" "EUA" ValueSet: EerDeviceTypeVS Id: eer-device-type-valueset -Title: "EHMI SOR Organization Identier Type Valueset" +Title: "EER SOR Organization Identier Type Valueset" Description: "ValueSet containing codes for EER-Device-Type" * ^version = "1.0.0" * ^status = #active diff --git a/input/fsh/eerDigitalSignature.fsh b/input/fsh/eerDigitalSignature.fsh new file mode 100644 index 0000000..10d1558 --- /dev/null +++ b/input/fsh/eerDigitalSignature.fsh @@ -0,0 +1,25 @@ +Profile: EerDigitalSignature +Parent: Basic +Id: eer.dk.digitalsignature +Title: "EER Digital Signature for eDelivery" +Description: "EER Digital Signature for eDelivery" +* identifier 1..1 MS SU +* code.coding.code = #ETSI +* code.coding.code from $EerDigSigVS +* code.coding.display = "Digital Signature" +* code.coding.system = $EerDigSigCS +* extension contains eer-dk-digital-signature-extension named digitalsignature 1..1 MS + + + +Extension: EerDigitalSignatureExtension +Id: eer-dk-digital-signature-extension +Title: "EER Digital Signature for eDelivery Extension" +Description: "EER Digital Signature for eDelivery Extension" +* valueSignature.sigFormat 1..1 +* valueSignature.data 1..1 +* value[x] + + + + diff --git a/input/fsh/eerEndpoints.fsh b/input/fsh/eerEndpoints.fsh new file mode 100644 index 0000000..995e1e0 --- /dev/null +++ b/input/fsh/eerEndpoints.fsh @@ -0,0 +1,138 @@ +Profile: EerEndpoint +Parent: MCSDEndpoint +Id: eer.dk.endpoint +Title: "EER Endpoint - General Endpoint" +Description: """ +A profile on the mCSD Endpoint. + +An Organization may be reachable through electronic Endpoint(s). +An Endpoint may be a eDelivery receiver or a vans receiver (or in the future a FHIR server, an IHE web services actor, or some other +mechanism). +""" +* identifier 1..1 MS SU +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type from $EerAuditEventAgentWhoIdentifierTypes +* identifier.value 1..1 MS SU +* connectionType from eer-endpoint-connection-type-valueset +* period 1..1 MS SU + +Profile: EerEndpointMessaging +Parent: EerEndpoint +Id: eer.dk.endpoint.messaging +Title: "EER Endpoint - General for Messaging" +Description: """ +A profile on the mCSD Endpoint. + +An Organization may be reachable through electronic Endpoint(s). +An Endpoint may be a eDelivery receiver or a vans receiver (or in the future a FHIR server, an IHE web services actor, or some other +mechanism). +""" +* identifier 1..1 MS SU +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN +//* identifier.code = #official +* identifier.value 1..1 MS SU +* managingOrganization only Reference(EerSorOrganization) +* connectionType from eer-endpoint-connection-type-valueset +* period 1..1 MS SU +* payloadType from eer-medcom-message-definition-uri-valueset +* payloadType 1..* MS SU +* payloadMimeType 1..* MS SU +//* extension contains eer-dk-eua-system-extension named eua-system 0..* MS +* extension contains eer-dk-msh-system-extension named msh-system 0..* MS +* extension contains eer-dk-network-supply-system-extension named networkSupplySystem 0..* MS + +Profile: EerEndpointMessagingEdelivery +Parent: EerEndpointMessaging +Id: eer.dk.messaging.edelivery +Title: "EER Endpoint Messaging - eDelivery" +Description: "EER Endpoint Messaging - eDelivery" +* connectionType = $EerEndpointConnectionType#EerMessagingEdelivery (exactly) + +Profile: EerEndpointMessagingEdeliveryFhir +Parent: EerEndpointMessagingEdelivery +Id: eer.dk.messaging.edelivery.fhir +Title: "EER Endpoint Messaging eDelivery - FHIR" +Description: "EER Endpoint Messaging eDelivery - FHIR" +//* payloadType = $EerEndpointPayloadType#urn:dk:medcom:prod:messaging:fhir (exactly) +//* payloadType = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 + +/* +Profile: EereDeliveryMessagingEdiEndpoint +Parent: EerEndpointMessagingEdelivery +Id: eer.dk.messaging.edelivery.edi +Title: "EER Endpoint eDelivery EDI Messaging" +Description: "EER Endpoint eDelivery EDI Messaging" +//* payloadType = $EerEndpointPayloadType#urn:dk:medcom:prod:messaging:edi (exactly) +//* payloadType.coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q +//* payloadType[0].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q +//* payloadType[+].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q +//* payloadType[+].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q +*/ + +/* +Profile: EereDeliveryMessagingOioxmlEndpoint +Parent: EerEndpointMessagingEdelivery +Id: eer.dk.messaging.edelivery.oioxml +Title: "EER Endpoint eDelivery Oioxml Messaging" +Description: "EER Endpoint eDelivery Oioxml Messaging" +//* payloadType = $EerEndpointPayloadType#urn:dk:medcom:prod:messaging:oioxml (exactly) +//* payloadType.coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" +//* payloadType[0].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" +//* payloadType[+].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" +//* payloadType[+].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" +*/ + +/* +Profile: EerMessagingVansEndpoint +Parent: EerEndpointMessaging +Id: eer.dk.messaging.vans +Title: "EER Endpoint VANS Messaging" +Description: "EER Endpoint VANS Messaging" +* connectionType = $EerEndpointConnectionType#vansMessaging (exactly) +*/ + +/* +Profile: EerMessagingVansFhirEndpoint +Parent: EerMessagingVansEndpoint +Id: eer.dk.messaging.vans.fhir +Title: "EER Endpoint VANS FHIR Messaging" +Description: "EER Endpoint VANS FHIR Messaging" +//* payloadType = $EerEndpointPayloadType#urn:dk:medcom:prod:messaging:fhir (exactly) +//* payloadType = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 +*/ + +/* +Profile: EerMessagingVansEdiEndpoint +Parent: EerMessagingVansEndpoint +Id: eer.dk.messaging.vans.edi +Title: "EER Endpoint VANS EDI Messaging" +Description: "EER Endpoint VANS EDI Messaging" +//* payloadType = $EerEndpointPayloadType#urn:dk:medcom:prod:messaging:edi (exactly) +//* payloadType.coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q +//* payloadType[0].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q +//* payloadType[+].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q +//* payloadType[+].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q +*/ + +/* +Profile: EerMessagingVansOioxmlEndpoint +Parent: EerMessagingVansEndpoint +Id: eer.dk.messaging.vans.oioxml +Title: "EER Endpoint VANS Oioxml Messaging" +Description: "EER Endpoint VANS Oioxml Messaging" +//* payloadType = $EerEndpointPayloadType#urn:dk:medcom:prod:messaging:oioxml (exactly) +//* payloadType.coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" +//* payloadType[0].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" +//* payloadType[+].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" +//* payloadType[+].coding.code = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" +*/ + +/* +Profile: SOREndpointDocShare +Parent: MCSDEndpointDocShare +Id: medcom.ehmi.dk.mcsd.DocShare +Title: "MedCom SOR DocShare Endpoint" +Description: """ SOR """ + +*/ \ No newline at end of file diff --git a/input/fsh/ehmiMedComMessageValueSets.fsh b/input/fsh/eerMedComMessageValueSets.fsh similarity index 95% rename from input/fsh/ehmiMedComMessageValueSets.fsh rename to input/fsh/eerMedComMessageValueSets.fsh index e45e9cd..b786166 100644 --- a/input/fsh/ehmiMedComMessageValueSets.fsh +++ b/input/fsh/eerMedComMessageValueSets.fsh @@ -1,7 +1,7 @@ -CodeSystem: MedComMessageDefinitionUri -Id: ehmi-medcom-message-definition-uri +CodeSystem: EerMedComMessageDefinitionUri +Id: eer-medcom-message-definition-uri Title: "MedCom Message Definition Uri CS" -Description: "CodeSystem containing codes for EHMI ehmi-medcom-message-definition-uri" +Description: "CodeSystem containing codes for EHMI eer-medcom-message-definition-uri" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" @@ -117,17 +117,18 @@ Description: "CodeSystem containing codes for EHMI ehmi-medcom-message-definitio * #urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:carecommunication:2.1 "CareCommunication 2.1" * #urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:carecommunication:3.0 "CareCommunication 3.0" * #urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:homecareobservation:1.0 "HomeCareObservation 1.0" +* #urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:homecareobservation:2.0 "HomeCareObservation 2.0" * #urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:1.0 "Acknowledgement 1.0" * #urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 "Acknowledgement 2.0" * #urn:dk:healthcare:medcom:messaging:envelope:xml:sbdh:1.0 "SBDH 1.0" * #urn:dk:healthcare:medcom:messaging:envelope:xml:sbdhacknowledgement:1.0 "SBDH Ack 1.0" -ValueSet: MedComMessageDefinitionUriVS -Id: ehmi-medcom-message-definition-uri-valueset +ValueSet: EerMedComMessageDefinitionUriVS +Id: eer-medcom-message-definition-uri-valueset Title: "MedCom Message Definition Uri Valueset" -Description: "ValueSet containing codes for EHMI ehmi-medcom-message-definition-uri" +Description: "ValueSet containing codes for EHMI eer-medcom-message-definition-uri" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = false -* include codes from system ehmi-medcom-message-definition-uri +* include codes from system eer-medcom-message-definition-uri diff --git a/input/fsh/ehmiMessageDefinition-fhir.fsh b/input/fsh/eerMessageDefinition-fhir.fsh similarity index 56% rename from input/fsh/ehmiMessageDefinition-fhir.fsh rename to input/fsh/eerMessageDefinition-fhir.fsh index 5309fc9..831e985 100644 --- a/input/fsh/ehmiMessageDefinition-fhir.fsh +++ b/input/fsh/eerMessageDefinition-fhir.fsh @@ -2,14 +2,14 @@ Profile: EerMessageDefinitionFhir Parent: EerMessageDefinition Description: "An example profile of the MessageDefinition-fhir resource." * identifier.system = $EerMessageDefinitionIdentifierSystem#urn:dk:healthcare:medcom:messaging:fhir (exactly) -* identifier.type = $EHMIMedComMessageDefinitionType#FHIR -* useContext.code = $EHMIUsageContextCodeSystem#workflow (exactly) -* useContext.code.system = $EHMIUsageContextCodeSystem (exactly) +* identifier.type = $EerMedComMessageDefinitionType#FHIR +* useContext.code = $EerUsageContextCodeSystem#workflow (exactly) +* useContext.code.system = $EerUsageContextCodeSystem (exactly) Profile: EerMsgDefHomeCareObservation Parent: EerMessageDefinitionFhir Description: "An example profile of the MessageDefinition-fhir resource." * identifier.system = $EerMessageDefinitionIdentifierSystem#urn:dk:healthcare:medcom:messaging:fhir (exactly) -* identifier.type = $EHMIMedComMessageDefinitionType#FHIR -* useContext.code = $EHMIUsageContextCodeSystem#workflow (exactly) -* useContext.code.system = $EHMIUsageContextCodeSystem (exactly) +* identifier.type = $EerMedComMessageDefinitionType#FHIR +* useContext.code = $EerUsageContextCodeSystem#workflow (exactly) +* useContext.code.system = $EerUsageContextCodeSystem (exactly) diff --git a/input/fsh/ehmiMessageDefinition-sbdh.fsh b/input/fsh/eerMessageDefinition-sbdh.fsh similarity index 61% rename from input/fsh/ehmiMessageDefinition-sbdh.fsh rename to input/fsh/eerMessageDefinition-sbdh.fsh index 6d82e69..2281ace 100644 --- a/input/fsh/ehmiMessageDefinition-sbdh.fsh +++ b/input/fsh/eerMessageDefinition-sbdh.fsh @@ -3,8 +3,8 @@ Parent: EerMessageDefinition Description: "An example profile of the MessageDefinition-envelope resource." //* id = * identifier.system = $EerMessageDefinitionIdentifierSystem#urn:dk:healthcare:medcom:messaging:envelope (exactly) -* identifier.type = $EHMIMedComMessageDefinitionType#ENVELOPE (exactly) -* useContext.code = $EHMIUsageContextCodeSystem#workflow (exactly) -* useContext.code.system = $EHMIUsageContextCodeSystem (exactly) +* identifier.type = $EerMedComMessageDefinitionType#ENVELOPE (exactly) +* useContext.code = $EerUsageContextCodeSystem#workflow (exactly) +* useContext.code.system = $EerUsageContextCodeSystem (exactly) * eventCoding = $MessageEvents#empty-message (exactly) diff --git a/input/fsh/ehmiMessageDefinition.fsh b/input/fsh/eerMessageDefinition.fsh similarity index 82% rename from input/fsh/ehmiMessageDefinition.fsh rename to input/fsh/eerMessageDefinition.fsh index a46fe8b..162de71 100644 --- a/input/fsh/ehmiMessageDefinition.fsh +++ b/input/fsh/eerMessageDefinition.fsh @@ -1,24 +1,24 @@ Profile: EerMessageDefinition Parent: MessageDefinition Description: "An example profile of the MessageDefinition resource." -//* url from ehmi-medcom-message-definition-uri-valueset +//* url from eer-medcom-message-definition-uri-valueset * identifier 1..1 MS SU -//* identifier.system from ehmi-medcom-message-definition-uri-valueset -* identifier.system from ehmi-messagedefinition-identifer-system-valueset +//* identifier.system from eer-medcom-message-definition-uri-valueset +* identifier.system from eer-messagedefinition-identifer-system-valueset * identifier.system 1..1 //MS SU //* identifier.system = $EerMessageDefinitionIdentifierSystem#MedCom * identifier.period.start 1..1 MS SU * identifier.period.end 0..1 MS SU -* identifier.type from ehmi-medcom-message-definition-type-valueset +* identifier.type from eer-medcom-message-definition-type-valueset * identifier.type 1..1 MS SU -* identifier.type.coding.system = $EHMIMedComMessageDefinitionType +* identifier.type.coding.system = $EerMedComMessageDefinitionType * identifier.use 1..1 MS SU * identifier.value 1..1 MS SU * version 1..1 MS SU //* name 1..1 MS SU * title 1..1 MS SU * replaces.value 0..1 MS -* publisher 1..1 MS SU +* publisher 0..1 MS SU * publisher = "MedCom, https://www.medcom.dk" * contact 1.. MS SU * contact ^slicing.discriminator.type = #value @@ -51,8 +51,8 @@ Description: "An example profile of the MessageDefinition resource." //* useContext 1..1 MS SU //* Message Context //* useContext.code.system from http://terminology.hl7.org/CodeSystem/usage-context-type -* useContext.code.system = $EHMIUsageContextCodeSystem -* useContext.code from $EHMIUsageContextCodeSystemVS +* useContext.code.system = $EerUsageContextCodeSystem +* useContext.code from $EerUsageContextCodeSystemVS * jurisdiction 1..1 MS SU * jurisdiction = #DK //* jurisdiction.coding.system = diff --git a/input/fsh/ehmiRegMunValueSets.fsh b/input/fsh/eerRegMunValueSets.fsh similarity index 77% rename from input/fsh/ehmiRegMunValueSets.fsh rename to input/fsh/eerRegMunValueSets.fsh index 98fe623..c94595b 100644 --- a/input/fsh/ehmiRegMunValueSets.fsh +++ b/input/fsh/eerRegMunValueSets.fsh @@ -1,7 +1,7 @@ -CodeSystem: EHMISORRegionType -Id: ehmi-sor-region-type -Title: "EHMI SOR Region Types CS" -Description: "ehmi-sor-region-type for the EHMI Messaging Infrastructure" +CodeSystem: EerSorRegionType +Id: eer-sor-region-type +Title: "EER SOR Region Types CS" +Description: "eer-sor-region-type for the EHMI Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" @@ -14,21 +14,21 @@ Description: "ehmi-sor-region-type for the EHMI Messaging Infrastructure" * #1085 "Region Sjælland" * #1083 "SOR Southern Region (DK:Region Syddanmark)" -ValueSet: EHMISORRegionTypeVS -Id: ehmi-sor-region-type-valueset -Title: "EHMI SOR Region Types Valueset" -Description: "ValueSet containing codes for EHMI ehmi-sor-region-type" +ValueSet: EerSorRegionTypeVS +Id: eer-sor-region-type-valueset +Title: "EER SOR Region Types Valueset" +Description: "ValueSet containing codes for EHMI eer-sor-region-type" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true -//* include codes from system ehmi-sor-region-type +//* include codes from system eer-sor-region-type * include codes from system http://hl7.dk/fhir/core/CodeSystem/dk-core-regional-subdivision-codes -CodeSystem: EHMISORMunicipalityType -Id: ehmi-sor-municipality-type -Title: "EHMI SOR Municipality Types CS" -Description: "ehmi-sor-Municipality-type for the EHMI Messaging Infrastructure" +CodeSystem: EerSorMunicipalityType +Id: eer-sor-municipality-type +Title: "EER SOR Municipality Types CS" +Description: "eer-sor-Municipality-type for the EHMI Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" @@ -134,10 +134,10 @@ Description: "ehmi-sor-Municipality-type for the EHMI Messaging Infrastructure" * #0851 "Aalborg" * #0860 "Hjørring" -ValueSet: EHMISORMunicipalityTypeVS -Id: ehmi-sor-municipality-type-valueset -Title: "EHMI SOR Municipality Types Valueset" -Description: "ValueSet containing codes for EHMI ehmi-sor-Municipality-type for the EHMI Messaging Infrastructure" +ValueSet: EerSorMunicipalityTypeVS +Id: eer-sor-municipality-type-valueset +Title: "EER SOR Municipality Types Valueset" +Description: "ValueSet containing codes for EHMI eer-sor-Municipality-type for the EHMI Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" diff --git a/input/fsh/ehmiMscdValueSets.fsh b/input/fsh/eerValueSets.fsh similarity index 66% rename from input/fsh/ehmiMscdValueSets.fsh rename to input/fsh/eerValueSets.fsh index b86b9c2..a077c87 100644 --- a/input/fsh/ehmiMscdValueSets.fsh +++ b/input/fsh/eerValueSets.fsh @@ -1,7 +1,7 @@ -CodeSystem: EHMISOROrganizationIdentierType -Id: ehmi-sor-organization-identier-type -Title: "EHMI SOR Organization Identier Type CodeSystem" -Description: "CodeSystem containing codes for EHMI SOR Organization Identier Type" +CodeSystem: EerSorOrganizationIdentierType +Id: eer-sor-organization-identier-type +Title: "EER SOR Organization Identier Type CodeSystem" +Description: "CodeSystem containing codes for EER SOR Organization Identier Type" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" @@ -13,47 +13,47 @@ Description: "CodeSystem containing codes for EHMI SOR Organization Identier Typ * #RegionCode "Region Code" "Regionskode" //* include codes from system http://hl7.org/fhir/ValueSet/identifier-type -ValueSet: EHMISORorganizationIdentierTypeVS -Id: ehmi-sor-organization-identier-type-valueset -Title: "EHMI SOR Organization Identier Type Valueset" +ValueSet: EerSorOrganizationIdentierTypeVS +Id: eer-sor-organization-identier-type-valueset +Title: "EER SOR Organization Identier Type Valueset" Description: "ValueSet containing codes for SOR Organization Identier Type" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true -* include codes from system ehmi-sor-organization-identier-type +* include codes from system eer-sor-organization-identier-type -CodeSystem: EHMIEndpointConnectionType -Id: ehmi-connection-type -Title: "EHMI Connection Types CS" -Description: "ehmi-connection-types for the EHMI Messaging Infrastructure" +CodeSystem: EerEndpointConnectionType +Id: eer-endpoint-connection-type +Title: "EER Connection Types CS" +Description: "eer-endpoint-connection-types for the EER Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true * ^caseSensitive = true -* #EHMIeDeliveryMessaging "EHMI messaging via eDelivery" +* #EerMessagingEdelivery "EHMI messaging via eDelivery" * #vansMessaging "EHMI VANS messaging" * #hl7-fhir-msg "hl7-fhir-msg" * #hl7-fhir-rest "hl7-fhir-rest" * #ihe-xds "ihe-xds - Cross-domain Document Sharing" -ValueSet: EHMIEndpointConnectionTypeVS -Id: ehmi-connection-type-valueset -Title: "EHMI connection Types Valueset" -Description: "ValueSet containing codes for EHMI connectionTypes" +ValueSet: EerEndpointConnectionTypeVS +Id: eer-endpoint-connection-type-valueset +Title: "EER connection Types Valueset" +Description: "ValueSet containing codes for EER connectionTypes" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true -* include codes from system ehmi-connection-type +* include codes from system eer-endpoint-connection-type //* include #hl7-fhir-msg from system $mCSDEndpointConnectionType //* include #hl7-fhir-rest from system $mCSDEndpointConnectionType //* include #ihe-xds from system $mCSDEndpointConnectionType -CodeSystem: EHMIEndpointPayloadType +CodeSystem: EerEndpointPayloadType Id: ehmi-payload-type -Title: "EHMI Payload Types CS" +Title: "EER Payload Types CS" Description: "ehmi-payload-types for the EHMI Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active @@ -71,20 +71,20 @@ Description: "ehmi-payload-types for the EHMI Messaging Infrastructure" * #urn:dk:medcom:prod:messaging:sbdhack "MedCom SBDH Ack message as a production message" * #urn:dk:medcom:test:messaging:sbdhack "MedCom SBDH Ack message as a test message" -ValueSet: EHMIEndpointPayloadTypeVS +ValueSet: EerEndpointPayloadTypeVS Id: ehmi-payload-type-valueset -Title: "EHMI payload Types Valueset" -Description: "ValueSet containing codes for EHMI payloadTypes" +Title: "EER payload Types Valueset" +Description: "ValueSet containing codes for EER payloadTypes" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true * include codes from system ehmi-payload-type -CodeSystem: EHMISOROrganization -Id: ehmi-sor-organization-type -Title: "EHMI SOR Organization Types CS" -Description: "ehmi-sor-organization-type for the EHMI Messaging Infrastructure" +CodeSystem: EerSorOrganization +Id: eer-sor-organization-type +Title: "EER SOR Organization Types CS" +Description: "eer-sor-organization-type for the EHMI Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" @@ -97,15 +97,15 @@ Description: "ehmi-sor-organization-type for the EHMI Messaging Infrastructure" * #SI "SOR Organization - Healthcare Institution HI" * #OE "SOR Organization - Organizational Unit OU" -ValueSet: EHMISOROrganizationVS -Id: ehmi-sor-organization-type-valueset -Title: "EHMI SOR Organization Types Valueset" -Description: "ValueSet containing codes for EHMI ehmi-sor-organization-type" +ValueSet: EerSorOrganizationVS +Id: eer-sor-organization-type-valueset +Title: "EER SOR Organization Types Valueset" +Description: "ValueSet containing codes for EER eer-sor-organization-type" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true -* ^compose.include[+].system = $EHMISOROrganizationType +* ^compose.include[+].system = $EerSorOrganizationType * ^compose.include[=].concept[+].code = #IO * ^compose.include[=].concept[=].display = "Institution Owner" * ^compose.include[=].concept[=].designation[+].language = #da @@ -130,12 +130,12 @@ Description: "ValueSet containing codes for EHMI ehmi-sor-organization-type" * ^compose.include[=].concept[=].display = "Organizational Unit" * ^compose.include[=].concept[=].designation[+].language = #da * ^compose.include[=].concept[=].designation[=].value = "Organisatorisk enhed" -//* include codes from system ehmi-sor-organization-type +//* include codes from system eer-sor-organization-type -CodeSystem: EHMISORNetOperator -Id: ehmi-sor-net-operator-type -Title: "EHMI SOR Netoperator Types CS" -Description: "ehmi-sor-net-operator-type for the EHMI Messaging Infrastructure" +CodeSystem: EerSorNetOperator +Id: eer-sor-net-operator-type +Title: "EER SOR Netoperator Types CS" +Description: "eer-sor-net-operator-type for the EHMI Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" @@ -149,18 +149,18 @@ Description: "ehmi-sor-net-operator-type for the EHMI Messaging Infrastructure" * #11000035002 "Ukendt" * #71000035005 "Vejle Amt" -ValueSet: EHMISORNetOperatorVS -Id: ehmi-sor-net-operator-type-valueset -Title: "EHMI SOR Netoperator Types Valueset" -Description: "ehmi-sor-net-operator-type for the EHMI Messaging Infrastructure" +ValueSet: EerSorNetOperatorVS +Id: eer-sor-net-operator-type-valueset +Title: "EER SOR Netoperator Types Valueset" +Description: "eer-sor-net-operator-type for the EHMI Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true -* include codes from system ehmi-sor-net-operator-type +* include codes from system eer-sor-net-operator-type CodeSystem: EHMIMedComMessageDefinitionType -Id: ehmi-medcom-message-definition-type +Id: eer-medcom-message-definition-type Title: "EHMIMedComMessageDefinitionType CodeSystem" Description: "EHMIMedComMessageDefinitionTypeCS for the EHMI Messaging Infrastructure" * ^version = "1.0.0" @@ -174,17 +174,17 @@ Description: "EHMIMedComMessageDefinitionTypeCS for the EHMI Messaging Infrastru * #ENVELOPE "Envelope" ValueSet: EHMIMedComMessageDefinitionTypeVS -Id: ehmi-medcom-message-definition-type-valueset +Id: eer-medcom-message-definition-type-valueset Title: "EHMIMedComMessageDefinitionType Valueset" Description: "EHMIMedComMessageDefinitionTypeVS for the EHMI Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true -* include codes from system ehmi-medcom-message-definition-type +* include codes from system eer-medcom-message-definition-type CodeSystem: EerMessageDefinitionIdentifierSystem -Id: ehmi-messagedefinition-identifer-system +Id: eer-messagedefinition-identifer-system Title: "EerMessageDefinitionIdentifierSystem CodeSystem" Description: "EerMessageDefinitionIdentifierSystemCS for the EHMI Messaging Infrastructure" * ^version = "1.0.0" @@ -198,17 +198,17 @@ Description: "EerMessageDefinitionIdentifierSystemCS for the EHMI Messaging Infr * #urn:dk:healthcare:medcom:messaging:envelope "urn:dk:healthcare:medcom:messaging:envelope" ValueSet: EerMessageDefinitionIdentifierSystemVS -Id: ehmi-messagedefinition-identifer-system-valueset +Id: eer-messagedefinition-identifer-system-valueset Title: "EerMessageDefinitionIdentifierSystem Valueset" Description: "EerMessageDefinitionIdentifierSystemVS for the EHMI Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true -* include codes from system ehmi-messagedefinition-identifer-system +* include codes from system eer-messagedefinition-identifer-system ValueSet: EHMIUseContextCodeSystemVS -Id: ehmi-messagedefinition-use-context-code-valueset +Id: eer-messagedefinition-use-context-code-valueset Title: "EHMIUseContextCodeSystem Valueset" Description: "EHMIUseContextCodeSystemVS for the EHMI Messaging Infrastructure" * ^version = "1.0.0" @@ -217,10 +217,10 @@ Description: "EHMIUseContextCodeSystemVS for the EHMI Messaging Infrastructure" * ^experimental = true * include codes from system http://terminology.hl7.org/CodeSystem/usage-context-type -CodeSystem: EHMISORIOOrganization -Id: ehmi-sor-io-organization-type -Title: "EHMI SOR Organization Types CS" -Description: "ehmi-sor-organization-type for the EHMI Messaging Infrastructure" +CodeSystem: EerSorIOOrganization +Id: eer-sor-io-organization-type +Title: "EER SOR Organization Types CS" +Description: "eer-sor-organization-type for the EHMI Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" @@ -231,20 +231,20 @@ Description: "ehmi-sor-organization-type for the EHMI Messaging Infrastructure" * #Region "SOR Region Organization - Institution Owner IO (DK:IE)" * #Generic "General encompassing the principle" -ValueSet: EHMISORIOOrganizationVS -Id: ehmi-sor-io-organization-type-valueset -Title: "EHMI SOR IO Organization Types Valueset" -Description: "ValueSet containing codes for EHMI ehmi-sor-io-organization-type" +ValueSet: EerSorIOOrganizationVS +Id: eer-sor-io-organization-type-valueset +Title: "EER SOR IO Organization Types Valueset" +Description: "ValueSet containing codes for EER eer-sor-io-organization-type" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true -* include codes from system ehmi-sor-io-organization-type +* include codes from system eer-sor-io-organization-type -CodeSystem: EHMISORUnitType -Id: ehmi-sor-unit-type -Title: "EHMI SOR Unit Types CS" -Description: "ehmi-sor-unit-type for the EHMI Messaging Infrastructure" +CodeSystem: EerSorUnitType +Id: eer-sor-unit-type +Title: "EER SOR Unit Types CS" +Description: "eer-sor-unit-type for the EER Messaging Infrastructure" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" @@ -271,20 +271,20 @@ Description: "ehmi-sor-unit-type for the EHMI Messaging Infrastructure" * #sygeplejeklinik "Sygeplejeklinik" * #behandlingscenter-for-stofmisbrugere "Behandlingscenter for stofmisbrugere" -ValueSet: EHMISORUnitTypeVS -Id: ehmi-sor-unit-type-valueset -Title: "EHMI SOR Unit Types Valueset" -Description: "ValueSet containing codes for EHMI ehmi-sor-io-organization-type" +ValueSet: EerSorUnitTypeVS +Id: eer-sor-unit-type-valueset +Title: "EER SOR Unit Types Valueset" +Description: "ValueSet containing codes for EER eer-sor-io-organization-type" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true -* include codes from system ehmi-sor-unit-type +* include codes from system eer-sor-unit-type -CodeSystem: EHMISORClinicalAdministrativeHierarchy -Id: ehmi-sor-clinical-administrative-hierarchy -Title: "EHMI SOR Clinical Administrative Hierarchy CS" -Description: "CodeSystem containing codes for EHMI SOR Clinical Administrative Hierarchy" +CodeSystem: EerSorClinicalAdministrativeHierarchy +Id: eer-sor-clinical-administrative-hierarchy +Title: "EER SOR Clinical Administrative Hierarchy CS" +Description: "CodeSystem containing codes for EER SOR Clinical Administrative Hierarchy" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" @@ -297,12 +297,33 @@ Description: "CodeSystem containing codes for EHMI SOR Clinical Administrative H * #Afdeling "Afdeling" * #Afsnit "Afsnit" -ValueSet: EHMISORClinicalAdministrativeHierarchyVS -Id: ehmi-sor-clinical-administrative-hierarchy-valueset -Title: "EHMI SOR Clinical Administrative Hierarchy Valueset" -Description: "ValueSet containing codes for EHMI SOR Clinical Administrative Hierarchy" +ValueSet: EerSorClinicalAdministrativeHierarchyVS +Id: eer-sor-clinical-administrative-hierarchy-valueset +Title: "EER SOR Clinical Administrative Hierarchy Valueset" +Description: "ValueSet containing codes for EER SOR Clinical Administrative Hierarchy" * ^version = "1.0.0" * ^status = #active * ^date = "2023-09-01" * ^experimental = true -* include codes from system ehmi-sor-clinical-administrative-hierarchy +* include codes from system eer-sor-clinical-administrative-hierarchy + +CodeSystem: EerDigitalSignatureType +Id: eer-digital-signature-type +Title: "EER digital-signature Types CS" +Description: "eer-digital-signature-types for the EER Messaging Infrastructure" +* ^version = "1.0.0" +* ^status = #active +* ^date = "2024-09-01" +* ^experimental = true +* ^caseSensitive = true +* #ETSI "Digital Signature" + +ValueSet: EerDigitalSignatureTypeVS +Id: eer-digital-signature-type-valueset +Title: "EER digital-signature Types VS" +Description: "eer-digital-signature-types for the EER Messaging Infrastructure" +* ^version = "1.0.0" +* ^status = #active +* ^date = "2024-09-01" +* ^experimental = true +* include codes from system $EerDigSigCS diff --git a/input/fsh/ehmiAliases.fsh b/input/fsh/ehmiAliases.fsh deleted file mode 100644 index f86efca..0000000 --- a/input/fsh/ehmiAliases.fsh +++ /dev/null @@ -1,78 +0,0 @@ -Alias: $EHMIAuditEventTypes = http://medcomehmi.dk/ig/ehmi_balp/CodeSystem/ehmi-auditevent-types -Alias: $EHMIAuditEventSubTypes = http://medcomehmi.dk/ig/ehmi_balp/CodeSystem/ehmi-auditevent-sub-types -Alias: $EHMIAuditEventSubTypesValueset = http://medcomehmi.dk/ig/ehmi_balp/CodeSystem/ehmi-auditevent-sub-types -Alias: $EHMIAuditEventOutcome = http://hl7.org/fhir/audit-event-outcome -Alias: $EHMIAuditEventSourceType = http://medcomehmi.dk/ig/ehmi_balp/CodeSystem/ehmi-auditevent-source-type -Alias: $EHMIAuditEventParticipationRoleType = http://medcomehmi.dk/ig/ehmi_balp/CodeSystem/ehmi-auditevent-participationroletype -Alias: $EHMIAuditEventAgentWhoIdentifierTypes = http://medcomehmi.dk/ig/ehmi_balp/CodeSystem/ehmi-auditevent-agent-who-identifier-types -Alias: $EHMIAuditEventEntityType = http://medcomehmi.dk/ig/ehmi_balp/CodeSystem/ehmi-auditevent-entity-type -Alias: $EHMIAuditEventEntityDetailType = http://medcomehmi.dk/ig/ehmi_balp/CodeSystem/ehmi-auditevent-entity-detail-type -Alias: $EHMIAuditEventValueSet = http://medcomfhir.dk/fhir/ehmi/CodeSystem/EHMIAuditEventValueSet -Alias: $AuditEventAgentNetworkType = http://hl7.org/fhir/R4/valueset-network-type.html -Alias: $AuditEventEntityType = http://hl7.org/fhir/R4/valueset-audit-entity-type.html -Alias: $AuditEventAgentWhoTypes = http://hl7.org/fhir/R4/valueset-participation-role-type.html -Alias: $AuditEventSubTypes = http://hl7.org/fhir/restful-interaction -Alias: $AuditEventSubTypesValueset = http://hl7.org/fhir/R4/valueset-audit-event-sub-type.html -Alias: $AuditEventTypes = http://terminology.hl7.org/CodeSystem/audit-event-type -Alias: $AuditEventTypes2 = http://dicom.nema.org/resources/ontology/DCM -Alias: $EHMIAuditEventEntityMessageType = http://medcomehmi.dk/ig/ehmi_balp/CodeSystem/ehmi-auditevent-entity-message-type - -Alias: $mCSDEndpointConnectionType = http://hl7.org/fhir/R4/valueset-endpoint-connection-type.html - - -Alias: $EHMISORorganizationIdentierType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-sor-organization-identier-type -Alias: $EHMISORorganizationIdentierTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-sor-organization-identier-type-valueset - -Alias: $EerMessageDefinitionIdentifierSystem = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-messagedefinition-identifier-system -Alias: $EerMessageDefinitionIdentifierSystemVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-messagedefinition-identifier-system-valueset - -Alias: $EHMIEndpointConnectionType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-connection-type -Alias: $EHMIEndpointConnectionTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-connection-type-valueset - -Alias: $EHMIEndpointPayloadType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-payload-type -Alias: $EHMIEndpointPayloadTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-payload-type-valueset - -Alias: $EHMISOROrganizationType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-sor-organization-type -Alias: $EHMISOROrganizationTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-sor-organization-type-valueset - -Alias: $EHMISORIOOrganizationType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-sor-io-organization-type -Alias: $EHMISORIOOrganizationTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-sor-io-organization-type-valueset - -Alias: $MedComMessageDefinitionUri = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-medcom-message-definition-uri -Alias: $MedComMessageDefinitionUriVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-medcom-message-definition-uri-valueset - -Alias: $EHMIMedComMessageDefinitionType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-medcom-message-definition-type -Alias: $EHMIMedComMessageDefinitionTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-medcom-message-definition-type-valueset - -Alias: $EHMISORUnitType = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-sor-unit-type -Alias: $EHMISORUnitTypeVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-sor-unit-type-valueset - -Alias: $EHMISORClinicalAdministrativeHierarchy = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-sor-clinical-administrative-hierarchy -Alias: $EHMISORClinicalAdministrativeHierarchyVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-sor-clinical-administrative-hierarchy-valueset - -//Alias: $EHMISORMunicipalityCode = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/ehmi-sor-municipality-type -Alias: $EHMISORMunicipalityCode = http://hl7.dk/fhir/core/CodeSystem/dk-core-municipality-codes -Alias: $EHMISORMunicipalityCodeVS = http://hl7.dk/fhir/core/ValueSet/dk-core-MunicipalityCodes - -Alias: $EHMISORRegionalCode = http://hl7.dk/fhir/core/CodeSystem/dk-core-regional-subdivision-codes -Alias: $EHMISORRegionalCodeVS = http://hl7.dk/fhir/core/ValueSet/dk-core-RegionalSubDivisionCodes - -Alias: $MessageEvents = http://medcomfhir.dk/ig/terminology/CodeSystem/medcom-messaging-eventCodes - -Alias: $EHMIUsageContextCodeSystem = http://terminology.hl7.org/CodeSystem/usage-context-type -Alias: $EHMIUsageContextCodeSystemVS = http://medcomehmi.dk/ig/dk-ehmi-eer/ValueSet/ehmi-messagedefinition-use-context-code-valueset -/* -Alias: $StatusCodes = http://hl7.org/fhir/encounter-status -Alias: $ActCodes = http://terminology.hl7.org/CodeSystem/v3-ActCode -Alias: $EventStatus = http://hl7.org/fhir/event-status -Alias: $CategoryCodes = http://medcomfhir.dk/fhir/carecommunication/CodeSystem/medcom-careCommunication-categoryCodes -Alias: $ServerityCode = http://hl7.org/fhir/issue-severity -Alias: $CodeCode = http://hl7.org/fhir/issue-type -Alias: $AcknowledgementCode = http://hl7.org/fhir/ValueSet/Acknowledgement-code -Alias: $BundleType = http://hl7.org/fhir/bundle-type -Alias: $Use = http://medcomfhir.dk/fhir/messaging/CodeSystem/medcom-messaging-destinationUse -Alias: $MessageEvents = http://medcomfhir.dk/fhir/messaging/CodeSystem/medcom-messaging-eventCodes -Alias: $SORCode = urn:oid:1.2.208.176.1.1 -Alias: $EANCode = urn:oid:1.3.88 -Alias: $activityCodes = http://medcomfhir.dk/fhir/messaging/CodeSystem/medcom-messaging-activityCodes -*/ \ No newline at end of file diff --git a/input/fsh/ehmiDevice.fsh b/input/fsh/ehmiDevice.fsh deleted file mode 100644 index 1847486..0000000 --- a/input/fsh/ehmiDevice.fsh +++ /dev/null @@ -1,15 +0,0 @@ -Profile: EerDevice -Parent: Device -Description: "An EHMI profile of the Device resource." - -Profile: EerDeviceAP -Parent: EerDevice -Description: "An EerDeviceAP profile of the EerDevice resource." - -Profile: EerDeviceMSH -Parent: EerDevice -Description: "An EerDeviceMSH profile of the EerDevice resource." - -Profile: EerDeviceEUA -Parent: EerDevice -Description: "An EerDeviceEUA profile of the EerDevice resource." diff --git a/input/fsh/ehmiMessageDefinition-edi.fsh b/input/fsh/ehmiMessageDefinition-edi.fsh deleted file mode 100644 index ffe9688..0000000 --- a/input/fsh/ehmiMessageDefinition-edi.fsh +++ /dev/null @@ -1,9 +0,0 @@ -Profile: EerMessageDefinitionEdi -Parent: EerMessageDefinition -Description: "An example profile of the MessageDefinition-edi resource." -//* id = -* identifier.system = $EerMessageDefinitionIdentifierSystem#urn:dk:healthcare:medcom:messaging:edifact -* identifier.type = $EHMIMedComMessageDefinitionType#EDIFACT -* useContext.code.system = $EHMIUsageContextCodeSystem (exactly) -* responseRequired = #on-error - diff --git a/input/fsh/ehmiMessageDefinition-oioxml.fsh b/input/fsh/ehmiMessageDefinition-oioxml.fsh deleted file mode 100644 index 4163cac..0000000 --- a/input/fsh/ehmiMessageDefinition-oioxml.fsh +++ /dev/null @@ -1,9 +0,0 @@ -Profile: EerMessageDefinitionOioxml -Parent: EerMessageDefinition -Description: "An example profile of the MessageDefinition-oioxml resource." -* identifier.system = $EerMessageDefinitionIdentifierSystem#urn:dk:healthcare:medcom:messaging:oioxml (exactly) -* identifier.type = $EHMIMedComMessageDefinitionType#OIOXML (exactly) -* useContext.code = $EHMIUsageContextCodeSystem#workflow (exactly) -* useContext.code.system = $EHMIUsageContextCodeSystem (exactly) -* responseRequired = #on-error - diff --git a/input/fsh/ehmiMessagingEndpoint.fsh b/input/fsh/ehmiMessagingEndpoint.fsh deleted file mode 100644 index 07ce4cf..0000000 --- a/input/fsh/ehmiMessagingEndpoint.fsh +++ /dev/null @@ -1,106 +0,0 @@ -Profile: EHMIMessagingEndpoint -Parent: MCSDEndpoint -Id: ehmi.dk.messaging -Title: "EHMI Endpoint - General for Messaging" -Description: """ -A profile on the mCSD Endpoint. - -An Organization may be reachable through electronic Endpoint(s). -An Endpoint may be a eDelivery receiver or a vans receiver (or in the future a FHIR server, an IHE web services actor, or some other -mechanism). -""" -* identifier 1..1 MS SU -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.code = #official -* identifier.value 1..1 MS SU -* connectionType from ehmi-connection-type-valueset -* period 1..1 MS SU -* payloadType from ehmi-medcom-message-definition-uri-valueset -* payloadType 1..* MS SU -* payloadMimeType 1..1 MS SU -* extension contains ehmi-core-system-extension named system 0..* MS -* extension contains ehmi-dk-core-network-supply-system-extension named networkSupplySystem 0..* MS - -Profile: EHMIeDeliveryMessagingEndpoint -Parent: EHMIMessagingEndpoint -Id: ehmi.dk.messaging.edelivery -Title: "EHMI Endpoint eDelivery Messaging" -Description: "EHMI Endpoint eDelivery Messaging" -* connectionType = $EHMIEndpointConnectionType#EHMIeDeliveryMessaging (exactly) - -Profile: EHMIeDeliveryMessagingFhirEndpoint -Parent: EHMIeDeliveryMessagingEndpoint -Id: ehmi.dk.messaging.edelivery.fhir -Title: "EHMI Endpoint eDelivery FHIR Messaging" -Description: "EHMI Endpoint eDelivery FHIR Messaging" -//* payloadType = $EHMIEndpointPayloadType#urn:dk:medcom:prod:messaging:fhir (exactly) -//* payloadType = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 - -Profile: EHMIeDeliveryMessagingEdiEndpoint -Parent: EHMIeDeliveryMessagingEndpoint -Id: ehmi.dk.messaging.edelivery.edi -Title: "EHMI Endpoint eDelivery EDI Messaging" -Description: "EHMI Endpoint eDelivery EDI Messaging" -//* payloadType = $EHMIEndpointPayloadType#urn:dk:medcom:prod:messaging:edi (exactly) -//* payloadType.coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q -//* payloadType[0].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q -//* payloadType[+].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q -//* payloadType[+].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q - -Profile: EHMIeDeliveryMessagingOioxmlEndpoint -Parent: EHMIeDeliveryMessagingEndpoint -Id: ehmi.dk.messaging.edelivery.oioxml -Title: "EHMI Endpoint eDelivery Oioxml Messaging" -Description: "EHMI Endpoint eDelivery Oioxml Messaging" -//* payloadType = $EHMIEndpointPayloadType#urn:dk:medcom:prod:messaging:oioxml (exactly) -//* payloadType.coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -//* payloadType[0].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -//* payloadType[+].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" -//* payloadType[+].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" - -Profile: EHMIMessagingVansEndpoint -Parent: EHMIMessagingEndpoint -Id: ehmi.dk.messaging.vans -Title: "EHMI Endpoint VANS Messaging" -Description: "EHMI Endpoint VANS Messaging" -* connectionType = $EHMIEndpointConnectionType#vansMessaging (exactly) - -Profile: EHMIMessagingVansFhirEndpoint -Parent: EHMIMessagingVansEndpoint -Id: ehmi.dk.messaging.vans.fhir -Title: "EHMI Endpoint VANS FHIR Messaging" -Description: "EHMI Endpoint VANS FHIR Messaging" -//* payloadType = $EHMIEndpointPayloadType#urn:dk:medcom:prod:messaging:fhir (exactly) -//* payloadType = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 - -Profile: EHMIMessagingVansEdiEndpoint -Parent: EHMIMessagingVansEndpoint -Id: ehmi.dk.messaging.vans.edi -Title: "EHMI Endpoint VANS EDI Messaging" -Description: "EHMI Endpoint VANS EDI Messaging" -//* payloadType = $EHMIEndpointPayloadType#urn:dk:medcom:prod:messaging:edi (exactly) -//* payloadType.coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q -//* payloadType[0].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q -//* payloadType[+].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q -//* payloadType[+].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q - -Profile: EHMIMessagingVansOioxmlEndpoint -Parent: EHMIMessagingVansEndpoint -Id: ehmi.dk.messaging.vans.oioxml -Title: "EHMI Endpoint VANS Oioxml Messaging" -Description: "EHMI Endpoint VANS Oioxml Messaging" -//* payloadType = $EHMIEndpointPayloadType#urn:dk:medcom:prod:messaging:oioxml (exactly) -//* payloadType.coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -//* payloadType[0].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -//* payloadType[+].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" -//* payloadType[+].coding.code = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" - -/* -Profile: SOREndpointDocShare -Parent: MCSDEndpointDocShare -Id: medcom.ehmi.dk.mcsd.DocShare -Title: "MedCom SOR DocShare Endpoint" -Description: """ SOR """ - -*/ \ No newline at end of file diff --git a/input/fsh/instances/DeviceDefinitions/EHMIDeviceDefinitions-LPS.fsh b/input/fsh/instances/DeviceDefinitions/EHMIDeviceDefinitions-LPS.fsh deleted file mode 100644 index 6a7efad..0000000 --- a/input/fsh/instances/DeviceDefinitions/EHMIDeviceDefinitions-LPS.fsh +++ /dev/null @@ -1,12 +0,0 @@ -Instance: eerDeviceDefinition-LPS.Novax -InstanceOf: EerDeviceDefinitionLPS -Description: "An example of an EerDeviceDefinition-LPS for eerDeviceDefinition-LPS.Novax" -* identifier.value = "eerDeviceDefinition.LPS.Novax" -//* identifier.value -* manufacturerString = "Novax" -// * manufacturerReference -* deviceName.name = "Novax LPS" -* deviceName.type = http://hl7.org/fhir/device-nametype#manufacturer-name "Manufacturer name" -//* type = http://medcomehmi.dk/ig/dk-ehmi-eer/CodeSystem/eer-device-type#LPS "General Practitioner System" -* specialization.systemType = "LPS Standards" - diff --git a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_VansEdi.fsh b/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_VansEdi.fsh deleted file mode 100644 index 77bcd38..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_VansEdi.fsh +++ /dev/null @@ -1,19 +0,0 @@ -/* -Instance: EHMIMessagingEndpoint-Herlev-VansEdi.5790002508226 -InstanceOf: EHMIMessagingVansEdiEndpoint -Description: "Herlev EHMIMessagingVansEdiEndpoint." -* id = "EHMIMessagingEndpoint-Herlev-VansEdi.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-Herlev-Kommune-SOR.101000016005) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://herlev.dk/edi" -* payloadMimeType = #text/plain -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q -*/ \ No newline at end of file diff --git a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_VansFhir.fsh b/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_VansFhir.fsh deleted file mode 100644 index ca22e4f..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_VansFhir.fsh +++ /dev/null @@ -1,17 +0,0 @@ -/* -Instance: EHMIMessagingEndpoint-Herlev-VansFhir.5790002508226 -InstanceOf: EHMIMessagingVansFhirEndpoint -Description: "Herlev EHMIMessagingEndpoint-Herlev-VansFhir.01." -* id = "EHMIMessagingEndpoint-Herlev-VansFhir.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-Herlev-Kommune-SOR.101000016005) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://herlev.dk/fhir" -* payloadMimeType = #text/plain -* payloadType = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 -*/ \ No newline at end of file diff --git a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_VansOioxml.fsh b/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_VansOioxml.fsh deleted file mode 100644 index 575d59f..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_VansOioxml.fsh +++ /dev/null @@ -1,19 +0,0 @@ -/* -Instance: EHMIMessagingEndpoint-Herlev-VansOioxml.5790002508226 -InstanceOf: EHMIMessagingVansOioxmlEndpoint -Description: "Herlev EHMIMessagingVansOioxmlEndpoint." -* id = "EHMIMessagingEndpoint-Herlev-VansOioxml.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-Herlev-Kommune-SOR.101000016005) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://www.xyz.dk/oioxml" -* payloadMimeType = #text/plain -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" -*/ \ No newline at end of file diff --git a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_eDeliveryEdi.fsh b/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_eDeliveryEdi.fsh deleted file mode 100644 index 41075c7..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_eDeliveryEdi.fsh +++ /dev/null @@ -1,19 +0,0 @@ -/* -Instance: EHMIMessagingEndpoint-Herlev-eDeliveryEdi.01 -InstanceOf: EHMIeDeliveryMessagingEdiEndpoint -Description: "Herlev EHMIeDeliveryMessagingEdiEndpoint." -* id = "EHMIMessagingEndpoint-Herlev-eDeliveryEdi.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-Herlev-Kommune-SOR.101000016005) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://herlev.dk/edi" -* payloadMimeType = #text/plain -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q -*/ \ No newline at end of file diff --git a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_eDeliveryFhir.fsh b/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_eDeliveryFhir.fsh deleted file mode 100644 index ace8fa6..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_eDeliveryFhir.fsh +++ /dev/null @@ -1,17 +0,0 @@ -/* -Instance: EHMIMessagingEndpoint-Herlev-eDeliveryFhir.5790002508226 -InstanceOf: EHMIeDeliveryMessagingFhirEndpoint -Description: "Herlev EHMIeDeliveryMessagingFhirEndpoint." -* id = "EHMIMessagingEndpoint-Herlev-eDeliveryFhir.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-Herlev-Kommune-SOR.101000016005) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://herlev.dk/fhir" -* payloadMimeType = #text/plain -* payloadType = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 -*/ \ No newline at end of file diff --git a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_eDeliveryOioxml.fsh b/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_eDeliveryOioxml.fsh deleted file mode 100644 index a02c01b..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEP_Herlev_eDeliveryOioxml.fsh +++ /dev/null @@ -1,18 +0,0 @@ -/* -Instance: EHMIMessagingEndpoint-Herlev-eDeliveryOioxml.5790002508226 -InstanceOf: EHMIeDeliveryMessagingOioxmlEndpoint -Description: "Herlev EHMIeDeliveryMessagingOioxmlEndpoint." -* id = "EHMIMessagingEndpoint-Herlev-eDeliveryOioxml.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-Herlev-Kommune-SOR.101000016005) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://herlev.dk/oioxml" -* payloadMimeType = #text/plain -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" -*/ \ No newline at end of file diff --git a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_VansEdi.05.fsh b/input/fsh/instances/Endpoints/EHMIMsgEndpoint_VansEdi.05.fsh deleted file mode 100644 index 8125d16..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_VansEdi.05.fsh +++ /dev/null @@ -1,15 +0,0 @@ -Instance: EHMIMessagingEndpoint-VansEdi.01 -InstanceOf: EHMIMessagingVansEdiEndpoint -Description: "An example of an EHMIMessagingVansEdiEndpoint." -* id = "EHMIMessagingEndpoint-VansEdi.01" -* identifier.value = "EHMIMessagingEndpoint-VansEdi.01" -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI.01.1) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://www.xyz.dk/edi" -* payloadMimeType = #text/plain -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q diff --git a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_VansFhir.04.fsh b/input/fsh/instances/Endpoints/EHMIMsgEndpoint_VansFhir.04.fsh deleted file mode 100644 index 3e59825..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_VansFhir.04.fsh +++ /dev/null @@ -1,13 +0,0 @@ -Instance: EHMIMessagingEndpoint-VansFhir.01 -InstanceOf: EHMIMessagingVansFhirEndpoint -Description: "An example of an EHMIMessagingEndpoint-VansFhir.01." -* id = "EHMIMessagingEndpoint-VansFhir.01" -* identifier.value = "EHMIMessagingEndpoint-VansFhir.01" -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI.01.1) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://www.xyz.dk/fhir" -* payloadMimeType = #text/plain -* payloadType = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 diff --git a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_VansOioxml.06.fsh b/input/fsh/instances/Endpoints/EHMIMsgEndpoint_VansOioxml.06.fsh deleted file mode 100644 index 6430047..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_VansOioxml.06.fsh +++ /dev/null @@ -1,15 +0,0 @@ -Instance: EHMIMessagingEndpoint-VansOioxml.01 -InstanceOf: EHMIMessagingVansOioxmlEndpoint -Description: "An example of an EHMIMessagingVansOioxmlEndpoint." -* id = "EHMIMessagingEndpoint-VansOioxml.01" -* identifier.value = "EHMIMessagingEndpoint-VansOioxml.01" -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI.01.1) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://www.xyz.dk/oioxml" -* payloadMimeType = #text/plain -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" diff --git a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_eDeliveryEdi.02.fsh b/input/fsh/instances/Endpoints/EHMIMsgEndpoint_eDeliveryEdi.02.fsh deleted file mode 100644 index deaa29b..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_eDeliveryEdi.02.fsh +++ /dev/null @@ -1,15 +0,0 @@ -Instance: EHMIMessagingEndpoint-eDeliveryEdi.01 -InstanceOf: EHMIeDeliveryMessagingEdiEndpoint -Description: "An example of an EHMIeDeliveryMessagingEdiEndpoint." -* id = "EHMIMessagingEndpoint-eDeliveryEdi.01" -* identifier.value = "EHMIMessagingEndpoint-eDeliveryEdi.01" -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI.01.1) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://www.xyz.dk/edi" -* payloadMimeType = #text/plain -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q diff --git a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_eDeliveryFhir.01.fsh b/input/fsh/instances/Endpoints/EHMIMsgEndpoint_eDeliveryFhir.01.fsh deleted file mode 100644 index 8503586..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_eDeliveryFhir.01.fsh +++ /dev/null @@ -1,13 +0,0 @@ -Instance: EHMIMessagingEndpoint-eDeliveryFhir.01 -InstanceOf: EHMIeDeliveryMessagingFhirEndpoint -Description: "An example of an EHMIeDeliveryMessagingFhirEndpoint." -* id = "EHMIMessagingEndpoint-eDeliveryFhir.01" -* identifier.value = "EHMIMessagingEndpoint-eDeliveryFhir.01" -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI.01.1) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://www.xyz.dk/fhir" -* payloadMimeType = #text/plain -* payloadType = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 diff --git a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_eDeliveryOioxml.03.fsh b/input/fsh/instances/Endpoints/EHMIMsgEndpoint_eDeliveryOioxml.03.fsh deleted file mode 100644 index a61be49..0000000 --- a/input/fsh/instances/Endpoints/EHMIMsgEndpoint_eDeliveryOioxml.03.fsh +++ /dev/null @@ -1,15 +0,0 @@ -Instance: EHMIMessagingEndpoint-eDeliveryOioxml.01 -InstanceOf: EHMIeDeliveryMessagingOioxmlEndpoint -Description: "An example of an EHMIeDeliveryMessagingOioxmlEndpoint." -* id = "EHMIMessagingEndpoint-eDeliveryOioxml.01" -* identifier.value = "EHMIMessagingEndpoint-eDeliveryOioxml.01" -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI.01.1) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://www.xyz.dk/oioxml" -* payloadMimeType = #text/plain -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" diff --git a/input/fsh/instances/MessageDefinitions/edifact/edi-MessageDefinition.fsh b/input/fsh/instances/MessageDefinitions/edifact/edi-MessageDefinition.fsh deleted file mode 100644 index c1daf2f..0000000 --- a/input/fsh/instances/MessageDefinitions/edifact/edi-MessageDefinition.fsh +++ /dev/null @@ -1,34 +0,0 @@ -Instance: EHMI.edi.bin02.b0210x.MessageDefinition -InstanceOf: EerMessageDefinitionEdi -Description: "An example of an EerMessageDefinition for bin02:b0210x." -* id = "EHMI.edi.bin02.b0210x.MessageDefinition" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:medbin:bin02:b0210x -* identifier.system = $EerMessageDefinitionIdentifierSystem#urn:dk:healthcare:medcom:messaging:edifact -* identifier.period.start = "2012-07-01" -* identifier.type = $EHMIMedComMessageDefinitionType#EDIFACT -* identifier.use = #official -* identifier.value = "bin02:b0210x" -* version = "b0210x" -//* name = "Binary document transport for attachments to all referral types" -* title = "binary-document-transport-for-attachments-to-all-referral-types" -* status = #active -* date = "2020-06-26" -* copyright = "Copyright © 2022 MedCom" -//* publisher = "MedCom" -* contact[InteroperabilityConsultant].id = "InteroperabilityConsultant" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Michael Johansen" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "mjo@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* contact[SubjectMatterExpert].id = "SubjectMatterExpert" -* contact[SubjectMatterExpert].name = "Subject Matter Expert, Gitte Henriksen" -* contact[SubjectMatterExpert].telecom.system = #email -* contact[SubjectMatterExpert].telecom.value = "ghe@medcom.dk" -* contact[SubjectMatterExpert].telecom.use = #work -* description = "BIN01 bliver i dag brugt til mange forskellige formål, hvoraf kun en delmængde er i form af vedhæftelse af bilag til en henvisning. Derfor indføres en ny MEDBIN-standard, BIN02, som skal bruges til vedhæftelse af bilag i forbindelse med henvisninger (REF01, REF02 og REF06). Når VANS-leverandørerne møder en BIN02, skal de sørge for at route den til henvisningshotellet (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.code = #workflow -* useContext.valueCodeableConcept.text = "Regioner, Private parter i sundhedsvæsenet, Kommuner" -* purpose = "Denne standard anvendes, når man ønsker at sende en binær fil sammen med henvisningstyperne REF01, RFE02 og REF06 (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* copyright = "Copyright © 2022 MedCom" -* eventCoding = $MessageEvents#empty-message - diff --git a/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-Acknowledgement.fsh b/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-Acknowledgement.fsh deleted file mode 100644 index b0da294..0000000 --- a/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-Acknowledgement.fsh +++ /dev/null @@ -1,54 +0,0 @@ -Instance: Eer.fhir.MessageDefinition.Acknowledgement:2.0 -InstanceOf: EerMessageDefinitionFhir -Description: "An example of an EerMessageDefinition for Acknowledgement:2.0" -* id = "Eer.fhir.MessageDefinition.Acknowledgement.2.0" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 -* identifier.period.start = "2021-03-23" -//* identifier.period.end = "2023-01-05" -* identifier.use = #official -* identifier.value = "Acknowledgement.2.0" -* version = "2.0" -//* name = "Acknowledgement:2.0" -* title = "Acknowledgement 2.0" -* replaces.value = "Eer.fhir.MessageDefinition.Acknowledgement:1.0" -* status = #active -* date = "2022-10-05" -* copyright = "Copyright © 2022 MedCom" -//* publisher = "MedCom" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Thea Mentz Sørensen" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "tms@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* description = "DK: Kvitteringsmeddelelse (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "DK: Alle som kvittering på en fhir meddelelse (Hvem skal anvende standarden jf. §3,3 i bekendtgørelsen)" -* purpose = "DK: Sende kvittering på en fhir meddelelse (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* eventCoding = $MessageEvents#acknowledgement-message -* responseRequired = #never - -Instance: Eer.fhir.MessageDefinition.Acknowledgement:1.0 -InstanceOf: EerMessageDefinitionFhir -Description: "An example of an EerMessageDefinition for Acknowledgement:1.0" -* id = "Eer.fhir.MessageDefinition.Acknowledgement.1.0" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:1.0 -* identifier.period.start = "2021-03-23" -* identifier.period.end = "2022-10-04" -* identifier.use = #old -* identifier.value = "Acknowledgement.1.0" -* version = "1.0" -//* name = "Acknowledgement:1.0" -* title = "Acknowledgement 1.0" -* status = #retired -* date = "2021-03-23" -* copyright = "Copyright © 2021 MedCom" -//* publisher = "MedCom" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Thea Mentz Sørensen" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "tms@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* description = "DK: Kvitteringsmeddelelse (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "DK: Alle som kvittering på en fhir meddelelse (Hvem skal anvende standarden jf. §3,3 i bekendtgørelsen)" -* purpose = "DK: Sende kvittering på en fhir meddelelse (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* copyright = "Copyright © 2022 MedCom" -* eventCoding = $MessageEvents#acknowledgement-message -* responseRequired = #never - diff --git a/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-CareCommunication.fsh b/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-CareCommunication.fsh deleted file mode 100644 index ff77c2f..0000000 --- a/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-CareCommunication.fsh +++ /dev/null @@ -1,100 +0,0 @@ -Instance: Eer.fhir.MessageDefinition.CareCommunication:3.0 -InstanceOf: EerMessageDefinitionFhir -Description: "An example of an EerMessageDefinition for CareCommunication:3.0" -* id = "Eer.fhir.MessageDefinition.CareCommunication.3.0" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:carecommunication:3.0 -* identifier.period.start = "2021-03-23" -* identifier.use = #official -* identifier.value = "CareCommunication.3.0" -* version = "3.0" -//* name = "CareCommunication-3.0" -* title = "care-communication-3-0-0" -* replaces.value = "Eer.fhir.MessageDefinition.CareCommunication:2.0" -* status = #draft -* date = "2023-01-06" -* copyright = "Copyright © 2023 MedCom" -//* publisher = "MedCom" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Thea Mentz Sørensen" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "tms@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* contact[SubjectMatterExpert].name = "Subject Matter Expert, Kirsten Christiansen" -* contact[SubjectMatterExpert].telecom.system = #email -* contact[SubjectMatterExpert].telecom.value = "krc@medcom.dk" -* contact[SubjectMatterExpert].telecom.use = #work -* description = "DK: Korrespondancemeddelelse (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "DK: Regioner, kommuner, apoteker og primærsektoren. (Hvem skal anvende standarden jf. §3,3 i bekendtgørelsen)" -* purpose = "DK: Sende sundhedsinformation mellem sundhedsvæsnets parter, der ikke kan sendes med andre standarder (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* eventCoding = $MessageEvents#care-communication-message -* responseRequired = #always -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0" -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0.1" -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.CareCommunication:3.0" - -Instance: Eer.fhir.MessageDefinition.CareCommunication:2.0 -InstanceOf: EerMessageDefinitionFhir -Description: "An example of an EerMessageDefinition for CareCommunication:2.0" -* id = "Eer.fhir.MessageDefinition.CareCommunication.2.0" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:carecommunication:2.0 -* identifier.period.start = "2021-03-23" -* identifier.period.end = "2023-01-05" -* identifier.use = #old -* identifier.value = "CareCommunication.2.0" -* version = "2.0" -//* name = "CareCommunication-2.0" -* title = "care-communication-2-0-0" -* replaces.value = "Eer.fhir.MessageDefinition.CareCommunication:1.0" -* status = #retired -* date = "2022-10-05" -* copyright = "Copyright © 2022 MedCom" -//* publisher = "MedCom" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Thea Mentz Sørensen" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "tms@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* contact[SubjectMatterExpert].name = "Subject Matter Expert, Kirsten Christiansen" -* contact[SubjectMatterExpert].telecom.system = #email -* contact[SubjectMatterExpert].telecom.value = "krc@medcom.dk" -* contact[SubjectMatterExpert].telecom.use = #work -* description = "DK: Korrespondancemeddelelse (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "DK: Regioner, kommuner, apoteker og primærsektoren. (Hvem skal anvende standarden jf. §3,3 i bekendtgørelsen)" -* purpose = "DK: Sende sundhedsinformation mellem sundhedsvæsnets parter, der ikke kan sendes med andre standarder (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* eventCoding = $MessageEvents#care-communication-message -* responseRequired = #always -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0" -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0.1" -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.CareCommunication:3.0" - -Instance: Eer.fhir.MessageDefinition.CareCommunication:1.0 -InstanceOf: EerMessageDefinitionFhir -Description: "An example of an EerMessageDefinition for CareCommunication:1.0" -* id = "Eer.fhir.MessageDefinition.CareCommunication.1.0" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:carecommunication:1.0 -* identifier.period.start = "2021-03-23" -* identifier.period.end = "2022-10-04" -* identifier.use = #old -* identifier.value = "CareCommunication.1.0" -* version = "1.0" -//* name = "CareCommunication-1.0" -* title = "care-communication-1-0-0" -* status = #retired -* date = "2021-03-23" -* copyright = "Copyright © 2021 MedCom" -//* publisher = "MedCom" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Thea Mentz Sørensen" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "tms@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* contact[SubjectMatterExpert].name = "Subject Matter Expert, Kirsten Tapia Ravn Christiansen" -* contact[SubjectMatterExpert].telecom.system = #email -* contact[SubjectMatterExpert].telecom.value = "krc@medcom.dk" -* contact[SubjectMatterExpert].telecom.use = #work -* description = "DK: Korrespondancemeddelelse (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "DK: Regioner, kommuner, apoteker og primærsektoren. (Hvem skal anvende standarden jf. §3,3 i bekendtgørelsen)" -* purpose = "DK: Sende sundhedsinformation mellem sundhedsvæsnets parter, der ikke kan sendes med andre standarder (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* copyright = "Copyright © 2022 MedCom" -* eventCoding = $MessageEvents#care-communication-message -* responseRequired = #always -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0" -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.CareCommunication:3.0" - diff --git a/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-HomeCareObservation.fsh b/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-HomeCareObservation.fsh deleted file mode 100644 index 1a00cec..0000000 --- a/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-HomeCareObservation.fsh +++ /dev/null @@ -1,34 +0,0 @@ -Instance: Eer.fhir.MessageDefinition.HomeCareObservation:1.0 -InstanceOf: EerMsgDefHomeCareObservation -Description: "An example of an EerMessageDefinition for HomeCareObservation:1.0" -* id = "Eer.fhir.MessageDefinition.HomeCareObservation.1.0" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:homecareobservation:1.0 -* identifier.period.start = "2021-03-23" -* identifier.use = #official -* identifier.value = "HomeCareObservation.1.0" -* version = "1.0" -//* name = "HomeCareObservation:1.0" -* title = "HomeCareObservation 1.0" -//* replaces.value = "Eer.fhir.MessageDefinition.HomeCareObservation:2.0" -* status = #draft -* date = "2023-01-06" -* copyright = "Copyright © 2023 MedCom" -//* publisher = "MedCom" -//InteroperabilityConsultant -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Thea Mentz Sørensen" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "tms@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -//SubjectMatterExpert -* contact[SubjectMatterExpert].name = "Subject Matter Expert, Kirsten Christiansen" -* contact[SubjectMatterExpert].telecom.system = #email -* contact[SubjectMatterExpert].telecom.value = "krc@medcom.dk" -* contact[SubjectMatterExpert].telecom.use = #work -* description = "DK: HomeCareObservation (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "DK: kommuner og primærsektoren. (Hvem skal anvende standarden jf. §3,3 i bekendtgørelsen)" -* purpose = "DK: Sende sundhedsobservationer mellem kommuners akutsygepleje og en patients praktiserende læge (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* eventCoding = $MessageEvents#homecareobservation-message "HomeCare Observation Message" -* responseRequired = #always -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0" -* allowedResponse[+].message.value = "http://medcomfhir.dk/ig/acknowledgement/ImplementationGuide/medcom.fhir.dk.acknowledgement" -* allowedResponse[+].message.value = "http://medcomfhir.dk/ig/carecommunication/StructureDefinition/medcom-careCommunication-message" diff --git a/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-HospitalNotification.fsh b/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-HospitalNotification.fsh deleted file mode 100644 index fd145ad..0000000 --- a/input/fsh/instances/MessageDefinitions/fhir/ehmiMsgDef-HospitalNotification.fsh +++ /dev/null @@ -1,101 +0,0 @@ -Instance: Eer.fhir.MessageDefinition.hospitalNotification:3.0 -InstanceOf: EerMessageDefinitionFhir -Description: "An example of an EerMessageDefinition for hospitalnotification:3.0" -* id = "Eer.fhir.MessageDefinition.hospitalNotification.3.0" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:hospitalnotification:3.0 -* identifier.period.start = "2021-03-23" -* identifier.use = #official -* identifier.value = "hospitalnotification.3.0" -* version = "3.0.0" -//* name = "HospitalNotification:3.0" -* title = "HospitalNotification 3.0" -* replaces.value = "Eer.fhir.MessageDefinition.hospitalNotification:2.0" -* status = #draft -* date = "2023-01-06" -* copyright = "Copyright © 2023 MedCom" -//* publisher = "MedCom" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Thea Mentz Sørensen" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "tms@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* contact[SubjectMatterExpert].name = "Subject Matter Expert, Mie Borch Dahl Ballegaard" -* contact[SubjectMatterExpert].telecom.system = #email -* contact[SubjectMatterExpert].telecom.value = "mbk@medcom.dk" -* contact[SubjectMatterExpert].telecom.use = #work -* description = "DK: Advis om sygehusophold (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "DK: Regioner sender og kommuner modtager (Hvem skal anvende standarden jf. §3,3 i bekendtgørelsen)" -* purpose = "DK: Sende information fra sygehus til kommune, når patient opholder sig på sygehuset, enten indlagt eller andet fysisk ophold (fx på et ambulatorium) (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* eventCoding = $MessageEvents#hospital-notification-message -* responseRequired = #always -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0.0" -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0.1" -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.CareCommunication:3.0.0" - -Instance: Eer.fhir.MessageDefinition.hospitalNotification:2.0 -InstanceOf: EerMessageDefinitionFhir -Description: "An example of an EerMessageDefinition for hospitalnotification:2.0" -* id = "Eer.fhir.MessageDefinition.hospitalNotification.2.0" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:hospitalnotification:2.0 -* identifier.period.start = "2021-03-23" -* identifier.period.end = "2023-01-05" -* identifier.use = #old -* identifier.value = "hospitalnotification.2.0" -* version = "2.0.0" -//* name = "HospitalNotification:2.0" -* title = "HospitalNotification 2.0" -* replaces.value = "Eer.fhir.MessageDefinition.hospitalNotification:1.0" -* status = #retired -* date = "2022-10-05" -* copyright = "Copyright © 2022 MedCom" -//* publisher = "MedCom" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Thea Mentz Sørensen" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "tms@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* contact[SubjectMatterExpert].name = "Subject Matter Expert, Mie Borch Dahl Ballegaard" -* contact[SubjectMatterExpert].telecom.system = #email -* contact[SubjectMatterExpert].telecom.value = "mbk@medcom.dk" -* contact[SubjectMatterExpert].telecom.use = #work -* description = "DK: Advis om sygehusophold (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "DK: Regioner sender og kommuner modtager (Hvem skal anvende standarden jf. §3,3 i bekendtgørelsen)" -* purpose = "DK: Sende information fra sygehus til kommune, når patient opholder sig på sygehuset, enten indlagt eller andet fysisk ophold (fx på et ambulatorium) (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* eventCoding = $MessageEvents#hospital-notification-message -* responseRequired = #always -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0.0" -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0.1" -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.CareCommunication:3.0.0" - -Instance: Eer.fhir.MessageDefinition.hospitalNotification:1.0 -InstanceOf: EerMessageDefinitionFhir -Description: "An example of an EerMessageDefinition for hospitalnotification:1.0" -* id = "Eer.fhir.MessageDefinition.hospitalNotification.1.0" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:hospitalnotification:1.0 -* identifier.period.start = "2021-03-23" -* identifier.period.end = "2022-10-04" -* identifier.use = #old -* identifier.value = "hospitalnotification.1.0" -* version = "1.0" -//* name = "HospitalNotification:1.0" -* title = "HospitalNotification 1.0" -* status = #retired -* date = "2021-03-23" -* copyright = "Copyright © 2021 MedCom" -//* publisher = "MedCom" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Thea Mentz Sørensen" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "tms@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* contact[SubjectMatterExpert].name = "Subject Matter Expert, Mie Borch Dahl Ballegaard" -* contact[SubjectMatterExpert].telecom.system = #email -* contact[SubjectMatterExpert].telecom.value = "mbk@medcom.dk" -* contact[SubjectMatterExpert].telecom.use = #work -* description = "DK: Advis om sygehusophold (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "DK: Regioner sender og kommuner modtager (Hvem skal anvende standarden jf. §3,3 i bekendtgørelsen)" -* purpose = "DK: Sende information fra sygehus til kommune, når patient opholder sig på sygehuset, enten indlagt eller andet fysisk ophold (fx på et ambulatorium) (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* copyright = "Copyright © 2022 MedCom" -* eventCoding = $MessageEvents#hospital-notification-message -* responseRequired = #always -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0.0" -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.Acknowledgement:2.0.1" -* allowedResponse[+].message.value = "Eer.fhir.MessageDefinition.CareCommunication:3.0.0" - diff --git a/input/fsh/instances/MessageDefinitions/oioxml/oioxml-MessageDefinition.fsh b/input/fsh/instances/MessageDefinitions/oioxml/oioxml-MessageDefinition.fsh deleted file mode 100644 index d44c745..0000000 --- a/input/fsh/instances/MessageDefinitions/oioxml/oioxml-MessageDefinition.fsh +++ /dev/null @@ -1,30 +0,0 @@ -Instance: EHMI.oioxml.MessageDefinition.xref15.xh1530r -InstanceOf: EerMessageDefinitionOioxml -Description: "An example of an EerMessageDefinition for xref15:xh1530r" -* id = "EHMI.edi.MessageDefinition.xref15.xh1530r" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:medref:xref15:xh1530r -* identifier.period.start = "2020-01-01" -* identifier.use = #official -* identifier.value = "xref15:xh1530r" -* version = "xh1530r" -//* name = "XML-Kommunehenvisning" -* title = "xml-kommunehenvisning" -* status = #active -* date = "2023-01-01" -//* publisher = "MedCom" -* contact[InteroperabilityConsultant].id = "InteroperabilityConsultant" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Michael Johansen" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "mjo@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* contact[SubjectMatterExpert].id = "SubjectMatterExpert" -* contact[SubjectMatterExpert].name = "Subject Matter Expert, Gitte Henriksen" -* contact[SubjectMatterExpert].telecom.system = #email -* contact[SubjectMatterExpert].telecom.value = "ghe@medcom.dk" -* contact[SubjectMatterExpert].telecom.use = #work -* description = "Patienter med kronisk sygdom, som ud fra en sundhedsfaglig vurdering af funktionsevne og helbredsforhold kan have gavn af et forebyggelsestilbud, eller patienter, der ikke har kronisk sygdom, kan have behov for at blive henvist til et forebyggelsestilbud i kommunen. Dette kan ske fra lægepraksis eller fra sygehuset i forbindelse med udskrivelse eller ambulant behandling (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "Regioner, Private parter i sundhedsvæsenet, Kommuner" -* purpose = "Denne standard anvendes til henvisning til kommunal forebyggelse (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* copyright = "Copyright © 2022 MedCom" -* eventCoding = $MessageEvents#empty-message - diff --git a/input/fsh/instances/MessageDefinitions/sbdh/sbdh-MessageDefinition.fsh b/input/fsh/instances/MessageDefinitions/sbdh/sbdh-MessageDefinition.fsh deleted file mode 100644 index 74afde4..0000000 --- a/input/fsh/instances/MessageDefinitions/sbdh/sbdh-MessageDefinition.fsh +++ /dev/null @@ -1,26 +0,0 @@ -Instance: EHMI.envelope.sbdh.sbd.MessageDefinition -InstanceOf: EerMessageDefinitionEnvelope -Description: "An example of an EerMessageDefinition for sbdh.1.0." -* id = "EHMI.MessageDefinition.envelope.sbdh.1.0" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:envelope:xml:sbdh:1.0 -//* identifier.system = $EerMessageDefinitionIdentifierSystem#urn:dk:healthcare:medcom:messaging:envelope -* identifier.period.start = "2024-01-01" -* identifier.use = #official -* identifier.value = "sbdh.1.0" -* version = "1.0" -//* name = "SBDHEnvelope" -* title = "SBDH Envelope 1.0" -* status = #active -* date = "2024-01-01" -* copyright = "Copyright © 2023 MedCom" -* contact[InteroperabilityConsultant].id = "InteroperabilityConsultant" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Ole Vilstrup Møller" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "ovi@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* description = "SBDH Envelope (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "Alle eDelivery kommunikerende parter" -* purpose = "Denne standard anvendes, når man ønsker at sende en meddelelse over eDelivery netværket (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* eventCoding = $MessageEvents#empty-message -* responseRequired = #always - diff --git a/input/fsh/instances/MessageDefinitions/sbdh/sbdhack-MessageDefinition.fsh b/input/fsh/instances/MessageDefinitions/sbdh/sbdhack-MessageDefinition.fsh deleted file mode 100644 index 80ced8e..0000000 --- a/input/fsh/instances/MessageDefinitions/sbdh/sbdhack-MessageDefinition.fsh +++ /dev/null @@ -1,26 +0,0 @@ -Instance: EHMI.envelope.sbdh.sbdhacknowledgement.MessageDefinition -InstanceOf: EerMessageDefinitionEnvelope -Description: "An example of an EerMessageDefinition for SBDH." -* id = "EHMI.MessageDefinition.envelope.sbdhacknowledgement.1.0" -* url = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:envelope:xml:sbdhacknowledgement:1.0 -//* identifier.system = $EerMessageDefinitionIdentifierSystem#urn:dk:healthcare:medcom:messaging:envelope -* identifier.period.start = "2024-01-01" -* identifier.use = #official -* identifier.value = "sbdhacknowledgement.1.0" -* version = "1.0" -//* name = "sbdhacknowledgement:1.0" -* title = "SBDH Acknowledgement 1.0" -* status = #active -* date = "2024-01-01" -* copyright = "Copyright © 2023 MedCom" -//* publisher = "MedCom" -* contact[InteroperabilityConsultant].id = "InteroperabilityConsultant" -* contact[InteroperabilityConsultant].name = "Interoperability Consultant, Ole Vilstrup Møller" -* contact[InteroperabilityConsultant].telecom.system = #email -* contact[InteroperabilityConsultant].telecom.value = "ovi@medcom.dk" -* contact[InteroperabilityConsultant].telecom.use = #work -* description = "SBDH Acknowledgement (RUSA Standardkatalog - Beskrivelse jf. §3stk2 i bekendtgørelsen)" -* useContext.valueCodeableConcept.text = "Alle eDelivery kommunikerende parter" -* purpose = "Denne standard anvendes, når man ønsker at kvittere på en sendt SBDH-envelope over eDelivery netværket (RUSA Standardkatalog - Hvad skal standarden anvendes til jf. §3,2 i bekendtgørelsen)" -* eventCoding = $MessageEvents#empty-message -* responseRequired = #never diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.IN.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.IN.fsh index a3302a2..264ce17 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.IN.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.IN.fsh @@ -1,18 +1,20 @@ +/* Instance: EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.IN -InstanceOf: EHMIMessagingVansEdiEndpoint -Description: "AAR EHMIMessaging VansEdi Endpoint Inbound" +InstanceOf: EerMessagingVansEdiEndpoint +Description: "AAR EerMessaging VansEdi Endpoint Inbound" * id = "EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.IN" * identifier.value = "5790002621741" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN //* identifier.use = "official" * status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.1280171000016004) +* managingOrganization = Reference(Organization/EER.SOR.HI-AAR-Kommune.1280171000016004) * period.start = "2023-01-01" //* period.end = "2024-01-01" * address = "http://aar.dk/vans/edi/in" * payloadMimeType[0] = #application/EDIFACT -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q "Negativ Vans kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q "Negativ kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q "Positiv kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis91:d9134l "Korrespondancebrev" +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q "Negativ Vans kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q "Negativ kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q "Positiv kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis91:d9134l "Korrespondancebrev" +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.OUT.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.OUT.fsh index 469e375..72c8074 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.OUT.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI/EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.OUT.fsh @@ -1,19 +1,21 @@ +/* Instance: EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.OUT -InstanceOf: EHMIMessagingVansEdiEndpoint -Description: "AAR EHMIMessaging VansEdi Endpoint Outbound" +InstanceOf: EerMessagingVansEdiEndpoint +Description: "AAR EerMessaging VansEdi Endpoint Outbound" * id = "EP.MSG.HI.AAR.1280171000016004.GLN.5790002621741.VANS.EDI.OUT" * identifier.value = "5790002621741" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN //* identifier.use = "official" * status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.1280171000016004) +* managingOrganization = Reference(Organization/EER.SOR.HI-AAR-Kommune.1280171000016004) * period.start = "2023-01-01" //* period.end = "2024-01-01" * address = "http://aar.dk/vans/edi/out" * payloadMimeType[0] = #application/EDIFACT -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q "Negativ Vans kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q "Negativ kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q "Positiv kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis01:d0134l "Udskrivningsepikrise" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis91:d9134l "Korrespondancebrev" +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q "Negativ Vans kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q "Negativ kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q "Positiv kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis01:d0134l "Udskrivningsepikrise" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis91:d9134l "Korrespondancebrev" +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.IN.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.IN.fsh index ebf1b89..84150fd 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.IN.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.IN.fsh @@ -1,22 +1,24 @@ +/* Instance: EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.IN -InstanceOf: EHMIMessagingVansOioxmlEndpoint -Description: "AAR EHMIMessagingVansOioxmlEndpoint." +InstanceOf: EerMessagingVansOioxmlEndpoint +Description: "AAR EerMessagingVansOioxmlEndpoint." * id = "EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.IN" * identifier.value = "5790000123117" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN //* identifier.use = "official" * status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.937961000016000) +* managingOrganization = Reference(Organization/EER.SOR.HI-AAR-Kommune.937961000016000) * period.start = "2023-01-01" //* period.end = "2024-01-01" * address = "http://aar.dk/vans/oioxml/in" * payloadMimeType = #text/xml -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis18:xd1834c "XML udskrivningsrapport" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis19:xd1934c "XML melding om færdigbehandling" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis21:xd2134c "XML plejeforløbsplan" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis22:xd2230l "XML Afslutningsnotat fra kommunens akutfunktion" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:medref:xref22:xh2230r "XML Henvisning til kommunens akutfunktion" +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis18:xd1834c "XML udskrivningsrapport" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis19:xd1934c "XML melding om færdigbehandling" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis21:xd2134c "XML plejeforløbsplan" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis22:xd2230l "XML Afslutningsnotat fra kommunens akutfunktion" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:medref:xref22:xh2230r "XML Henvisning til kommunens akutfunktion" +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.OUT.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.OUT.fsh index 5395feb..f44ac77 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.OUT.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML/EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.OUT.fsh @@ -1,20 +1,22 @@ +/* Instance: EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.OUT -InstanceOf: EHMIMessagingVansOioxmlEndpoint -Description: "AAR EHMIMessagingVansOioxmlEndpoint." +InstanceOf: EerMessagingVansOioxmlEndpoint +Description: "AAR EerMessagingVansOioxmlEndpoint." * id = "EP.MSG.HI.AAR.937961000016000.GLN.5790000123117.VANS.OIOXML.OUT" * identifier.value = "5790000123117" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN //* identifier.use = "official" * status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.937961000016000) +* managingOrganization = Reference(Organization/EER.SOR.HI-AAR-Kommune.937961000016000) * period.start = "2023-01-01" //* period.end = "2024-01-01" * address = "http://www.aar.dk/oioxml" * payloadMimeType = #text/xml -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis16:xd1634c "XML indlæggelsesrapport" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis22:xd2230l "XML Afslutningsnotat fra kommunens akutfunktion" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:medref:xref22:xh2230r "XML Henvisning til kommunens akutfunktion" +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis16:xd1634c "XML indlæggelsesrapport" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis22:xd2230l "XML Afslutningsnotat fra kommunens akutfunktion" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:medref:xref22:xh2230r "XML Henvisning til kommunens akutfunktion" +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI.IN.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI.IN.fsh index 7df037e..aa1fd36 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI.IN.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI.IN.fsh @@ -1,18 +1,20 @@ +/* Instance: EP.MSG.HI.AAR.937961000016000.GLN.5790001998486.VANS.EDI.IN -InstanceOf: EHMIMessagingVansEdiEndpoint -Description: "AAR EHMIMessaging VansEdi Endpoint Inbound" +InstanceOf: EerMessagingVansEdiEndpoint +Description: "AAR EerMessaging VansEdi Endpoint Inbound" * id = "EP.MSG.HI.AAR.937961000016000.GLN.5790001998486.VANS.EDI.IN" * identifier.value = "5790001998486" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN //* identifier.use = "official" * status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951351000016007) +* managingOrganization = Reference(Organization/EER.SOR.HI-AAR-Kommune.951351000016007) * period.start = "2023-01-01" //* period.end = "2024-01-01" * address = "http://aar.dk/vans/edi/in" * payloadMimeType[0] = #application/EDIFACT -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q "Negativ Vans kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q "Negativ kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q "Positiv kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis91:d9134l "Korrespondancebrev" +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q "Negativ Vans kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q "Negativ kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q "Positiv kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis91:d9134l "Korrespondancebrev" +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI.OUT.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI.OUT.fsh index 2c6be28..544a54f 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI.OUT.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.EDI.OUT.fsh @@ -1,19 +1,21 @@ +/* Instance: EP.MSG.HI.AAR.937961000016000.GLN.5790001998486.VANS.EDI.OUT -InstanceOf: EHMIMessagingVansEdiEndpoint -Description: "AAR EHMIMessaging VansEdi Endpoint Inbound" +InstanceOf: EerMessagingVansEdiEndpoint +Description: "AAR EerMessaging VansEdi Endpoint Inbound" * id = "EP.MSG.HI.AAR.937961000016000.GLN.5790001998486.VANS.EDI.OUT" * identifier.value = "5790001998486" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN //* identifier.use = "official" * status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951351000016007) +* managingOrganization = Reference(Organization/EER.SOR.HI-AAR-Kommune.951351000016007) * period.start = "2023-01-01" //* period.end = "2024-01-01" * address = "http://aar.dk/vans/edi/out" * payloadMimeType[0] = #application/EDIFACT -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q "Negativ Vans kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q "Negativ kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q "Positiv kvittering" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis01:d0134l "Udskrivningsepikrise" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis91:d9134l "Korrespondancebrev" +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl01:c0130q "Negativ Vans kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl02:c0230q "Negativ kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:contrl:ctl03:c0330q "Positiv kvittering" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis01:d0134l "Udskrivningsepikrise" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:edifact:meddis:dis91:d9134l "Korrespondancebrev" +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML.IN.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML.IN.fsh index b578fc7..46071ef 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML.IN.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML.IN.fsh @@ -1,18 +1,20 @@ +/* Instance: EP.MSG.HI.AAR.937961000016000.GLN.5790001998486.VANS.OIOXML.IN -InstanceOf: EHMIMessagingVansOioxmlEndpoint -Description: "AAR EHMIMessaging VansOioxml Endpoint Inbound" +InstanceOf: EerMessagingVansOioxmlEndpoint +Description: "AAR EerMessaging VansOioxml Endpoint Inbound" * id = "EP.MSG.HI.AAR.937961000016000.GLN.5790001998486.VANS.OIOXML.IN" * identifier.value = "5790001998486" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN //* identifier.use = "official" * status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951351000016007) +* managingOrganization = Reference(Organization/EER.SOR.HI-AAR-Kommune.951351000016007) * period.start = "2023-01-01" //* period.end = "2024-01-01" * address = "http://aar.dk/vans/oioxml/in" * payloadMimeType = #text/xml -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis91:xd9134l "ClinicalEmail" +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis91:xd9134l "ClinicalEmail" +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML.OUT.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML.OUT.fsh index aafbdb6..e97f125 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML.OUT.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML/EP.MSG.HI.AAR.951351000016007.GLN.5790001998486.VANS.OIOXML.OUT.fsh @@ -1,18 +1,20 @@ +/* Instance: EP.MSG.HI.AAR.937961000016000.GLN.5790001998486.VANS.OIOXML.OUT -InstanceOf: EHMIMessagingVansOioxmlEndpoint -Description: "AAR EHMIMessaging VansEdi Endpoint Outbound" +InstanceOf: EerMessagingVansOioxmlEndpoint +Description: "AAR EerMessaging VansEdi Endpoint Outbound" * id = "EP.MSG.HI.AAR.937961000016000.GLN.5790001998486.VANS.OIOXML.OUT" * identifier.value = "5790000123117" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN //* identifier.use = "official" * status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951351000016007) +* managingOrganization = Reference(Organization/EER.SOR.HI-AAR-Kommune.951351000016007) * period.start = "2023-01-01" //* period.end = "2024-01-01" * address = "http://aar.dk/vans/edi/out" * payloadMimeType = #text/xml -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" -* payloadType[+] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis91:xd9134l "ClinicalEmail" +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl01:xc0130q "NegativeVansReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl02:xc0230q "NegativeReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:contrl:xctl03:xc0330q "PositivReceipt" +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:oioxml:schema:xsd:meddis:xdis91:xd9134l "ClinicalEmail" +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.Msg.AAR.eDeliveryFhir.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.Msg.AAR.eDeliveryFhir.fsh new file mode 100644 index 0000000..8e32d4b --- /dev/null +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/EP.Msg.AAR.eDeliveryFhir.fsh @@ -0,0 +1,18 @@ +Instance: EerEndpoint-Messaging-AAR-eDeliveryFhir.5790002508226 +InstanceOf: EerEndpointMessagingEdeliveryFhir +Description: "AAR EerEndpointMessagingEdeliveryFhir." +* id = "EerEndpoint-Messaging-AAR-eDeliveryFhir.01" +* identifier.value = "5790002508226" +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN +//* identifier.use = "official" +* status = #active +* managingOrganization = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* period.start = "2023-01-01" +* period.end = "2024-01-01" +* address = "http://eDeliveryAccessPoint.aar.dk/fhir" +* extension[networkSupplySystem].valueReference = Reference(EerDeviceAP-MultiMedAP) +* payloadMimeType[0] = #application/fhir+xml +* payloadMimeType[+] = #application/fhir+json +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:homecareobservation:2.0 +* payloadType[+] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP-AAR-VansEdi.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP-AAR-VansEdi.fsh deleted file mode 100644 index 97a2cae..0000000 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP-AAR-VansEdi.fsh +++ /dev/null @@ -1,17 +0,0 @@ -Instance: EHMIMessagingEndpoint-AAR-VansEdi.5790002508226 -InstanceOf: EHMIeDeliveryMessagingEdiEndpoint -Description: "AAR EHMIeDeliveryMessagingEdiEndpoint." -* id = "EHMIMessagingEndpoint-AAR-VansEdi.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://aar.dk/fhir" -* payloadMimeType[0] = #application/fhir+xml -//* payloadMimeType[1] = #application/fhir+json -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 -//* payloadType[1] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP-AAR-VansOioxml.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP-AAR-VansOioxml.fsh deleted file mode 100644 index 1eb2a77..0000000 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP-AAR-VansOioxml.fsh +++ /dev/null @@ -1,17 +0,0 @@ -Instance: EHMIMessagingEndpoint-AAR-VansOioxml.5790002508226 -InstanceOf: EHMIeDeliveryMessagingOioxmlEndpoint -Description: "AAR EHMIeDeliveryMessagingOioxmlEndpoint." -* id = "EHMIMessagingEndpoint-AAR-VansOioxml.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://aar.dk/fhir" -* payloadMimeType[0] = #application/fhir+xml -//* payloadMimeType[1] = #application/fhir+json -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 -//* payloadType[1] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_VansFhir.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_VansFhir.fsh deleted file mode 100644 index 11c2958..0000000 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_VansFhir.fsh +++ /dev/null @@ -1,15 +0,0 @@ -Instance: EHMIMessagingEndpoint-AAR-VansFhir.5790002508226 -InstanceOf: EHMIMessagingVansFhirEndpoint -Description: "AAR EHMIMessagingEndpoint-AAR-VansFhir.01." -* id = "EHMIMessagingEndpoint-AAR-VansFhir.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://aar.dk/fhir" -* payloadMimeType = #text/plain -* payloadType = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_eDeliveryEdi.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_eDeliveryEdi.fsh deleted file mode 100644 index 5883ff9..0000000 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_eDeliveryEdi.fsh +++ /dev/null @@ -1,17 +0,0 @@ -Instance: EHMIMessagingEndpoint-AAR-eDeliveryEdi.5790002508226 -InstanceOf: EHMIeDeliveryMessagingEdiEndpoint -Description: "AAR EHMIeDeliveryMessagingEdiEndpoint." -* id = "EHMIMessagingEndpoint-AAR-eDeliveryEdi.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://aar.dk/fhir" -* payloadMimeType[0] = #application/fhir+xml -//* payloadMimeType[1] = #application/fhir+json -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 -//* payloadType[1] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_eDeliveryFhir.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_eDeliveryFhir.fsh deleted file mode 100644 index 132e223..0000000 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_eDeliveryFhir.fsh +++ /dev/null @@ -1,17 +0,0 @@ -Instance: EHMIMessagingEndpoint-AAR-eDeliveryFhir.5790002508226 -InstanceOf: EHMIeDeliveryMessagingFhirEndpoint -Description: "AAR EHMIeDeliveryMessagingFhirEndpoint." -* id = "EHMIMessagingEndpoint-AAR-eDeliveryFhir.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://aar.dk/fhir" -* payloadMimeType[0] = #application/fhir+xml -//* payloadMimeType[1] = #application/fhir+json -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 -//* payloadType[1] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_eDeliveryOioxml.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_eDeliveryOioxml.fsh deleted file mode 100644 index 314fb01..0000000 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/MsgEP_AAR_eDeliveryOioxml.fsh +++ /dev/null @@ -1,17 +0,0 @@ -Instance: EHMIMessagingEndpoint-AAR-eDeliveryOioxml.5790002508226 -InstanceOf: EHMIeDeliveryMessagingOioxmlEndpoint -Description: "AAR EHMIeDeliveryMessagingOioxmlEndpoint." -* id = "EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01" -* identifier.value = "5790002508226" -* identifier.system = $EHMIAuditEventAgentWhoIdentifierTypes -* identifier.type = $EHMIAuditEventAgentWhoIdentifierTypes#GLN -//* identifier.use = "official" -* status = #active -* managingOrganization = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* period.start = "2023-01-01" -* period.end = "2024-01-01" -* address = "http://aar.dk/fhir" -* payloadMimeType[0] = #application/fhir+xml -//* payloadMimeType[1] = #application/fhir+json -* payloadType[0] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 -//* payloadType[1] = $MedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP-AAR-VansEdi.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP-AAR-VansEdi.fsh new file mode 100644 index 0000000..0926290 --- /dev/null +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP-AAR-VansEdi.fsh @@ -0,0 +1,19 @@ +/* +Instance: EerEndpoint-Messaging-AAR-VansEdi.5790002508226 +InstanceOf: EereDeliveryMessagingEdiEndpoint +Description: "AAR EereDeliveryMessagingEdiEndpoint." +* id = "EerEndpoint-Messaging-AAR-VansEdi.01" +* identifier.value = "5790002508226" +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN +//* identifier.use = "official" +* status = #active +* managingOrganization = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* period.start = "2023-01-01" +* period.end = "2024-01-01" +* address = "http://eDeliveryAccessPoint.aar.dk/fhir" +* payloadMimeType[0] = #application/fhir+xml +//* payloadMimeType[1] = #application/fhir+json +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 +//* payloadType[1] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP-AAR-VansOioxml.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP-AAR-VansOioxml.fsh new file mode 100644 index 0000000..6a61355 --- /dev/null +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP-AAR-VansOioxml.fsh @@ -0,0 +1,19 @@ +/* +Instance: EerEndpoint-Messaging-AAR-VansOioxml.5790002508226 +InstanceOf: EereDeliveryMessagingOioxmlEndpoint +Description: "AAR EereDeliveryMessagingOioxmlEndpoint." +* id = "EerEndpoint-Messaging-AAR-VansOioxml.01" +* identifier.value = "5790002508226" +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN +//* identifier.use = "official" +* status = #active +* managingOrganization = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* period.start = "2023-01-01" +* period.end = "2024-01-01" +* address = "http://eDeliveryAccessPoint.aar.dk/fhir" +* payloadMimeType[0] = #application/fhir+xml +//* payloadMimeType[1] = #application/fhir+json +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 +//* payloadType[1] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP_AAR_VansFhir.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP_AAR_VansFhir.fsh new file mode 100644 index 0000000..b8dbca1 --- /dev/null +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP_AAR_VansFhir.fsh @@ -0,0 +1,17 @@ +/* +Instance: EerEndpoint-Messaging-AAR-VansFhir.5790002508226 +InstanceOf: EerMessagingVansFhirEndpoint +Description: "AAR EerEndpoint-Messaging-AAR-VansFhir.01." +* id = "EerEndpoint-Messaging-AAR-VansFhir.01" +* identifier.value = "5790002508226" +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN +//* identifier.use = "official" +* status = #active +* managingOrganization = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* period.start = "2023-01-01" +* period.end = "2024-01-01" +* address = "http://eDeliveryAccessPoint.aar.dk/fhir" +* payloadMimeType = #text/plain +* payloadType = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP_AAR_eDeliveryEdi.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP_AAR_eDeliveryEdi.fsh new file mode 100644 index 0000000..7a8a285 --- /dev/null +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP_AAR_eDeliveryEdi.fsh @@ -0,0 +1,19 @@ +/* +Instance: EerEndpoint-Messaging-AAR-eDeliveryEdi.5790002508226 +InstanceOf: EereDeliveryMessagingEdiEndpoint +Description: "AAR EereDeliveryMessagingEdiEndpoint." +* id = "EerEndpoint-Messaging-AAR-eDeliveryEdi.01" +* identifier.value = "5790002508226" +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN +//* identifier.use = "official" +* status = #active +* managingOrganization = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* period.start = "2023-01-01" +* period.end = "2024-01-01" +* address = "http://eDeliveryAccessPoint.aar.dk/fhir" +* payloadMimeType[0] = #application/fhir+xml +//* payloadMimeType[1] = #application/fhir+json +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 +//* payloadType[1] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP_AAR_eDeliveryOioxml.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP_AAR_eDeliveryOioxml.fsh new file mode 100644 index 0000000..cc3f35f --- /dev/null +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/Endpoints/Version2 instances/MsgEP_AAR_eDeliveryOioxml.fsh @@ -0,0 +1,19 @@ +/* +Instance: EerEndpoint-Messaging-AAR-eDeliveryOioxml.5790002508226 +InstanceOf: EereDeliveryMessagingOioxmlEndpoint +Description: "AAR EereDeliveryMessagingOioxmlEndpoint." +* id = "EerEndpoint-Messaging-AAR-eDeliveryOioxml.01" +* identifier.value = "5790002508226" +* identifier.system = $EerAuditEventAgentWhoIdentifierTypes +* identifier.type = $EerAuditEventAgentWhoIdentifierTypes#GLN +//* identifier.use = "official" +* status = #active +* managingOrganization = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* period.start = "2023-01-01" +* period.end = "2024-01-01" +* address = "http://eDeliveryAccessPoint.aar.dk/fhir" +* payloadMimeType[0] = #application/fhir+xml +//* payloadMimeType[1] = #application/fhir+json +* payloadType[0] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 +//* payloadType[1] = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.Facility.7141000016000/HI.Facility.7141000016000.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.Facility.7141000016000/HI.Facility.7141000016000.fsh deleted file mode 100644 index 20fbfef..0000000 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.Facility.7141000016000/HI.Facility.7141000016000.fsh +++ /dev/null @@ -1,10 +0,0 @@ -Instance: EHMI.SOR.HI.Fac-AAR-Kommune.7141000016000 -InstanceOf: SORFacilityOrganization -Description: "An example of an SOR HI Organization." -* id = "EHMI.SOR.HI.Fac-AAR-Kommune.7141000016000" -* identifier.value = "EHMI.SOR.HI.Fac-AAR-Kommune.7141000016000" -* name = "EHMI.SOR.HI.Fac-AAR-Kommune.7141000016000" -//* type[facility] = #prov -//* type[facility].coding.code = #facility -//* type[facility].coding.system = https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.7141000016000) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.533291000016001/SOR.OU-Aarhus-Kommune-533301000016002.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.533291000016001/SOR.OU-Aarhus-Kommune-533301000016002.fsh index 9068369..6151c99 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.533291000016001/SOR.OU-Aarhus-Kommune-533301000016002.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.533291000016001/SOR.OU-Aarhus-Kommune-533301000016002.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.533301000016002 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.533301000016002 +InstanceOf: EerSorOrganization Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.533301000016002" -* id = "EHMI.SOR.OU-AAR-Kommune.533301000016002" +* id = "Eer.Sor.OU-AAR-Kommune.533301000016002" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "533301000016002" -* name = "EHMI SOR OU AAR Kommune (533301000016002)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.533291000016001) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (533301000016002)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.533291000016001) +//*endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//*endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//*endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//*endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//*endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144351000016009.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144351000016009.fsh index 3e679c2..79ddae3 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144351000016009.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144351000016009.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.1144351000016009 -InstanceOf: EHMISOROUOrganization -Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune-SOR.1144351000016009" -* id = "EHMI.SOR.OU-AAR-Kommune.1144351000016009" +Instance: Eer.Sor.OU-AAR-Kommune.1144351000016009 +InstanceOf: EerSorOrganization +Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.1144351000016009" +* id = "Eer.Sor.OU-AAR-Kommune.1144351000016009" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1144351000016009" -* name = "EHMI SOR OU AAR Kommune (1144351000016009)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.937961000016000) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (1144351000016009)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.937961000016000) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144541000016003.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144541000016003.fsh index 9da512c..73c073a 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144541000016003.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144541000016003.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.1144541000016003 -InstanceOf: EHMISOROUOrganization -Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune-SOR.1144541000016003" -* id = "EHMI.SOR.OU-AAR-Kommune.1144541000016003" +Instance: Eer.Sor.OU-AAR-Kommune.1144541000016003 +InstanceOf: EerSorOrganization +Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.1144541000016003" +* id = "Eer.Sor.OU-AAR-Kommune.1144541000016003" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1144541000016003" -* name = "EHMI SOR OU AAR Kommune (1144541000016003)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.937961000016000) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (1144541000016003)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.937961000016000) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144751000016008.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144751000016008.fsh index 5a54155..26d339f 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144751000016008.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1144751000016008.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.1144751000016008 -InstanceOf: EHMISOROUOrganization -Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune-SOR.1144751000016008" -* id = "EHMI.SOR.OU-AAR-Kommune.1144751000016008" +Instance: Eer.Sor.OU-AAR-Kommune.1144751000016008 +InstanceOf: EerSorOrganization +Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.1144751000016008" +* id = "Eer.Sor.OU-AAR-Kommune.1144751000016008" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1144751000016008" -* name = "EHMI SOR OU AAR Kommune (1144751000016008)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.937961000016000) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (1144751000016008)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.937961000016000) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1244791000016004.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1244791000016004.fsh index 4bae2ab..0aea010 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1244791000016004.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-1244791000016004.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.1244791000016004 -InstanceOf: EHMISOROUOrganization -Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune-SOR.1244791000016004" -* id = "EHMI.SOR.OU-AAR-Kommune.1244791000016004" +Instance: Eer.Sor.OU-AAR-Kommune.1244791000016004 +InstanceOf: EerSorOrganization +Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.1244791000016004" +* id = "Eer.Sor.OU-AAR-Kommune.1244791000016004" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1244791000016004" -* name = "EHMI SOR OU AAR Kommune (1244791000016004)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.937961000016000) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (1244791000016004)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.937961000016000) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-937971000016005.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-937971000016005.fsh index 5052ea1..bda3db7 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-937971000016005.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.937961000016000/SOR.OU-Aarhus-Kommune-937971000016005.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.937971000016005 -InstanceOf: EHMISOROUOrganization -Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune-SOR.937971000016005" -* id = "EHMI.SOR.OU-AAR-Kommune.937971000016005" +Instance: Eer.Sor.OU-AAR-Kommune.937971000016005 +InstanceOf: EerSorOrganization +Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.937971000016005" +* id = "Eer.Sor.OU-AAR-Kommune.937971000016005" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "937971000016005" -* name = "EHMI SOR OU AAR Kommune (937971000016005)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.937961000016000) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (937971000016005)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.937961000016000) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-1027201000016001.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-1027201000016001.fsh index d3593de..7d0e10c 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-1027201000016001.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-1027201000016001.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.1027201000016001 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.1027201000016001 +InstanceOf: EerSorOrganization Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.1027201000016001" -* id = "EHMI.SOR.OU-AAR-Kommune.1027201000016001" +* id = "Eer.Sor.OU-AAR-Kommune.1027201000016001" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1027201000016001" -* name = "EHMI SOR OU AAR Kommune (1027201000016001)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951311000016008) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (1027201000016001)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.951311000016008) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-1221961000016009.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-1221961000016009.fsh index 81739ab..28c4ba6 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-1221961000016009.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-1221961000016009.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.1221961000016009 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.1221961000016009 +InstanceOf: EerSorOrganization Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.1221961000016009" -* id = "EHMI.SOR.OU-AAR-Kommune.1221961000016009" +* id = "Eer.Sor.OU-AAR-Kommune.1221961000016009" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1221961000016009" -* name = "EHMI SOR OU AAR Kommune (1221961000016009)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951311000016008) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (1221961000016009)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.951311000016008) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-951321000016004.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-951321000016004.fsh index ba0d7a4..e472200 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-951321000016004.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-951321000016004.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.951321000016004 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.951321000016004 +InstanceOf: EerSorOrganization Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.951321000016004" -* id = "EHMI.SOR.OU-AAR-Kommune.951321000016004" +* id = "Eer.Sor.OU-AAR-Kommune.951321000016004" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "951321000016004" -* name = "EHMI SOR OU AAR Kommune (951321000016004)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951311000016008) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (951321000016004)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.951311000016008) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-951341000016009.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-951341000016009.fsh index 3841e23..9d24fab 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-951341000016009.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951311000016008/SOR.OU-Aarhus-Kommune-951341000016009.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.951341000016009 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.951341000016009 +InstanceOf: EerSorOrganization Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.951341000016009" -* id = "EHMI.SOR.OU-AAR-Kommune.951341000016009" +* id = "Eer.Sor.OU-AAR-Kommune.951341000016009" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "951341000016009" -* name = "EHMI SOR OU AAR Kommune (951341000016009)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951311000016008) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (951341000016009)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.951311000016008) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1296871000016007.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1296871000016007.fsh index f27aaec..b683883 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1296871000016007.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1296871000016007.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.1296871000016007 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.1296871000016007 +InstanceOf: EerSorOrganization Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.1296871000016007" -* id = "EHMI.SOR.OU-AAR-Kommune.1296871000016007" +* id = "Eer.Sor.OU-AAR-Kommune.1296871000016007" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1296871000016007" -* name = "EHMI SOR OU AAR Kommune (1296871000016007)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951351000016007) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (1296871000016007)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.951351000016007) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1297941000016008.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1297941000016008.fsh index 945f8d2..dfe02ee 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1297941000016008.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1297941000016008.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.1297941000016008 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.1297941000016008 +InstanceOf: EerSorOrganization Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.1297941000016008" -* id = "EHMI.SOR.OU-AAR-Kommune.1297941000016008" +* id = "Eer.Sor.OU-AAR-Kommune.1297941000016008" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1297941000016008" -* name = "EHMI SOR OU AAR Kommune (1297941000016008)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951351000016007) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (1297941000016008)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.951351000016007) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1336701000016008.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1336701000016008.fsh index ffbbf3b..3d27a0f 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1336701000016008.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-1336701000016008.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.1336701000016008 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.1336701000016008 +InstanceOf: EerSorOrganization Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.1336701000016008" -* id = "EHMI.SOR.OU-AAR-Kommune.1336701000016008" +* id = "Eer.Sor.OU-AAR-Kommune.1336701000016008" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1336701000016008" -* name = "EHMI SOR OU AAR Kommune (1336701000016008)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951351000016007) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (1336701000016008)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.951351000016007) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-445351000016009.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-445351000016009.fsh index 82704f0..39e9893 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-445351000016009.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-445351000016009.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.445351000016009 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.445351000016009 +InstanceOf: EerSorOrganization Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.445351000016009" -* id = "EHMI.SOR.OU-AAR-Kommune.445351000016009" +* id = "Eer.Sor.OU-AAR-Kommune.445351000016009" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "445351000016009" -* name = "EHMI SOR OU AAR Kommune (445351000016009)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951351000016007) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (445351000016009)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.951351000016007) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-535411000016006.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-535411000016006.fsh index 0fafde1..a0d64d8 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-535411000016006.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-535411000016006.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.535411000016006 -InstanceOf: EHMISOROUOrganization -Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune-SOR.535411000016006" -* id = "EHMI.SOR.OU-AAR-Kommune.535411000016006" +Instance: Eer.Sor.OU-AAR-Kommune.535411000016006 +InstanceOf: EerSorOrganization +Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.535411000016006" +* id = "Eer.Sor.OU-AAR-Kommune.535411000016006" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "535411000016006" -* name = "EHMI SOR OU AAR Kommune (535411000016006)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune-SOR.951351000016007) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -//* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -//* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -//* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (535411000016006)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune-SOR.951351000016007) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//*endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//*endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//*endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951361000016005.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951361000016005.fsh index 36cd998..6124169 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951361000016005.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951361000016005.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.951361000016005 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.951361000016005 +InstanceOf: EerSorOrganization Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.951361000016005" -* id = "EHMI.SOR.OU-AAR-Kommune.951361000016005" +* id = "Eer.Sor.OU-AAR-Kommune.951361000016005" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "951361000016005" -* name = "EHMI SOR OU AAR Kommune (951361000016005)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.951351000016007) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (951361000016005)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.951351000016007) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951391000016001.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951391000016001.fsh index 8b7cf25..8c1fc2b 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951391000016001.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951391000016001.fsh @@ -1,15 +1,12 @@ -Instance: EHMI.SOR.OU-AAR-Kommune-SOR.951391000016001 -InstanceOf: EHMISOROUOrganization -Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune-SOR.951391000016001" -* id = "EHMI.SOR.OU-AAR-Kommune.951391000016001" +Instance: Eer.SOR.OU-AAR-Kommune.951391000016001 +InstanceOf: EerSorOrganization +Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.951391000016001" +* id = "Eer.Sor.OU-AAR-Kommune.951391000016001" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "951391000016001" -* name = "EHMI SOR OU AAR Kommune (951391000016001)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune-SOR.951351000016007) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -//* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -//* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -//* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (951391000016001)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune-SOR.951351000016007) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951401000016003.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951401000016003.fsh index e9c35e7..f707f77 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951401000016003.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.OU.951351000016007/SOR.OU-Aarhus-Kommune-951401000016003.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune-SOR.951401000016003 -InstanceOf: EHMISOROUOrganization -Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune-SOR.951401000016003" -* id = "EHMI.SOR.OU-AAR-Kommune.951401000016003" +Instance: Eer.SOR.OU-AAR-Kommune.951401000016003 +InstanceOf: EerSorOrganization +Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.951401000016003" +* id = "Eer.Sor.OU-AAR-Kommune.951401000016003" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "951401000016003" -* name = "EHMI SOR OU AAR Kommune (951401000016003)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune-SOR.951351000016007) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -//* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -//* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -//* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (951401000016003)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune-SOR.951351000016007) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//*endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//*endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//*endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.1280171000016004.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.1280171000016004.fsh index 906c226..bc15ced 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.1280171000016004.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.1280171000016004.fsh @@ -1,9 +1,14 @@ -Instance: EHMI.SOR.HI-AAR-Kommune.1280171000016004 -InstanceOf: EHMISORHIOrganization +Instance: EER.SOR.HI-AAR-Kommune.1280171000016004 +InstanceOf: EerSorOrganization Description: "AAR SOR HI Organization.1280171000016004 - Sociale Forhold og Beskæftigelse" -* id = "EHMI.SOR.HI-AAR-Kommune.1280171000016004" +* id = "EER.SOR.HI-AAR-Kommune.1280171000016004" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1280171000016004" -* type[SOR-UnitType].coding.code = $EHMISORUnitType#administrativ-enhed -* name = "EHMI SOR HI AAR Kommune - Sociale Forhold og Beskæftigelse (1280171000016004)" -* partOf = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#SI +* identifier[SOR].system = "1.2.208.176.1.1" +* type[SOR-UnitType].coding.code = $EerSorUnitType#administrativ-enhed +* type[SOR-UnitType].coding.system = $EerSorUnitType +* name = "EER SOR HI AAR Kommune - Sociale Forhold og Beskæftigelse (1280171000016004)" +* partOf = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#SI +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.533291000016001.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.533291000016001.fsh index 4f8a4d7..8a1c411 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.533291000016001.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.533291000016001.fsh @@ -1,9 +1,12 @@ -Instance: EHMI.SOR.HI-AAR-Kommune.533291000016001 -InstanceOf: EHMISORHIOrganization +Instance: EER.SOR.HI-AAR-Kommune.533291000016001 +InstanceOf: EerSorOrganization Description: "AAR SOR HI Organization.533291000016001 - Specialdagtilbud Skovbrynet" -* id = "EHMI.SOR.HI-AAR-Kommune.533291000016001" +* id = "EER.SOR.HI-AAR-Kommune.533291000016001" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "533291000016001" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#SI -* type[SOR-UnitType].coding.code = $EHMISORUnitType#genoptræningsenhed -* name = "EHMI SOR HI AAR Kommune - Specialdagtilbud Skovbrynet (533291000016001)" -* partOf = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#SI +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* type[SOR-UnitType].coding.code = $EerSorUnitType#genoptræningsenhed +* name = "EER SOR HI AAR Kommune - Specialdagtilbud Skovbrynet (533291000016001)" +* partOf = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.937961000016000.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.937961000016000.fsh index 4d1550e..93bcd0c 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.937961000016000.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.937961000016000.fsh @@ -1,9 +1,14 @@ -Instance: EHMI.SOR.HI-AAR-Kommune.937961000016000 -InstanceOf: EHMISORHIOrganization +Instance: EER.SOR.HI-AAR-Kommune.937961000016000 +InstanceOf: EerSorOrganization Description: "AAR SOR HI Organization - Sundhed og Omsorg" -* id = "EHMI.SOR.HI-AAR-Kommune.937961000016000" +* id = "EER.SOR.HI-AAR-Kommune.937961000016000" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "937961000016000" -* type[SOR-UnitType] = $EHMISORUnitType#sundhedsforvaltning -* name = "EHMI SOR HI AAR Kommune - Sundhed og Omsorg (937961000016000)" -* partOf = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#SI +* type[SOR-UnitType] = $EerSorUnitType#sundhedsforvaltning +* name = "EER SOR HI AAR Kommune - Sundhed og Omsorg (937961000016000)" +* partOf = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#SI +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType + + diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.951351000016007.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.951351000016007.fsh index cdf496c..82bbe00 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.951351000016007.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/SOR.HI-Aarhus-Kommune.951351000016007.fsh @@ -1,9 +1,12 @@ -Instance: EHMI.SOR.HI-AAR-Kommune.951351000016007 -InstanceOf: EHMISORHIOrganization +Instance: EER.SOR.HI-AAR-Kommune.951351000016007 +InstanceOf: EerSorOrganization Description: "AAR SOR HI Organization.951351000016007 - Socialforvaltningen, AAR kommune" -* id = "EHMI.SOR.HI-AAR-Kommune.951351000016007" +* id = "EER.SOR.HI-AAR-Kommune.951351000016007" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "951351000016007" -* type[SOR-UnitType] = $EHMISORUnitType#administrativ-enhed -* name = "EHMI SOR HI AAR Kommune - Socialforvaltningen, AAR kommune (951351000016007)" -* partOf = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#SI +* type[SOR-UnitType] = $EerSorUnitType#administrativ-enhed +* name = "EER SOR HI AAR Kommune - Socialforvaltningen, AAR kommune (951351000016007)" +* partOf = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#SI +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.Facility.7141000016000/HI.Facility.7141000016000.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.Facility.7141000016000/HI.Facility.7141000016000.fsh new file mode 100644 index 0000000..741ea1f --- /dev/null +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.Facility.7141000016000/HI.Facility.7141000016000.fsh @@ -0,0 +1,12 @@ +/* +Instance: Eer.Sor.HI.Fac-AAR-Kommune.7141000016000 +InstanceOf: SORFacilityOrganization +Description: "An example of an SOR HI Organization." +* id = "Eer.Sor.HI.Fac-AAR-Kommune.7141000016000" +* identifier.value = "Eer.Sor.HI.Fac-AAR-Kommune.7141000016000" +* name = "Eer.Sor.HI.Fac-AAR-Kommune.7141000016000" +//* type[facility] = #prov +//* type[facility].coding.code = #facility +//* type[facility].coding.system = https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.7141000016000) +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.HealthCareService.7141000016000/HI.Facility.HealthcareService.7141000016000.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.HealthCareService.7141000016000/HI.Facility.HealthcareService.7141000016000.fsh similarity index 57% rename from input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.HealthCareService.7141000016000/HI.Facility.HealthcareService.7141000016000.fsh rename to input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.HealthCareService.7141000016000/HI.Facility.HealthcareService.7141000016000.fsh index dad20d5..34ed22a 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/HI.HealthCareService.7141000016000/HI.Facility.HealthcareService.7141000016000.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.HealthCareService.7141000016000/HI.Facility.HealthcareService.7141000016000.fsh @@ -1,13 +1,14 @@ -Instance: EHMI.SOR.HI.Fac.HCS-AAR-Kommune.7141000016000 +/* +Instance: Eer.Sor.HI.Fac.HCS-AAR-Kommune.7141000016000 InstanceOf: SORHealthcareService Description: "An example of an SOR HI Organization." -* id = "EHMI.SOR.HI.Fac.HCS-AAR-Kommune.7141000016000" -* identifier.value = "EHMI.SOR.HI.Fac.HCS-AAR-Kommune.7141000016000" -* name = "EHMI.SOR.HI.Fac.HCS-AAR-Kommune.7141000016000" +* id = "Eer.Sor.HI.Fac.HCS-AAR-Kommune.7141000016000" +* identifier.value = "Eer.Sor.HI.Fac.HCS-AAR-Kommune.7141000016000" +* name = "Eer.Sor.HI.Fac.HCS-AAR-Kommune.7141000016000" //* type[facility] = #prov //* type[facility].coding.code = #facility //* type[facility].coding.system = https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types -* providedBy = Reference(Organization/EHMI.SOR.HI.Fac-AAR-Kommune.7141000016000) +* providedBy = Reference(Organization/Eer.Sor.HI.Fac-AAR-Kommune.7141000016000) * category = #35 * type = #358 * specialty = #394602003 @@ -15,3 +16,4 @@ Description: "An example of an SOR HI Organization." * extraDetails = "extraDetails" * program = #21 * referralMethod = #elec +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.7141000016000/SOR.OU-Aarhus-Kommune-1053851000016007.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.7141000016000/SOR.OU-Aarhus-Kommune-1053851000016007.fsh index efbd64f..6ffa93d 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.7141000016000/SOR.OU-Aarhus-Kommune-1053851000016007.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.7141000016000/SOR.OU-Aarhus-Kommune-1053851000016007.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune-SOR.1053851000016007 -InstanceOf: EHMISOROUOrganization -Description: "LÆ- blanketter, suppl. kommunikation, AAR - SOR.OU-AAR-Kommune-SOR.1053851000016007" -* id = "EHMI.SOR.OU-AAR-Kommune-SOR.1053851000016007" +Instance: Eer.SOR.OU-AAR-Kommune.1053851000016007 +InstanceOf: EerSorOrganization +Description: "LÆ- blanketter, suppl. kommunikation, AAR - SOR.OU-AAR-Kommune.1053851000016007" +* id = "Eer.SOR.OU-AAR-Kommune.1053851000016007" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1053851000016007" -* name = "EHMI SOR OU AAR Kommune (1053851000016007)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune-SOR.937961000016000) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (1053851000016007)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune-SOR.937961000016000) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.7141000016000/SOR.OU-Aarhus-Kommune-576011000016009.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.7141000016000/SOR.OU-Aarhus-Kommune-576011000016009.fsh index d9da62c..95a81db 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.7141000016000/SOR.OU-Aarhus-Kommune-576011000016009.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.7141000016000/SOR.OU-Aarhus-Kommune-576011000016009.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.576011000016009 -InstanceOf: EHMISOROUOrganization -Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune-SOR.576011000016009" -* id = "EHMI.SOR.OU-AAR-Kommune.576011000016009" +Instance: Eer.Sor.OU-AAR-Kommune.576011000016009 +InstanceOf: EerSorOrganization +Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.576011000016009" +* id = "Eer.Sor.OU-AAR-Kommune.576011000016009" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "576011000016009" -* name = "EHMI SOR OU AAR Kommune (576011000016009)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.7141000016000) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (576011000016009)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.7141000016000) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.947241000016008/SOR.OU-Aarhus-Kommune-1028251000016001.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.947241000016008/SOR.OU-Aarhus-Kommune-1028251000016001.fsh index bb140db..1e6946b 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.947241000016008/SOR.OU-Aarhus-Kommune-1028251000016001.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.947241000016008/SOR.OU-Aarhus-Kommune-1028251000016001.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.1028251000016001 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.1028251000016001 +InstanceOf: EerSorOrganization Description: "LÆ- blanketter, suppl. kommunikation, AAR - SOR.OU-AAR-Kommune.1028251000016001" -* id = "EHMI.SOR.OU-AAR-Kommune.1028251000016001" +* id = "Eer.Sor.OU-AAR-Kommune.1028251000016001" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "1028251000016001" -* name = "EHMI SOR OU AAR Kommune (1028251000016001)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.947241000016008) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (1028251000016001)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.947241000016008) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.947241000016008/SOR.OU-Aarhus-Kommune-947251000016006.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.947241000016008/SOR.OU-Aarhus-Kommune-947251000016006.fsh index d6ce1d4..c87f43e 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.947241000016008/SOR.OU-Aarhus-Kommune-947251000016006.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xHI.OU.947241000016008/SOR.OU-Aarhus-Kommune-947251000016006.fsh @@ -1,15 +1,17 @@ -Instance: EHMI.SOR.OU-AAR-Kommune.947251000016006 -InstanceOf: EHMISOROUOrganization +Instance: Eer.Sor.OU-AAR-Kommune.947251000016006 +InstanceOf: EerSorOrganization Description: "Sygehusadviser, AAR - SOR.OU-AAR-Kommune.947251000016006" -* id = "EHMI.SOR.OU-AAR-Kommune.947251000016006" +* id = "Eer.Sor.OU-AAR-Kommune.947251000016006" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "947251000016006" -* name = "EHMI SOR OU AAR Kommune (947251000016006)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-AAR-Kommune.947241000016008) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-AAR-eDeliveryOioxml.01) +* name = "EER SOR OU AAR Kommune (947251000016006)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR.HI-AAR-Kommune.947241000016008) +//* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryEdi.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryFhir.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-VansOioxml.01) +//* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-AAR-eDeliveryOioxml.01) diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.7141000016000.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.7141000016000.fsh index 079aef4..f9bcfbf 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.7141000016000.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.7141000016000.fsh @@ -1,9 +1,12 @@ -Instance: EHMI.SOR.HI-AAR-Kommune.7141000016000 -InstanceOf: EHMISORHIOrganization +Instance: EER.SOR.HI-AAR-Kommune.7141000016000 +InstanceOf: EerSorOrganization Description: "AAR SOR HI Organization - Sundhed og Omsorg" -* id = "EHMI.SOR.HI-AAR-Kommune.7141000016000" +* id = "EER.SOR.HI-AAR-Kommune.7141000016000" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "7141000016000" -* type[SOR-UnitType].coding.code = $EHMISORUnitType#sundhedsforvaltning -* name = "EHMI SOR HI AAR Kommune - Sundhed og Omsorg (7141000016000)" -* partOf = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#SI +* type[SOR-UnitType].coding.code = $EerSorUnitType#sundhedsforvaltning +* name = "EER SOR HI AAR Kommune - Sundhed og Omsorg (7141000016000)" +* partOf = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#SI +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.947241000016008.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.947241000016008.fsh index f111c0d..b65d680 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.947241000016008.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.947241000016008.fsh @@ -1,9 +1,12 @@ -Instance: EHMI.SOR.HI-AAR-Kommune.947241000016008 -InstanceOf: EHMISORHIOrganization +Instance: EER.SOR.HI-AAR-Kommune.947241000016008 +InstanceOf: EerSorOrganization Description: "AAR SOR HI Organization.947241000016008" -* id = "EHMI.SOR.HI-AAR-Kommune.947241000016008" +* id = "EER.SOR.HI-AAR-Kommune.947241000016008" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "947241000016008" -* type[SOR-UnitType].coding.code = $EHMISORUnitType#sundhedsforvaltning -* name = "EHMI SOR HI AAR Kommune (947241000016008)" -* partOf = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#SI +* type[SOR-UnitType].coding.code = $EerSorUnitType#sundhedsforvaltning +* name = "EER SOR HI AAR Kommune (947241000016008)" +* partOf = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#SI +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.951311000016008.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.951311000016008.fsh index 626e429..0cdf162 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.951311000016008.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/HI/xSOR.HI-Aarhus-Kommune.951311000016008.fsh @@ -1,9 +1,12 @@ -Instance: EHMI.SOR.HI-AAR-Kommune.951311000016008 -InstanceOf: EHMISORHIOrganization +Instance: EER.SOR.HI-AAR-Kommune.951311000016008 +InstanceOf: EerSorOrganization Description: "AAR SOR HI Organization.951311000016008" -* id = "EHMI.SOR.HI-AAR-Kommune.951311000016008" +* id = "EER.SOR.HI-AAR-Kommune.951311000016008" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "951311000016008" -* type[SOR-UnitType] = $EHMISORUnitType#sundhedsforvaltning -* name = "EHMI SOR HI AAR Kommune (951311000016008)" -* partOf = Reference(Organization/EHMI.SOR.IO-AAR-Kommune.311000016009) -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#SI +* type[SOR-UnitType] = $EerSorUnitType#sundhedsforvaltning +* name = "EER SOR HI AAR Kommune (951311000016008)" +* partOf = Reference(Organization/Eer.Sor.IO-AAR-Kommune.311000016009) +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#SI +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType diff --git a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/SOR.IO-Aarhus-Kommune.fsh b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/SOR.IO-Aarhus-Kommune.fsh index a7e1dcd..c448f9b 100644 --- a/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/SOR.IO-Aarhus-Kommune.fsh +++ b/input/fsh/instances/SOR Hierarchi/Aarhus Kommune/SOR.IO-Aarhus-Kommune.fsh @@ -1,16 +1,17 @@ -Instance: EHMI.SOR.IO-AAR-Kommune.311000016009 -InstanceOf: EHMISORMunicipalityOrganization -Description: "EHMI.SOR.IO-AAR-Kommune as a SOR IO Organization." -* id = "EHMI.SOR.IO-AAR-Kommune.311000016009" //SOR-Id -* identifier[SOR].type = $EHMISORorganizationIdentierType#SOR +Instance: Eer.Sor.IO-AAR-Kommune.311000016009 +InstanceOf: EerSorOrganization +Description: "Eer.Sor.IO-AAR-Kommune as a SOR IO Organization." +* id = "Eer.Sor.IO-AAR-Kommune.311000016009" //SOR-Id +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" * identifier[SOR].value = "311000016009" -* identifier[MunicipalityCode].system = $EHMISORMunicipalityCode -* identifier[MunicipalityCode].type = $EHMISORorganizationIdentierType#MunicipalityCode -* identifier[MunicipalityCode].value = $EHMISORMunicipalityCode#0751 -* name = "EHMI SOR IO AAR Kommune (311000016009)" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#IE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* type[EHMISORIOOrganizationType].coding.code = $EHMISORIOOrganizationType#Municipality -* type[EHMISORIOOrganizationType].coding.system = $EHMISORIOOrganizationType -* type[SOR-UnitType].coding.code = $EHMISORUnitType#kommune -* type[SOR-UnitType].coding.system = $EHMISORUnitType +* identifier[MunicipalityCode].system = $EerSorMunicipalityCode +* identifier[MunicipalityCode].type = $EerSorOrganizationIdentierType#MunicipalityCode +* identifier[MunicipalityCode].value = $EerSorMunicipalityCode#0751 +* name = "EER SOR IO AAR Kommune (311000016009)" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#IE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* type[EerSorIOOrganizationType].coding.code = $EerSorIOOrganizationType#Municipality +* type[EerSorIOOrganizationType].coding.system = $EerSorIOOrganizationType +* type[SOR-UnitType].coding.code = $EerSorUnitType#kommune +* type[SOR-UnitType].coding.system = $EerSorUnitType diff --git a/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.HI-Herlev-Kommune.fsh b/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.HI-Herlev-Kommune.fsh deleted file mode 100644 index 2a8d495..0000000 --- a/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.HI-Herlev-Kommune.fsh +++ /dev/null @@ -1,11 +0,0 @@ -/* -Instance: EHMI.SOR.HI-Herlev-Kommune-SOR.6501000016006 -InstanceOf: EHMISORHIOrganization -Description: "An example of an SOR HI Organization." -* id = "EHMI.SOR.HI-Herlev-Kommune-SOR.6501000016006" -* identifier.value = "6501000016006" -* type[SOR-Hierarchy] = $EHMISOROrganizationType#HI -* name = "EHMI.SOR.HI-Herlev-Kommune-SOR.6501000016006" -* partOf = Reference(Organization/EHMI.SOR.IO-Herlev-Kommune-SOR.101000016005) -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#HI -*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.IO-Herlev-Kommune.fsh b/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.IO-Herlev-Kommune.fsh deleted file mode 100644 index 276b32a..0000000 --- a/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.IO-Herlev-Kommune.fsh +++ /dev/null @@ -1,10 +0,0 @@ -/* -Instance: EHMI.SOR.IO-Herlev-Kommune -InstanceOf: EHMISORIOMunicipalityOrganization -Description: "EHMI.SOR.IO-Herlev-Kommune as a SOR IO Organization." -* id = "EHMI.SOR.IO-Herlev-Kommune-SOR.101000016005" //SOR-Id -* identifier.value = "101000016005" //SOR-Id -* name = "EHMI.SOR.IO-Herlev-Kommune" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#IO -* type[EHMISORIOOrganizationType].coding.code = $EHMISORIOOrganizationType#Municipality -*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.OU-Herlev-Kommune-Level1.fsh b/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.OU-Herlev-Kommune-Level1.fsh deleted file mode 100644 index fe55347..0000000 --- a/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.OU-Herlev-Kommune-Level1.fsh +++ /dev/null @@ -1,17 +0,0 @@ -/* -Instance: EHMI.SOR.OU-Herlev-Kommune-SOR.1053211000016007 -InstanceOf: EHMISOROUOrganization -Description: "Sygehusadviser, Herlev - SOR.OU-Herlev-Kommune-SOR.1053211000016007" -* id = "EHMI.SOR.OU-Herlev-Kommune-SOR.1053211000016007" -* identifier.value = "1053211000016007" -* name = "EHMI.SOR.OU-Herlev-Kommune-SOR.1053211000016007" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OU -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-Herlev-Kommune-SOR.6501000016006) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-eDeliveryOioxml.01) -*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.OU-Herlev-Kommune-Level2.fsh b/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.OU-Herlev-Kommune-Level2.fsh deleted file mode 100644 index 7fe3ced..0000000 --- a/input/fsh/instances/SOR Hierarchi/Herlev Kommune/SOR.OU-Herlev-Kommune-Level2.fsh +++ /dev/null @@ -1,17 +0,0 @@ -/* -Instance: EHMI.SOR.OU-Herlev-Kommune-SOR.646961000016000 -InstanceOf: EHMISOROUOrganization -Description: "LÆ- blanketter, suppl. kommunikation, Herlev - SOR.OU-Herlev-Kommune-SOR.646961000016000" -* id = "EHMI.SOR.OU-Herlev-Kommune-SOR.646961000016000" -* identifier.value = "646961000016000" -* name = "EHMI.SOR.OU-Herlev-Kommune-SOR.646961000016000" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OU -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI-Herlev-Kommune-SOR.6501000016006) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-VansOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-Herlev-eDeliveryOioxml.01) -*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Princip/SOR HI Org.fsh b/input/fsh/instances/SOR Hierarchi/Princip/SOR HI Org.fsh index a808adc..a9093d0 100644 --- a/input/fsh/instances/SOR Hierarchi/Princip/SOR HI Org.fsh +++ b/input/fsh/instances/SOR Hierarchi/Princip/SOR HI Org.fsh @@ -1,9 +1,12 @@ -Instance: EHMISORHIOrganization_1.0 -InstanceOf: EHMISORHIOrganization +Instance: EER.SOR-HI.01 +InstanceOf: EerSorOrganization Description: "An example of an SOR HI Organization." -* id = "EHMI.SOR.HI.01.1" -* identifier[SOR].value = "EHMI.SOR.HI.01.1" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#SI -* type[SOR-UnitType].coding.code = $EHMISORUnitType#genoptræningsenhed -* name = "EHMI-SOR-HI-Organization" -* partOf = Reference(Organization/EHMI.SOR.IO.01) \ No newline at end of file +* id = "EER.SOR-HI.01" +* identifier[SOR].value = "EER.SOR-HI.01" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#SI +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* type[SOR-UnitType].coding.code = $EerSorUnitType#genoptræningsenhed +* name = "EER-SOR-HI-Organization" +* partOf = Reference(Organization/EER.SOR.IO.01) \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Princip/SOR IO Org.fsh b/input/fsh/instances/SOR Hierarchi/Princip/SOR IO Org.fsh index 9d6d81b..fd02b1b 100644 --- a/input/fsh/instances/SOR Hierarchi/Princip/SOR IO Org.fsh +++ b/input/fsh/instances/SOR Hierarchi/Princip/SOR IO Org.fsh @@ -1,13 +1,14 @@ -Instance: EHMI.SORIOOrganization.1.0 -InstanceOf: EHMISORIOOrganization +Instance: EER.SOR-IO.01 +InstanceOf: EerSorOrganization Description: "An example of an SOR IO Organization." -* id = "EHMI.SOR.IO.01" -* identifier[SOR].type = $EHMISORorganizationIdentierType#SOR -* identifier[SOR].value = "EHMI.SOR.IO.01" -* name = "EHMI-SOR-IO-Organization" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#IE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* type[EHMISORIOOrganizationType].coding.code = $EHMISORIOOrganizationType#Generic -* type[EHMISORIOOrganizationType].coding.system = $EHMISORIOOrganizationType -//* type[SOR-UnitType].coding.code = $EHMISORUnitType#other -* type[SOR-UnitType].coding.system = $EHMISORUnitType +* id = "EER.SOR.IO.01" +* identifier[SOR].value = "EER.SOR.IO.01" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" +* name = "EER-SOR-IO-Organization" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#IE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* type[EerSorIOOrganizationType].coding.code = $EerSorIOOrganizationType#Generic +* type[EerSorIOOrganizationType].coding.system = $EerSorIOOrganizationType +* type[SOR-UnitType].coding.code = $EerSorUnitType#region +* type[SOR-UnitType].coding.system = $EerSorUnitType diff --git a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L1 Facility.fsh b/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L1 Facility.fsh deleted file mode 100644 index 3fc080f..0000000 --- a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L1 Facility.fsh +++ /dev/null @@ -1,8 +0,0 @@ -Instance: EHMI.SOR.OU.L1.Facility.Organization-1.0 -InstanceOf: SORFacilityOrganization -Description: "An example of an SOR HI Organization." -* id = "EHMI.SOR.OU.L1.Facility.Organization-1.0" -* identifier.value = "EHMI.SOR.OU.L1.Facility.Organization-1.0" -* name = "EHMI.SOR.OU.L1.Facility.Organization-1.0" -* partOf = Reference(Organization/EHMI.SOROU-EMCSD.SOR.OU.01) - diff --git a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L1 Healthcare Service.fsh b/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L1 Healthcare Service.fsh deleted file mode 100644 index 6fa5efd..0000000 --- a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L1 Healthcare Service.fsh +++ /dev/null @@ -1,12 +0,0 @@ -Instance: EHMI.SOR.OU.L1.HealthcareService.Organization-1.0 -InstanceOf: SORHealthcareService -Description: "An example of an SOR HI Organization." -* id = "EHMI.SOR.OU.L1.HealthcareService.Organization-1.0" -* identifier.value = "EHMI.SOR.OU.L1.HealthcareService.Organization-1.0" -* name = "EHMI.SOR.OU.L1.HealthcareService.Organization-1.0" -//* type[facility] = #prov -//* type[facility].coding.code = #facility -//* type[facility].coding.system = https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types -* providedBy = Reference(Organization/EHMI.SOR.OU.L1.Facility.Organization-1.0) -* type = #358 -* specialty = #394602003 diff --git a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L1 Org.fsh b/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L1 Org.fsh index 8af29ce..35392fe 100644 --- a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L1 Org.fsh +++ b/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L1 Org.fsh @@ -1,15 +1,19 @@ -Instance: EHMI.SOROU-EMCSD.SOR.OU.01 -InstanceOf: EHMISOROUOrganization +Instance: EER.SOR-OU.01 +InstanceOf: EerSorOrganization Description: "An example of an SOR OU Organization." -* id = "EHMI.SOROU-EMCSD.SOR.OU.01" -* identifier[SOR].value = "EHMI.SOROU-EMCSD.SOR.OU.01" -* name = "EHMI.SOR-OU-Organization" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOR.HI.01.1) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-eDeliveryOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-VansOioxml.01) +* id = "EER.SOR-OU.01" +* identifier[SOR].value = "EER.SOR-OU.01" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" +* name = "EER.SOR-OU-Organization" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR-HI.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-eDeliveryFhir.01) +/* +* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-eDeliveryEdi.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-eDeliveryOioxml.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-VansEdi.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-VansOioxml.01) +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L2 Facility.fsh b/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L2 Facility.fsh deleted file mode 100644 index 0aebfa8..0000000 --- a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L2 Facility.fsh +++ /dev/null @@ -1,8 +0,0 @@ -Instance: EHMI.SOR.OU.L2.Facility.Organization-1.0 -InstanceOf: SORFacilityOrganization -Description: "An example of an SOR HI Organization." -* id = "EHMI.SOR.OU.L2.Facility.Organization-1.0" -* identifier.value = "EHMI.SOR.OU.L2.Facility.Organization-1.0" -* name = "EHMI.SOR.OU.L2.Facility.Organization-1.0" -* partOf = Reference(Organization/EHMI.SOROU-EMCSD.SOR.OU.01.01) - diff --git a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L2 Healthcare Service.fsh b/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L2 Healthcare Service.fsh deleted file mode 100644 index 2703929..0000000 --- a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L2 Healthcare Service.fsh +++ /dev/null @@ -1,9 +0,0 @@ -Instance: EHMI.SOR.OU.L2.HealthcareService.Organization-1.0 -InstanceOf: SORHealthcareService -Description: "An example of an SOR HI Organization." -* id = "EHMI.SOR.OU.L2.HealthcareService.Organization-1.0" -* identifier.value = "EHMI.SOR.OU.L2.HealthcareService.Organization-1.0" -* name = "EHMI.SOR.OU.L2.HealthcareService.Organization-1.0" -* providedBy = Reference(Organization/EHMI.SOR.OU.L2.Facility.Organization-1.0) -* type = #359 -* specialty = #394602002 diff --git a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L2 Org.fsh b/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L2 Org.fsh index 7e1aa3a..4ecd5f2 100644 --- a/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L2 Org.fsh +++ b/input/fsh/instances/SOR Hierarchi/Princip/SOR OU-L2 Org.fsh @@ -1,15 +1,19 @@ -Instance: EHMI.SOROU-EMCSD.SOR.OU.01.01 -InstanceOf: EHMISOROUOrganization +Instance: EER.SOR-OU.01.01 +InstanceOf: EerSorOrganization Description: "An example of an SOR OU Organization." -* id = "EHMI.SOROU-EMCSD.SOR.OU.01.01" -* identifier[SOR].value = "SOROU-EMCSD.SOR.OU.01.01" -* name = "EHMI.SOR-OU-Organization" -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* partOf = Reference(Organization/EHMI.SOROU-EMCSD.SOR.OU.01) -* endpoint[0] = Reference(Endpoint/EHMIMessagingEndpoint-eDeliveryEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-eDeliveryFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-eDeliveryOioxml.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-VansEdi.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-VansFhir.01) -* endpoint[+] = Reference(Endpoint/EHMIMessagingEndpoint-VansOioxml.01) +* id = "EER.SOR-OU.01.01" +* identifier[SOR].value = "EER.SOR.OU.01.01" +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID +* identifier[SOR].system = "1.2.208.176.1.1" +* name = "EER.SOR-OU-Organization" +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* partOf = Reference(Organization/EER.SOR-OU.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-eDeliveryFhir.01) +/* +* endpoint[0] = Reference(Endpoint/EerEndpoint-Messaging-eDeliveryEdi.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-eDeliveryOioxml.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-VansEdi.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-VansFhir.01) +* endpoint[+] = Reference(Endpoint/EerEndpoint-Messaging-VansOioxml.01) +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Princip/SOR HI Facility.fsh b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR HI Facility.fsh similarity index 51% rename from input/fsh/instances/SOR Hierarchi/Princip/SOR HI Facility.fsh rename to input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR HI Facility.fsh index c72b1ce..fc36a64 100644 --- a/input/fsh/instances/SOR Hierarchi/Princip/SOR HI Facility.fsh +++ b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR HI Facility.fsh @@ -1,10 +1,12 @@ -Instance: EHMI.SOR.HI.Facility.Organization-1.0 +/* +Instance: Eer.Sor.HI.Facility.Organization-1.0 InstanceOf: SORFacilityOrganization Description: "An example of an SOR HI Organization." -* id = "EHMI.SOR.HI.Facility.Organization-1.0" -* identifier.value = "EHMI.SOR.HI.Facility.Organization-1.0" -* name = "EHMI.SOR.HI.Facility.Organization-1.0" +* id = "Eer.Sor.HI.Facility.Organization-1.0" +* identifier.value = "Eer.Sor.HI.Facility.Organization-1.0" +* name = "Eer.Sor.HI.Facility.Organization-1.0" //* type[facility] = #prov //* type[facility].coding.code = #facility //* type[facility].coding.system = https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types -* partOf = Reference(Organization/EHMI.SOR.HI.01.1) +* partOf = Reference(Organization/EER.SOR-HI.01) +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Princip/SOR HI Healthcare Service.fsh b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR HI Healthcare Service.fsh similarity index 57% rename from input/fsh/instances/SOR Hierarchi/Princip/SOR HI Healthcare Service.fsh rename to input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR HI Healthcare Service.fsh index b30fbde..dd6a9b8 100644 --- a/input/fsh/instances/SOR Hierarchi/Princip/SOR HI Healthcare Service.fsh +++ b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR HI Healthcare Service.fsh @@ -1,13 +1,14 @@ -Instance: EHMI.SOR.HI.HealthcareService.Organization-1.0 +/* +Instance: Eer.Sor.HI.HealthcareService.Organization-1.0 InstanceOf: SORHealthcareService Description: "An example of an SOR HI Organization." -* id = "EHMI.SOR.HI.HealthcareService.Organization-1.0" -* identifier.value = "EHMI.SOR.HI.HealthcareService.Organization-1.0" -* name = "EHMI.SOR.HI.HealthcareService.Organization-1.0" +* id = "Eer.Sor.HI.HealthcareService.Organization-1.0" +* identifier.value = "Eer.Sor.HI.HealthcareService.Organization-1.0" +* name = "Eer.Sor.HI.HealthcareService.Organization-1.0" //* type[facility] = #prov //* type[facility].coding.code = #facility //* type[facility].coding.system = https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types -* providedBy = Reference(Organization/EHMI.SOR.HI.Facility.Organization-1.0) +* providedBy = Reference(Organization/Eer.Sor.HI.Facility.Organization-1.0) * category = #35 * type = #358 * specialty = #394602003 @@ -15,3 +16,4 @@ Description: "An example of an SOR HI Organization." * extraDetails = "extraDetails" * program = #21 * referralMethod = #elec +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Princip/SOR IO Jurisdiction.fsh b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR IO Jurisdiction.fsh similarity index 92% rename from input/fsh/instances/SOR Hierarchi/Princip/SOR IO Jurisdiction.fsh rename to input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR IO Jurisdiction.fsh index d24c3d5..273cd4e 100644 --- a/input/fsh/instances/SOR Hierarchi/Princip/SOR IO Jurisdiction.fsh +++ b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR IO Jurisdiction.fsh @@ -5,7 +5,7 @@ Description: "An example of an SORIOOrganization." * id = "EMCSD.SOR.JUR.01.1" * identifier.value = "EMCSD.SOR.JUR.01.1" * name = "SOR-JUR-Organization" -* type.coding.system = http://medcomehmi.dk/ig/ehmi_mcsd/CodeSystem/ehmi-sor-organization-type +* type.coding.system = http://medcomehmi.dk/ig/ehmi_mcsd/CodeSystem/eer-sor-organization-type * type.coding.code = "IO" //* partOf = Reference(Organization/EMCSD.SOR.IO.01.1) */ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L1 Facility.fsh b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L1 Facility.fsh new file mode 100644 index 0000000..9053d93 --- /dev/null +++ b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L1 Facility.fsh @@ -0,0 +1,10 @@ +/* +Instance: Eer.Sor.OU.L1.Facility.Organization-1.0 +InstanceOf: SORFacilityOrganization +Description: "An example of an SOR HI Organization." +* id = "Eer.Sor.OU.L1.Facility.Organization-1.0" +* identifier.value = "Eer.Sor.OU.L1.Facility.Organization-1.0" +* name = "Eer.Sor.OU.L1.Facility.Organization-1.0" +* partOf = Reference(Organization/EER.SOR-OU.01) + +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L1 Healthcare Service.fsh b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L1 Healthcare Service.fsh new file mode 100644 index 0000000..ee81b52 --- /dev/null +++ b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L1 Healthcare Service.fsh @@ -0,0 +1,14 @@ +/* +Instance: Eer.Sor.OU.L1.HealthcareService.Organization-1.0 +InstanceOf: SORHealthcareService +Description: "An example of an SOR HI Organization." +* id = "Eer.Sor.OU.L1.HealthcareService.Organization-1.0" +* identifier.value = "Eer.Sor.OU.L1.HealthcareService.Organization-1.0" +* name = "Eer.Sor.OU.L1.HealthcareService.Organization-1.0" +//* type[facility] = #prov +//* type[facility].coding.code = #facility +//* type[facility].coding.system = https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types +* providedBy = Reference(Organization/Eer.Sor.OU.L1.Facility.Organization-1.0) +* type = #358 +* specialty = #394602003 +*/ \ No newline at end of file diff --git a/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L2 Facility.fsh b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L2 Facility.fsh new file mode 100644 index 0000000..daab57b --- /dev/null +++ b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L2 Facility.fsh @@ -0,0 +1,9 @@ +/* +Instance: Eer.Sor.OU.L2.Facility.Organization-1.0 +InstanceOf: SORFacilityOrganization +Description: "An example of an SOR HI Organization." +* id = "Eer.Sor.OU.L2.Facility.Organization-1.0" +* identifier.value = "Eer.Sor.OU.L2.Facility.Organization-1.0" +* name = "Eer.Sor.OU.L2.Facility.Organization-1.0" +* partOf = Reference(Organization/EER.SOR-OU.01.01) +*/ diff --git a/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L2 Healthcare Service.fsh b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L2 Healthcare Service.fsh new file mode 100644 index 0000000..03ff431 --- /dev/null +++ b/input/fsh/instances/SOR Hierarchi/Princip/Version2 instances/SOR OU-L2 Healthcare Service.fsh @@ -0,0 +1,11 @@ +/* +Instance: Eer.Sor.OU.L2.HealthcareService.Organization-1.0 +InstanceOf: SORHealthcareService +Description: "An example of an SOR HI Organization." +* id = "Eer.Sor.OU.L2.HealthcareService.Organization-1.0" +* identifier.value = "Eer.Sor.OU.L2.HealthcareService.Organization-1.0" +* name = "Eer.Sor.OU.L2.HealthcareService.Organization-1.0" +* providedBy = Reference(Organization/Eer.Sor.OU.L2.Facility.Organization-1.0) +* type = #359 +* specialty = #394602002 +*/ \ No newline at end of file diff --git a/input/fsh/instances/devices/eerDevices.fsh b/input/fsh/instances/devices/eerDevices.fsh new file mode 100644 index 0000000..34a5401 --- /dev/null +++ b/input/fsh/instances/devices/eerDevices.fsh @@ -0,0 +1,61 @@ +Instance: EerDeviceAP-MultiMedAP +InstanceOf: EerDeviceAP +Description: "EerDeviceAP-MultiMedAP" +* id = "EerDeviceAP-MultiMedAP" +* identifier.value = "EerDeviceAP-MultiMedAP" +* definition = Reference("http://medcomehmi.dk/ig/dk-ehmi-eer/StructureDefinition/EerEndpointDeviceDefinitionAP") +* status = #active +* deviceName.name = "MultiMedAP" +* deviceName.type = #manufacturer-name +* manufacturer = "MultiMed" + +Instance: EerDeviceAP-BizKitAP +InstanceOf: EerDeviceAP +Description: "EerDeviceAP-BizKitAP" +* id = "EerDeviceAP-BizKitAP" +* identifier.value = "EerDeviceAP-BizKitAP" +* definition = Reference("StructureDefinition/EerEndpointDeviceDefinitionAP") +* status = #active +* deviceName.name = "BizKitAP" +* deviceName.type = #manufacturer-name +* manufacturer = "BizKit" + +Instance: EerDeviceMSH-MultiMedMSH +InstanceOf: EerDeviceMSH +Description: "EerDeviceMSH-MultiMedMSH" +* identifier.value = "EerDeviceMSH-MultiMedMSH" +* definition = Reference("http://medcomehmi.dk/ig/dk-ehmi-eer/StructureDefinition/EerEndpointDeviceDefinitionMSH") +* status = #active +* deviceName.name = "MultiMedMSH" +* deviceName.type = #manufacturer-name +* manufacturer = "MultiMed" + +Instance: EerDeviceMSH-NovaxEUA +InstanceOf: EerDeviceEUA +Description: "EerDeviceEUA-NovaxEUA" +* identifier.value = "EerDeviceEUA-NovaxEUA" +* definition = Reference("http://medcomehmi.dk/ig/dk-ehmi-eer/StructureDefinition/EerEndpointDeviceDefinitionEUA") +* status = #active +* deviceName.name = "NovaxEUA" +* deviceName.type = #manufacturer-name +* manufacturer = "Novax" + +Instance: EerDeviceMSH-SystematicMSH +InstanceOf: EerDeviceMSH +Description: "EerDeviceMSH-SystematicMSH" +* identifier.value = "EerDeviceMSH-SystematicMSH" +* definition = Reference("http://medcomehmi.dk/ig/dk-ehmi-eer/StructureDefinition/EerEndpointDeviceDefinitionMSH") +* status = #active +* deviceName.name = "SystematicMSH" +* deviceName.type = #manufacturer-name +* manufacturer = "Systematic" + +Instance: EerDeviceMSH-SystematicCura +InstanceOf: EerDeviceEUA +Description: "EerDeviceEUA-SystematicCura" +* identifier.value = "EerDeviceEUA-SystematicCura" +* definition = Reference("http://medcomehmi.dk/ig/dk-ehmi-eer/StructureDefinition/EerEndpointDeviceDefinitionEUA") +* status = #active +* deviceName.name = "Systematic Cura" +* deviceName.type = #manufacturer-name +* manufacturer = "Systematic" diff --git a/input/fsh/instances/endpoints/EerEndpoint_Messaging_eDeliveryFhir.01.fsh b/input/fsh/instances/endpoints/EerEndpoint_Messaging_eDeliveryFhir.01.fsh new file mode 100644 index 0000000..dfdf713 --- /dev/null +++ b/input/fsh/instances/endpoints/EerEndpoint_Messaging_eDeliveryFhir.01.fsh @@ -0,0 +1,13 @@ +Instance: EerEndpoint-Messaging-eDeliveryFhir.01 +InstanceOf: EerEndpointMessagingEdeliveryFhir +Description: "An example of an EerEndpointMessagingEdeliveryFhir." +* id = "EerEndpoint-Messaging-eDeliveryFhir.01" +* identifier.value = "EerEndpoint-Messaging-eDeliveryFhir.01" +//* identifier.use = "official" +* status = #active +* managingOrganization = Reference(Organization/EER.SOR-HI.01) +* period.start = "2023-01-01" +* period.end = "2024-01-01" +* address = "http://www.eDeliveryAccessPoint.dk/fhir" +* payloadMimeType = #text/plain +* payloadType = $EerEerMedComMessageDefinitionUri#urn:dk:healthcare:medcom:messaging:fhir:structuredefinition:acknowledgement:2.0 diff --git a/input/fsh/sor-affiliate.fsh b/input/fsh/sor-affiliate.fsh deleted file mode 100644 index 879ebbc..0000000 --- a/input/fsh/sor-affiliate.fsh +++ /dev/null @@ -1,14 +0,0 @@ -Profile: SOROrganizationAffiliation -Parent: MCSDOrganizationAffiliation -Id: medcom.sor.OrganizationAffiliation -Title: "SOR Organization Affiliation" -Description: """ -A profile on the OrganizationAffiliation resource for SOR.""" - -Profile: SOROrganizationAffiliationDocShare -Parent: MCSDOrganizationAffiliationDocShare -Id: medcom.sor.OrganizationAffiliation.DocShare -Title: "SOR Organization Affiliation DocumentSharing" -Description: """ -A profile on the OrganizationAffiliation resource for SOR in Document Sharing. Karen's Cross, when expanded to either/or a service that translates protocols, or a proxy that mediates network communication. -""" \ No newline at end of file diff --git a/input/fsh/sor-example.fsh b/input/fsh/sor-example.fsh deleted file mode 100644 index 39f29c7..0000000 --- a/input/fsh/sor-example.fsh +++ /dev/null @@ -1,222 +0,0 @@ -/*// jurisdiction pair - -Instance: SORJurisdictionOrganization-Example -InstanceOf: SORJurisdictionOrganization -Title: "Example SOR Jurisdiction Organization" -Description: "Organization resource for an example SOR Jurisdiction" -Usage: #example -* name = "SORJurisdictionOrganization-Example" -* active = true -* type[jurisdiction] = MCSDOrganizationLocationTypes#jurisdiction - -Instance: SORJurisdictionLocation-Example -InstanceOf: SORJurisdictionLocation -Title: "Example SOR Jurisdiction Location" -Description: "Location resource for an example SOR Jurisdiction" -Usage: #example -* name = "SORJurisdictionLocation-Example" -* status = #active -* managingOrganization = Reference(SORJurisdictionOrganization-Example) -* physicalType = http://terminology.hl7.org/CodeSystem/location-physical-type#jdn -* type[jurisdiction] = MCSDOrganizationLocationTypes#jurisdiction - -// another department - -Instance: SOROrganization-ExamplePartner -InstanceOf: SOROrganization -Title: "Example Partner Organization" -Description: "Example Organization for a Partner Organization" -Usage: #example -* name = "Organization-ExamplePartner" -* active = true -* type[+] = http://terminology.hl7.org/CodeSystem/organization-type#govt - -// Hierarchy Code System Example -CodeSystem: SORExampleHierarchy -Id: SORexample-hierarchy -Title: "SOR Example Hierarchy Code System" -Description: "An example vocabulary of hierarchies." -* ^caseSensitive = false -* ^content = #complete -* ^experimental = true -// * ^url = http://example.org/IHE/CodeSystem/SORexample-hierarchy -* #supply "Supply Chain" -* #admin "Administrative" - -// facility pair which is part of a jurisdiction and has one other external org attached - -Instance: SORFacilityOrganization-Example -InstanceOf: SORFacilityOrganization -Title: "Example SOR Facility Organization" -Description: "Organization resource for an example SOR Facility" -Usage: #example -* name = "SORFacilityOrganization-Example" -* active = true -* type[facility] = MCSDOrganizationLocationTypes#facility -* partOf = Reference(SORJurisdictionOrganization-Example) - -Instance: SORFacilityOrganizationAffiliation-Example -InstanceOf: SOROrganizationAffiliation -Title: "Example SOR Facility Admin Organization Affiliation" -Description: "Organization Affiliation resource for an example administrative relationship for a facility." -Usage: #example -* active = true -* organization = Reference(SOROrganization-ExamplePartner) -* participatingOrganization = Reference(SORFacilityOrganization-Example) -* code = SORExampleHierarchy#admin - -Instance: SORFacilityLocation-Example -InstanceOf: SORFacilityLocation -Title: "Example SOR Facility Location" -Description: "Location resource for an example SOR Facility" -Usage: #example -* name = "SORFacilityLocation-Example" -* status = #active -* managingOrganization = Reference(SORFacilityOrganization-Example) -* partOf = Reference(SORJurisdictionLocation-Example) -* physicalType = http://terminology.hl7.org/CodeSystem/location-physical-type#bu -* type[facility] = MCSDOrganizationLocationTypes#facility -* type[service] = http://terminology.hl7.org/CodeSystem/v3-RoleCode#HOSP - -Instance: SORLocation-Example -InstanceOf: SORLocation -Title: "Example SOR Location" -Description: "Location resource for an example of an SOR Location (Ward)" -Usage: #example -* name = "SORLocation-Example" -* status = #active -* partOf = Reference(SORFacilityLocation-Example) -* type[+] = http://terminology.hl7.org/CodeSystem/v3-RoleCode#RNEU -* physicalType = http://terminology.hl7.org/CodeSystem/location-physical-type#wa - -Instance: SORLocationDistance-Example -InstanceOf: SORLocationDistance -Title: "Example SOR Location with Distance Option" -Description: "Location resource for an example of an SOR Location with Distance Option" -Usage: #example -* name = "SORLocationDistance-Example" -* status = #active -* type[+] = http://terminology.hl7.org/CodeSystem/v3-RoleCode#HOSP -* physicalType = http://terminology.hl7.org/CodeSystem/location-physical-type#bu -* position.latitude = -1.46929510804737 -* position.longitude = -78.81700744576973 - -// service, role, practitioner - -Instance: SORHealthcareService-Example -InstanceOf: SORHealthcareService -Title: "Example SOR HealthcareService" -Description: "HealthcareService resource example for SOR." -Usage: #example -* name = "ANC" -* type = http://terminology.hl7.org/CodeSystem/service-type#124 "General Practice" -* location = Reference(SORFacilityLocation-Example) - -Instance: SORPractitionerRole-Example -InstanceOf: SORPractitionerRole -Title: "Example SOR PractitionerRole" -Description: "PractitionerRole resource example for SOR." -Usage: #example -* code = http://terminology.hl7.org/CodeSystem/practitioner-role#nurse -* location = Reference(SORFacilityLocation-Example) -* healthcareService = Reference(SORHealthcareService-Example) -* organization = Reference(SORFacilityOrganization-Example) -* practitioner = Reference(SORPractitioner-Example) - -Instance: SORPractitioner-Example -InstanceOf: SORPractitioner -Title: "Example SOR Practitioner" -Description: "Practitioner resource example for SOR." -Usage: #example -* name.text = "John Galt" - -// bundler - -Instance: Example-SOR -InstanceOf: Bundle -Title: "Example Bundle of SOR Resources" -Description: "Example Bundle of Core SOR Resources." -Usage: #example -* type = #transaction - - -* entry[+].fullUrl = "http://www.example.org/fhir/Organization/SORJurisdictionOrganization-Example" -* entry[=].request.url = "Organization/SORJurisdictionOrganization-Example" -* entry[=].request.method = #PUT -* entry[=].resource = SORJurisdictionOrganization-Example - -* entry[+].fullUrl = "http://www.example.org/fhir/Location/SORJurisdictionLocation-Example" -* entry[=].request.url = "Location/SORJurisdictionLocation-Example" -* entry[=].request.method = #PUT -* entry[=].resource = SORJurisdictionLocation-Example - -* entry[+].fullUrl = "http://www.example.org/fhir/Organization/SOROrganization-ExamplePartner" -* entry[=].request.url = "Organization/SOROrganization-ExamplePartner" -* entry[=].request.method = #PUT -* entry[=].resource = SOROrganization-ExamplePartner - -* entry[+].fullUrl = "http://www.example.org/fhir/Organization/SORFacilityOrganization-Example" -* entry[=].request.url = "Organization/SORFacilityOrganization-Example" -* entry[=].request.method = #PUT -* entry[=].resource = SORFacilityOrganization-Example - -* entry[+].fullUrl = "http://www.example.org/fhir/Location/SORFacilityLocation-Example" -* entry[=].request.url = "Location/SORFacilityLocation-Example" -* entry[=].request.method = #PUT -* entry[=].resource = SORFacilityLocation-Example - -* entry[+].fullUrl = "http://www.example.org/fhir/HealthcareService/SORHealthcareService-Example" -* entry[=].request.url = "HealthcareService/SORHealthcareService-Example" -* entry[=].request.method = #PUT -* entry[=].resource = SORHealthcareService-Example - -* entry[+].fullUrl = "http://www.example.org/fhir/PractitionerRole/SORPractitionerRole-Example" -* entry[=].request.url = "PractitionerRole/SORPractitionerRole-Example" -* entry[=].request.method = #PUT -* entry[=].resource = SORPractitionerRole-Example - -* entry[+].fullUrl = "http://www.example.org/fhir/Practitioner/SORPractitioner-Example" -* entry[=].request.url = "Practitioner/SORPractitioner-Example" -* entry[=].request.method = #PUT -* entry[=].resource = SORPractitioner-Example -/* -* entry[+].fullUrl = "http://www.example.org/fhir/OrganizationAffiliation/ex-OrgAff" -* entry[=].request.url = "OrganizationAffiliation/ex-OrgAff" -* entry[=].request.method = #PUT -* entry[=].resource = ex-OrgAff - -* entry[+].fullUrl = "http://www.example.org/fhir/Organization/ex-OrgA" -* entry[=].request.url = "Organization/ex-OrgA" -* entry[=].request.method = #PUT -* entry[=].resource = ex-OrgA - -* entry[+].fullUrl = "http://www.example.org/fhir/Organization/ex-OrgB" -* entry[=].request.url = "Organization/ex-OrgB" -* entry[=].request.method = #PUT -* entry[=].resource = ex-OrgB - -* entry[+].fullUrl = "http://www.example.org/fhir/Organization/ex-OrgC" -* entry[=].request.url = "Organization/ex-OrgC" -* entry[=].request.method = #PUT -* entry[=].resource = ex-OrgC - -* entry[+].fullUrl = "http://www.example.org/fhir/OrganizationAffiliation/ex-OrgAffC" -* entry[=].request.url = "OrganizationAffiliation/ex-OrgAffC" -* entry[=].request.method = #PUT -* entry[=].resource = ex-OrgAffC - -* entry[+].fullUrl = "http://www.example.org/fhir/Endpoint/ex-endpointXCAquery" -* entry[=].request.url = "Endpoint/ex-endpointXCAquery" -* entry[=].request.method = #PUT -* entry[=].resource = ex-endpointXCAquery - -* entry[+].fullUrl = "http://www.example.org/fhir/Endpoint/ex-endpointXCAretrieve" -* entry[=].request.url = "Endpoint/ex-endpointXCAretrieve" -* entry[=].request.method = #PUT -* entry[=].resource = ex-endpointXCAretrieve - -* entry[+].fullUrl = "http://www.example.org/fhir/Endpoint/ex-endpointDicom" -* entry[=].request.url = "Endpoint/ex-endpointDicom" -* entry[=].request.method = #PUT -* entry[=].resource = ex-endpointDicom -*/ \ No newline at end of file diff --git a/input/fsh/sor-facility.fsh b/input/fsh/sor-facility.fsh deleted file mode 100644 index b39717c..0000000 --- a/input/fsh/sor-facility.fsh +++ /dev/null @@ -1,11 +0,0 @@ -Profile: SORFacilityOrganization -Parent: MCSDFacilityOrganization -Id: MedCom.SOR.FacilityOrganization -Title: "SOR Facility Organization" -Description: """ MedCom.SOR.FacilityOrganization """ - -Profile: SORFacilityLocation -Parent: MCSDFacilityLocation -Id: MedCom.SOR.FacilityLocation -Title: "SOR Facility Location" -Description: """ MedCom.SOR.FacilityLocation """ diff --git a/input/fsh/sor-healthcareservice.fsh b/input/fsh/sor-healthcareservice.fsh deleted file mode 100644 index 1a80e33..0000000 --- a/input/fsh/sor-healthcareservice.fsh +++ /dev/null @@ -1,7 +0,0 @@ -Profile: SORHealthcareService -Parent: MCSDHealthcareService -Id: medcom.sor.HealthcareService -Title: "SOR HealthcareService" -Description: """ -A profile on the HealthcareService resource for SOR. -""" diff --git a/input/fsh/sor-jurisdiction.fsh b/input/fsh/sor-jurisdiction.fsh deleted file mode 100644 index 7302624..0000000 --- a/input/fsh/sor-jurisdiction.fsh +++ /dev/null @@ -1,13 +0,0 @@ -Profile: SORJurisdictionOrganization -Parent: MCSDJurisdictionOrganization -Id: MedCom.SOR.JurisdictionOrganization -Title: "SOR Jurisdiction Organization" -Description: """ MedCom.SOR.JurisdictionOrganization """ -* type from ehmi-sor-organization-type-valueset -* type = $EHMISOROrganizationType#IE (exactly) - -Profile: SORJurisdictionLocation -Parent: MCSDJurisdictionLocation -Id: MedCom.SOR.JurisdictionLocation -Title: "SOR Jurisdiction Location" -Description: """ MedCom.SOR.JurisdictionLocation """ diff --git a/input/fsh/sor-location.fsh b/input/fsh/sor-location.fsh deleted file mode 100644 index 737a608..0000000 --- a/input/fsh/sor-location.fsh +++ /dev/null @@ -1,13 +0,0 @@ -Profile: SORLocation -Parent: MCSDLocation -Id: medcom.sor.Location -Title: "SOR Location" -Description: "A profile on the Location resource for SOR." - -Profile: SORLocationDistance -Parent: MCSDLocationDistance -Id: medcom.sor.LocationDistance -Title: "SOR Location with Distance" -Description: """ -A profile on the SOR Location resource for distance searches. -""" \ No newline at end of file diff --git a/input/fsh/sor-organization.fsh b/input/fsh/sor-organization.fsh index 668f33f..d3bb7fc 100644 --- a/input/fsh/sor-organization.fsh +++ b/input/fsh/sor-organization.fsh @@ -1,131 +1,146 @@ -Profile: EHMISOROrganization +Profile: EerSorOrganization Parent: MCSDOrganization -Id: EHMI.SOR.Organization -Title: "EHMI SOR Organization" -Description: """ EHMI SOR General Organization """ -* identifier ^slicing.discriminator.type = #value +Id: Eer.Sor.Organization +Title: "EER SOR Organization" +Description: """ EER SOR General Organization """ +* identifier ^slicing.discriminator.type = #pattern * ^slicing.discriminator.path = type * ^slicing.rules = #open //#closed eller #open * identifier contains SOR 1..1 MS SU + and MunicipalityCode 0..1 MS SU * identifier[SOR].use = #official -* identifier[SOR].type from $EHMISORorganizationIdentierTypeVS -* identifier[SOR].type = $EHMISORorganizationIdentierType#SOR (exactly) +* identifier[SOR].type from $EerSorOrganizationIdentierTypeVS +* identifier[SOR].type = $EerSorOrganizationIdentierType#SORID (exactly) * identifier[SOR].system = "1.2.208.176.1.1" (exactly) +* identifier[MunicipalityCode].use = #official +* identifier[MunicipalityCode].value from $EerSorMunicipalityCodeVS +* identifier[MunicipalityCode].type from $EerSorOrganizationIdentierTypeVS +* identifier[MunicipalityCode].system = $EerSorMunicipalityCode * type ^slicing.discriminator.type = #value * ^slicing.discriminator.path = coding.code * ^slicing.rules = #open //#closed eller #open * type contains SOR-Hierarchy 1..1 MS SU and SOR-UnitType 0..1 SU -* type[SOR-Hierarchy].coding.code from $EHMISOROrganizationTypeVS -* type[SOR-Hierarchy].coding.system = $EHMISOROrganizationType -* type[SOR-UnitType].coding.code from $EHMISORUnitTypeVS -* type[SOR-UnitType].coding.system = $EHMISORUnitType -//* endpoint 0..0 + and EerSorOrganizationType 0..1 MS SU + and EerSorIOOrganizationType 0..1 MS SU +* type[SOR-Hierarchy].coding.code from $EerSorOrganizationTypeVS +* type[SOR-Hierarchy].coding.system = $EerSorOrganizationType +* type[SOR-UnitType].coding.code from $EerSorUnitTypeVS +* type[SOR-UnitType].coding.system = $EerSorUnitType +* type[EerSorOrganizationType].coding.code from $EerSorOrganizationTypeVS +* type[EerSorOrganizationType].coding.system = $EerSorOrganizationType +* type[EerSorIOOrganizationType].coding.code from $EerSorIOOrganizationTypeVS +* type[EerSorIOOrganizationType].coding.system = $EerSorIOOrganizationType +* extension contains eer-dk-eua-system-extension named eua-system 0..* MS +* endpoint 0..* +* endpoint only Reference(EerEndpointMessagingEdelivery) -Profile: EHMISORIOOrganization -Parent: EHMISOROrganization -Id: EHMI.SOR.InstitutionOwner.Organization -Title: "EHMI SOR Institution Owner Organization" -Description: """ EHMI SOR Institution Owner Organization IO (DK:IE) """ +/* +Profile: EerSorIOOrganization +Parent: EerSorOrganization +Id: Eer.Sor.InstitutionOwner.Organization +Title: "EER SOR Institution Owner Organization" +Description: """ EER SOR Institution Owner Organization IO (DK:IE) """ * type ^slicing.discriminator.type = #value * ^slicing.discriminator.path = coding.code * ^slicing.rules = #open //#closed eller #open * type contains - EHMISORIOOrganizationType 1..1 MS SU -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#IE (exactly) -* type[EHMISORIOOrganizationType].coding.code from $EHMISORIOOrganizationTypeVS -* type[EHMISORIOOrganizationType].coding.system = $EHMISORIOOrganizationType + EerSorOrganizationType 1..1 MS SU +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#IE (exactly) +* type[EerSorOrganizationType].coding.code from $EerSorOrganizationTypeVS +* type[EerSorOrganizationType].coding.system = $EerSorOrganizationType * partOf 0..0 * endpoint 0..0 -Profile: EHMISORMunicipalityOrganization -Parent: EHMISORIOOrganization -Id: EHMI.SOR.InstitutionOwner.Municipality.Organization -Title: "EHMI SOR Institution Owner Municipality Organization" -Description: """ EHMI SOR Institution Owner Municipality Organization IO (DK:IE) """ -//* type[SOR-Hierarchy] = $EHMISOROrganizationType#IE (exactly) +Profile: EerSorMunicipalityOrganization +Parent: EerSorOrganization +Id: Eer.Sor.InstitutionOwner.Municipality.Organization +Title: "EER SOR Institution Owner Municipality Organization" +Description: """ EER SOR Institution Owner Municipality Organization IO (DK:IE) """ +//* type[SOR-Hierarchy] = $EerSorOrganizationType#IE (exactly) * identifier ^slicing.discriminator.type = #value * ^slicing.discriminator.path = type * ^slicing.rules = #open //#closed eller #open * identifier contains MunicipalityCode 1..1 MS SU * identifier[MunicipalityCode].use = #official -* identifier[MunicipalityCode].value from $EHMISORMunicipalityCodeVS -* identifier[MunicipalityCode].type from $EHMISORorganizationIdentierTypeVS -* identifier[MunicipalityCode].system = $EHMISORMunicipalityCode -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#IE (exactly) -* type[EHMISORIOOrganizationType].coding.code = $EHMISORIOOrganizationType#Municipality (exactly) -* type[SOR-UnitType].coding.code = $EHMISORUnitType#kommune (exactly) +* identifier[MunicipalityCode].value from $EerSorMunicipalityCodeVS +* identifier[MunicipalityCode].type from $EerSorOrganizationIdentierTypeVS +* identifier[MunicipalityCode].system = $EerSorMunicipalityCode +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#IE (exactly) +* type[EerSorOrganizationType].coding.code = $EerSorOrganizationType#Municipality (exactly) +* type[SOR-UnitType].coding.code = $EerSorUnitType#kommune (exactly) -Profile: EHMISORRegionalOrganization -Parent: EHMISORIOOrganization -Id: EHMI.SOR.InstitutionOwner.Regional.Organization -Title: "EHMI SOR Institution Owner Regional Organization" -Description: """ EHMI SOR Institution Owner Regional Organization IO (DK:IE) """ -///* type[SOR-Hierarchy] = $EHMISOROrganizationType#IE (exactly) +Profile: EerSorRegionalOrganization +Parent: EerSorOrganization +Id: Eer.Sor.InstitutionOwner.Regional.Organization +Title: "EER SOR Institution Owner Regional Organization" +Description: """ EER SOR Institution Owner Regional Organization IO (DK:IE) """ +///* type[SOR-Hierarchy] = $EerSorOrganizationType#IE (exactly) * identifier ^slicing.discriminator.type = #value * ^slicing.discriminator.path = type * ^slicing.rules = #open //#closed eller #open * identifier contains RegionalCode 1..1 MS SU * identifier[RegionalCode].use = #official -* identifier[RegionalCode].value from $EHMISORRegionalCodeVS -* identifier[RegionalCode].type from $EHMISORorganizationIdentierTypeVS -* identifier[RegionalCode].system = $EHMISORRegionalCode -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#IE (exactly) -* type[EHMISORIOOrganizationType].coding.code = $EHMISORIOOrganizationType#Region (exactly) -* type[SOR-UnitType].coding.code = $EHMISORUnitType#region (exactly) +* identifier[RegionalCode].value from $EerSorRegionalCodeVS +* identifier[RegionalCode].type from $EerSorOrganizationIdentierTypeVS +* identifier[RegionalCode].system = $EerSorRegionalCode +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#IE (exactly) +* type[EerSorOrganizationType].coding.code = $EerSorOrganizationType#Region (exactly) +* type[SOR-UnitType].coding.code = $EerSorUnitType#region (exactly) -Profile: EHMISORHIOrganization -Parent: EHMISOROrganization -Id: EHMI.SOR.HealthcareInstitution.Organization -Title: "EHMI SOR Healthcare Institution Organization" -Description: """ EHMI SOR Healthcare Institution Organization HI (DK:SI) """ -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#SI (exactly) +Profile: EerSorHIOrganization +Parent: EerSorOrganization +Id: Eer.Sor.HealthcareInstitution.Organization +Title: "EER SOR Healthcare Institution Organization" +Description: """ EER SOR Healthcare Institution Organization HI (DK:SI) """ +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#SI (exactly) //* partOf = Reference(Organization) * partOf 1..1 MS /* Invariant: dk-ehmi-org-1 -Description: "EHMISORHIOrganization.partOf SHALL be of type IO" +Description: "EerSorHIOrganization.partOf SHALL be of type IO" Severity: #error -Expression: "partOf only Reference({Organization/EHMISORIOOrganization})" +Expression: "partOf only Reference({Organization/EerSorIOOrganization})" //XPath: "f:given or f:family" */ - -Profile: EHMISORHospitalOrganization -Parent: EHMISORHIOrganization -Id: EHMI.SOR.HealthcareInstitution.Hospital.Organization -Title: "EHMI SOR Healthcare Institution Hospital Organization" -Description: """ EHMI SOR Healthcare Institution Hospital Organization HI (DK:SI) """ +/* +Profile: EerSorHospitalOrganization +Parent: EerSorOrganization +Id: Eer.Sor.HealthcareInstitution.Hospital.Organization +Title: "EER SOR Healthcare Institution Hospital Organization" +Description: """ EER SOR Healthcare Institution Hospital Organization HI (DK:SI) """ * type ^slicing.discriminator.type = #value * ^slicing.discriminator.path = coding.code * ^slicing.rules = #open //#closed eller #open * type contains ClinicalAdministrativeHierarchy 1..1 MS SU -* type[SOR-Hierarchy] = $EHMISOROrganizationType#SI (exactly) -* type[ClinicalAdministrativeHierarchy].coding.code from ehmi-sor-clinical-administrative-hierarchy-valueset -* type[ClinicalAdministrativeHierarchy].coding.code = $EHMISORClinicalAdministrativeHierarchy#Hospital (exactly) -* type[ClinicalAdministrativeHierarchy].coding.system = $EHMISORClinicalAdministrativeHierarchy +* type[SOR-Hierarchy] = $EerSorOrganizationType#SI (exactly) +* type[ClinicalAdministrativeHierarchy].coding.code from eer-sor-clinical-administrative-hierarchy-valueset +* type[ClinicalAdministrativeHierarchy].coding.code = $EerSorClinicalAdministrativeHierarchy#Hospital (exactly) +* type[ClinicalAdministrativeHierarchy].coding.system = $EerSorClinicalAdministrativeHierarchy -Profile: EHMISOROUOrganization -Parent: EHMISOROrganization -Id: EHMI.SOR.OrganizationalUnit.Organization -Title: "EHMI SOR Organizational Unit" -Description: """ EHMI SOR Organizational Unit OU (DK:OE) """ -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE (exactly) +Profile: EerSorOUOrganization +Parent: EerSorOrganization +Id: Eer.Sor.OrganizationalUnit.Organization +Title: "EER SOR Organizational Unit" +Description: """ EER SOR Organizational Unit OU (DK:OE) """ +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE (exactly) -Profile: EHMISORHospitalOUOrganization -Parent: EHMISOROUOrganization -Id: EHMI.SOR.HospitalOUOrganization.Organization -Title: "EHMI SOR Organizational Unit" -Description: """ EHMI SOR Organizational Unit OU (DK:OE) """ +Profile: EerSorHospitalOUOrganization +Parent: EerSorOrganization +Id: Eer.Sor.HospitalOUOrganization.Organization +Title: "EER SOR Organizational Unit" +Description: """ EER SOR Organizational Unit OU (DK:OE) """ * type ^slicing.discriminator.type = #value * ^slicing.discriminator.path = coding.code * ^slicing.rules = #open //#closed eller #open * type contains ClinicalAdministrativeHierarchy 1..1 MS SU -* type[SOR-Hierarchy].coding.code = $EHMISOROrganizationType#OE (exactly) -//* type[ClinicalAdministrativeHierarchy] = $EHMISORClinicalAdministrativeHierarchy#Afdeling +* type[SOR-Hierarchy].coding.code = $EerSorOrganizationType#OE (exactly) +//* type[ClinicalAdministrativeHierarchy] = $EerSorClinicalAdministrativeHierarchy#Afdeling +*/ \ No newline at end of file diff --git a/input/fsh/sor-practitioner.fsh b/input/fsh/sor-practitioner.fsh deleted file mode 100644 index 56a344d..0000000 --- a/input/fsh/sor-practitioner.fsh +++ /dev/null @@ -1,15 +0,0 @@ -Profile: SORPractitioner -Parent: MCSDPractitioner -Id: medcom.sor.Practitioner -Title: "SOR Practitioner" -Description: """ -A profile on the Practitioner resource for SOR. -""" - -Profile: SORPractitionerRole -Parent: MCSDPractitionerRole -Id: medcom.sor.PractitionerRole -Title: "SOR PractitionerRole" -Description: """ -A profile on the PractitionerRole resource for SOR. -""" diff --git a/input/images-source/eerDiagramBasic.plantuml b/input/images-source/eerDiagramBasic.plantuml new file mode 100644 index 0000000..cbae59a --- /dev/null +++ b/input/images-source/eerDiagramBasic.plantuml @@ -0,0 +1,13 @@ +@startuml EER + +hide empty members + +class "Lokationsnummer" as Lokationsnummer <> +class "SorEnhed" as SorEnhed <> +class "Meddelelsestype" as Meddelelsestype <> + +SorEnhed --> Lokationsnummer : "har" +Lokationsnummer --> Meddelelsestype : "sender" +Lokationsnummer --> Meddelelsestype : "modtager" + +@enduml diff --git a/input/images-source/eerDiagramBasicEnhanced.plantuml b/input/images-source/eerDiagramBasicEnhanced.plantuml new file mode 100644 index 0000000..61baea2 --- /dev/null +++ b/input/images-source/eerDiagramBasicEnhanced.plantuml @@ -0,0 +1,17 @@ +@startuml EER + +hide empty members + +class "EerOrganization" as EerOrganization <> +class "EerEndpoint" as EerEndpoint <> +class "EerMessageType" as EerMessageType <> +class "EerDeviceEUA" as EerDeviceEUA <> +class "EerDeviceAP" as EerDeviceAP <> + +EerOrganization --> EerEndpoint : "has" +EerOrganization --> EerDeviceEUA : "is served by" +EerEndpoint --> EerMessageType : "sends" +EerEndpoint --> EerMessageType : "receives" +EerEndpoint --> EerDeviceAP : "is served by" + +@enduml diff --git a/input/images-source/eerDiagramWithMSH.plantuml b/input/images-source/eerDiagramWithMSH.plantuml new file mode 100644 index 0000000..055bdbd --- /dev/null +++ b/input/images-source/eerDiagramWithMSH.plantuml @@ -0,0 +1,22 @@ +@startuml EER + +hide empty members + +class "EerEndpoint" as EerEndpoint <> +class "EerSorOrganization" as EerOrganization <> +class "EerMessageDefinition" as EerMessageDefinition <> +class "EerDeviceEUA" as EerDeviceEUA <> +class "EerDeviceAP" as EerDeviceAP <> +class "EerDeviceMSH" as EerDeviceMSH <> + +EerOrganization --> EerEndpoint : "has" +EerOrganization --> EerDeviceEUA : "uses" +EerDeviceAP --> EerOrganization : "acts as Endpoint for" +EerDeviceAP --> EerEndpoint : "instanciates" +EerDeviceEUA --> EerMessageDefinition : "supports" +EerEndpoint --> EerMessageDefinition : "sends" +EerEndpoint --> EerMessageDefinition : "receives" +EerDeviceMSH --> EerOrganization : "supports (potentially)" +EerDeviceMSH --> EerEndpoint : "supports (potentially)" + +@enduml diff --git a/input/images-source/eerDiagramWithoutMSH.plantuml b/input/images-source/eerDiagramWithoutMSH.plantuml new file mode 100644 index 0000000..cf88393 --- /dev/null +++ b/input/images-source/eerDiagramWithoutMSH.plantuml @@ -0,0 +1,19 @@ +@startuml EER + +hide empty members + +class "EerEndpoint" as EerEndpoint <> +class "EerSorOrganization" as EerOrganization <> +class "EerMessageDefinition" as EerMessageDefinition <> +class "EerDeviceEUA" as EerDeviceEUA <> +class "EerDeviceAP" as EerDeviceAP <> + +EerOrganization --> EerEndpoint : "has" +EerOrganization --> EerDeviceEUA : "uses" +EerDeviceAP --> EerOrganization : "acts as Endpoint for" +EerDeviceAP --> EerEndpoint : "instanciates" +EerDeviceEUA --> EerMessageDefinition : "supports" +EerEndpoint --> EerMessageDefinition : "sends" +EerEndpoint --> EerMessageDefinition : "receives" + +@enduml diff --git a/input/images-source/eerToSMP.plantuml b/input/images-source/eerToSMP.plantuml new file mode 100644 index 0000000..c741efc --- /dev/null +++ b/input/images-source/eerToSMP.plantuml @@ -0,0 +1,16 @@ +@startuml SMP + +hide empty members + +class "EerOrganization" as EerOrganization <> +class "EerEndpoint" as EerEndpoint <> +class "EerMessageType" as EerMessageType <> +class "SMP" as SMP <> + +EerOrganization --> EerEndpoint : "has" +EerEndpoint --> EerMessageType : "receives" +EerOrganization --> SMP : "populates" +EerEndpoint --> SMP : "populates" +EerMessageType --> SMP : "populates" + +@enduml diff --git a/input/images-source/sorDiagramBasic.plantuml b/input/images-source/sorDiagramBasic.plantuml new file mode 100644 index 0000000..b85435a --- /dev/null +++ b/input/images-source/sorDiagramBasic.plantuml @@ -0,0 +1,17 @@ +@startuml EER + +hide empty members + +class "LokationsnummerEntitet" as LokationsnummerEntitet <> +class "Organisatorisk enhed" as SorEnhed <> +class "Meddelelsestype" as Meddelelsestype <> + +SorEnhed --> LokationsnummerEntitet : "har" +LokationsnummerEntitet --> Lokationsnummer : "har" +LokationsnummerEntitet --> ItFagsystem : "har" +LokationsnummerEntitet --> ItLeverandør : "har" +LokationsnummerEntitet --> VansLeverandør : "har" +LokationsnummerEntitet <-- Meddelelsestype : "kan sendes af" +LokationsnummerEntitet <-- Meddelelsestype : "kan modtages af" + +@enduml diff --git a/input/images/eas_1_1_getReceiverData.png b/input/images/eas_1_1_getReceiverData.png new file mode 100644 index 0000000..0c58555 Binary files /dev/null and b/input/images/eas_1_1_getReceiverData.png differ diff --git a/input/images/eas_1_1_getReceiverData_error1.png b/input/images/eas_1_1_getReceiverData_error1.png new file mode 100644 index 0000000..660625a Binary files /dev/null and b/input/images/eas_1_1_getReceiverData_error1.png differ diff --git a/input/images/eds_1_1_getDeviceDataBySorId&DeviceType.png b/input/images/eds_1_1_getDeviceDataBySorId&DeviceType.png new file mode 100644 index 0000000..92bec3b Binary files /dev/null and b/input/images/eds_1_1_getDeviceDataBySorId&DeviceType.png differ diff --git a/input/images/eds_1_1_getDeviceDataBySorId&DeviceType_error1.png b/input/images/eds_1_1_getDeviceDataBySorId&DeviceType_error1.png new file mode 100644 index 0000000..6fbd132 Binary files /dev/null and b/input/images/eds_1_1_getDeviceDataBySorId&DeviceType_error1.png differ diff --git a/input/images/eerDiagramWithMSH.png b/input/images/eerDiagramWithMSH.png new file mode 100644 index 0000000..bf79372 Binary files /dev/null and b/input/images/eerDiagramWithMSH.png differ diff --git a/input/images/eerDiagramWithoutMSH.png b/input/images/eerDiagramWithoutMSH.png new file mode 100644 index 0000000..0972926 Binary files /dev/null and b/input/images/eerDiagramWithoutMSH.png differ diff --git a/input/images/hr.png b/input/images/hr.png new file mode 100644 index 0000000..ce4d85a Binary files /dev/null and b/input/images/hr.png differ diff --git a/input/images/mCSDRelationships.png b/input/images/mCSDRelationships.png deleted file mode 100644 index a38bd60..0000000 Binary files a/input/images/mCSDRelationships.png and /dev/null differ diff --git a/input/pagecontent/EHMI-CSD-User-Stories.md b/input/pagecontent/EHMI-CSD-User-Stories.md index e3a422a..a410791 100644 --- a/input/pagecontent/EHMI-CSD-User-Stories.md +++ b/input/pagecontent/EHMI-CSD-User-Stories.md @@ -1,16 +1,16 @@ -# EHMI EHMI Endpoint Register User stories +# EHMI EER Endpoint Register User stories ### User stories i scope for produktionspilot -#### Forretningsejer af EHMI EHMI Endpoint Register (FCSD) +#### Forretningsejer af EHMI EER Endpoint Register (FCSD) ##### FCSD.1 i. Som FCSD - ii. Ønsker jeg at have en kanonisk datamodel for EHMI EHMI Endpoint Register + ii. Ønsker jeg at have en kanonisk datamodel for EHMI EER Endpoint Register - iii. Når jeg skal modellere og implementere EHMI EHMI Endpoint Register + iii. Når jeg skal modellere og implementere EHMI EER Endpoint Register ##### FCSD.2 @@ -54,7 +54,7 @@ iii. Når jeg skal agere som autoritative kilde for Sundhedsadresseringsservicen -#### Komponenten EHMI EHMI Endpoint Register (KCSD) +#### Komponenten EHMI EER Endpoint Register (KCSD) ##### KCSD.1 diff --git a/input/pagecontent/EHMI-User-Stories.md b/input/pagecontent/EHMI-User-Stories.md index c18f02c..9782068 100644 --- a/input/pagecontent/EHMI-User-Stories.md +++ b/input/pagecontent/EHMI-User-Stories.md @@ -1,8 +1,8 @@ -# EHMI EHMI Endpoint Register User stories +# EHMI EER Endpoint Register User stories ## User stories i scope for produktionspilot -### Forretningsejer af EHMI EHMI Endpoint Register (FPKR) +### Forretningsejer af EHMI EER Endpoint Register (FPKR) **FPKR.1** @@ -52,7 +52,7 @@ ii. Ønsker jeg i så vidt omfang som muligt at kunne genanvende eksisterende sn iii. Når jeg skal agere som autoritative kilde for sundhedsadresseringsservicen -### Komponenten EHMI EHMI Endpoint Register (KPKR) +### Komponenten EHMI EER Endpoint Register (KPKR) **KPKR.1** diff --git a/input/pagecontent/Endpoint.md b/input/pagecontent/Endpoint.md deleted file mode 100644 index 19fb5b1..0000000 --- a/input/pagecontent/Endpoint.md +++ /dev/null @@ -1,5 +0,0 @@ -# Facility - -(tbd) - -**Facility** – Facilities are physical care delivery sites such as hospitals, clinics, health outposts, physician offices, labs, pharmacies, etc. A Facility has a unique identifier, geographic attributes (address, geocode), contact attributes, attributes regarding its hours of operation, etc. Each Facility is defined by a pairing of Location and Organization. diff --git a/input/pagecontent/Facility.md b/input/pagecontent/Facility.md deleted file mode 100644 index 19fb5b1..0000000 --- a/input/pagecontent/Facility.md +++ /dev/null @@ -1,5 +0,0 @@ -# Facility - -(tbd) - -**Facility** – Facilities are physical care delivery sites such as hospitals, clinics, health outposts, physician offices, labs, pharmacies, etc. A Facility has a unique identifier, geographic attributes (address, geocode), contact attributes, attributes regarding its hours of operation, etc. Each Facility is defined by a pairing of Location and Organization. diff --git a/input/pagecontent/Healthcare-Service.md b/input/pagecontent/Healthcare-Service.md deleted file mode 100644 index 5320f15..0000000 --- a/input/pagecontent/Healthcare-Service.md +++ /dev/null @@ -1,5 +0,0 @@ -# HealthcareService - -(tbd) - -Each healthcare service has a unique identifier. Examples include surgical services, antenatal care services, or primary care services. The combination of a Healthcare Service offered at a Location may have specific attributes including contact person, hours of operation, etc. [See more](Healthcare-Service) diff --git a/input/pagecontent/Jurisdiction.md b/input/pagecontent/Jurisdiction.md deleted file mode 100644 index 180d4b2..0000000 --- a/input/pagecontent/Jurisdiction.md +++ /dev/null @@ -1,7 +0,0 @@ -# Jurisdiction - -(tbd) - -**Jurisdiction** – Jurisdictions are political administrative units or other territories over which authority is exercised. A Jurisdiction has a unique identifier, geographic attributes, etc. Jurisdictions include political administrative units such as village districts or regions. Each Jurisdiction is defined by a pairing of Location and Organization. - - **SOR IE Organization** – is reflected as a Jurisdiction instead of Organization diff --git a/input/pagecontent/Location.md b/input/pagecontent/Location.md deleted file mode 100644 index 71f37ff..0000000 --- a/input/pagecontent/Location.md +++ /dev/null @@ -1,5 +0,0 @@ -# Location - -(tbd) - -**Location** – Locations are physical places where care can be delivered such as facilities, buildings, wards, rooms, or vehicles. Locations also include jurisdictions such as a village districts or regions. A Location has a unique identifier and may have geographic attributes (address, geocode), attributes regarding its hours of operation, etc. Each Location may be related to one Organization. A location may have a hierarchical relationship with other locations. diff --git a/input/pagecontent/SOR-EER-mapping.md b/input/pagecontent/SOR-EER-mapping.md new file mode 100644 index 0000000..080def0 --- /dev/null +++ b/input/pagecontent/SOR-EER-mapping.md @@ -0,0 +1,52 @@ +# EER and SOR + +Traditionally messaging metadata for a SOR unit has been placed in SOR and SOR-EDI. + +EER replaces and reorganizes how these messaging metadata are represented. + +The following table gives and overview of how these messaging metadata are mapped and reorganized in EER: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SOREERLinkNotes
SOR-UnitEER-OrganizationEER-SOR-OrganizationNote, that this is EER-SOR-Organization representing the SOR-Unit is only carrying the most necessary information from SOR. It is not a complete representation of the SOR unit. It holds the relationship between the SOR-unit and the EER-Endpoint. Most importantly it will not carry the GLN-identifier as it has been moved to the Endpoint ressource
SOR-EDIEER-Endpoint with MedCom MessageDefinitions as payloadTypeEER-EndpointEER-Endpoint represents or hold relationsships to all metadata regarding an endpoint in EHMI. EER-Endpoint holds relationsships to all MedCom Messages through the references of payloadTypes (MedCom MessageDefinitions). A MedCom MessageDefinition is defined together with the FHIR Message Profile and is included in an IG
SOR-GLN (attribute)EER-EndpointEER-EndpointIn EHMI messaging it will hold SOR-GLN is now the primary identifier of an EER-Endpoint ressource
SOR-System (attribute)EER-DeviceEER-DeviceEER-Device represents the System, End-User Application (EUA), that operates for the organization on the endpoint. Only MedCom Certified Systems can appear as a EER-device
SOR-Network Supply System (attribute)EER-DeviceEER-DeviceEER-Device represents the network System, Message Service Handler (MSH) or eDelivery Access Point (AP), that operates for the organization on the endpoint. While SOR-System is the actal EUA, the SOR-Network is the more technical device that connects with the EHMI Network. Only MedCom Certified Systems can appear as a EER-device
xyLinkz
\ No newline at end of file diff --git a/input/pagecontent/eas-Use-case-1.md b/input/pagecontent/eas-Use-case-1.md new file mode 100644 index 0000000..f1b2c6a --- /dev/null +++ b/input/pagecontent/eas-Use-case-1.md @@ -0,0 +1,21 @@ +# Get Receiver metadata by SORID + +An End User Application, EUA, calls EAS to retrieve the necessary message address metadata information for a potential receiver of a message. The sequence diagram for this is as follows: + +1_1_getReceiverData_getReceivingOrganizationBySORId + +Initially, when EAS receives this request, the given organization id is validated, after which relevant organization information associated with the organization id is obtained from SOR. With this and the type of message to be sent, the EER Endpoint Register (EER) is then called to obtain the GLN number and other relevant information, and finally the response is packed and sent back to the caller of EAS. The message type is, again, needed in the second call to EAS, such that EAS can return the correct response for the given message type – it could for example be that the system of the general practitioner does not support receiving the particular type of message. + +This use case is conforming to this OperationDefinition: OperationDefinition-eas.getReceivingOrganizationBySORId + +# Error use cases for EAS use case 1 + +- error use case 4a - SOR-Information does not exist + +### Error use case 1a - EER-ReceiverData does not exist + +Should an error occur when calling EER to obtain the GLN number and other relevant information, an error response stating this is packed and returned to the caller of EAS as illustrated by: + +1_1_getReceiverData_error1_getReceivingOrganizationBySORId + + \ No newline at end of file diff --git a/input/pagecontent/ihepagecontent/ihe_ITI-90.md b/input/pagecontent/ihepagecontent/ihe_ITI-90.md deleted file mode 100644 index 853050f..0000000 --- a/input/pagecontent/ihepagecontent/ihe_ITI-90.md +++ /dev/null @@ -1,330 +0,0 @@ - -### 2:3.90.1 Scope - -The Find Matching Care Services transaction returns a list of matching care services resources based on the query sent. A Care Services Selective Consumer initiates a Find Matching Care Services transaction against a Care Services Selective Supplier. - -### 2:3.90.2 Actor Roles - -| **Actor** | **Role** | -| ----- | ---- | -| Care Services Selective Consumer | Requests a list of resources from the Care Services Selective Supplier based on query parameters | -| Care Services Selective Supplier | Accepts the query request and returns a list of matching resources | -{: .grid} - -### 2:3.90.3 Referenced Standards - - - HL7 FHIR standard Release 4 [http://hl7.org/fhir/R4/index.html](http://hl7.org/fhir/R4/index.html) - -### 2:3.90.4 Messages - -
-{%include ITI-90-seq.svg%} -
-
- -**Figure 2:3.90.4-1: Interaction Diagram** - -#### 2:3.90.4.1 Find Matching Care Services Request Message - -The Find Matching Care Services message is a FHIR search operation on the mCSD Resources. - -##### 2:3.90.4.1.1 Trigger Events - -A Care Services Selective Consumer triggers a Find Matching Care Services Request to a Care Services Selective Supplier according to the business rules for the query. These business rules are outside the scope of this transaction. - -##### 2:3.90.4.1.2 Message Semantics - -A Care Services Selective Consumer initiates a search request using HTTP GET or POST as defined at [http://hl7.org/fhir/R4/http.html#search](http://hl7.org/fhir/R4/http.html#search) on the mCSD Resources. The Care Services Selective Supplier shall support both GET and POST based searches. The query parameters are identified below. A Care Services Selective Consumer may query any combination or subset of the parameters. - -A Care Services Selective Supplier shall support responding to a request for both the JSON and the XML messaging formats as defined in FHIR. A Care Services Selective Consumer shall accept either the JSON or the XML messaging formats as defined in FHIR. See [ITI TF-2: Z.6](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.6-populating-the-expected-response-format) for more details. - -A Care Services Selective Supplier shall implement the parameters described below for the mCSD resources it supports. A Care Services Selective Supplier may choose to support additional query parameters beyond the subset listed below. Any additional query parameters supported shall be supported according to the core FHIR specification. - -See [ITI TF-2: Appendix W](https://profiles.ihe.net/ITI/TF/Volume2/ch-W.html) for informative implementation material for this transaction. - -###### 2:3.90.4.1.2.1 Common Parameters - -The Care Services Selective Supplier shall support the `:contains` and `:exact` modifiers in all of the string query parameters below. - -The Care Services Selective Supplier shall support the following search parameters as defined at [http://hl7.org/fhir/R4/search.html#all](http://hl7.org/fhir/R4/search.html#all). - -``` -_id -_lastUpdated -``` - -The Care Services Selective Supplier shall also support the following prefixes for the `_lastUpdated` parameter: `gt`, `lt`, `ge`, `le`, `sa`, and `eb`. - -###### 2:3.90.4.1.2.2 Organization Resource Message Semantics - -The Care Services Selective Supplier shall support the following search parameters on the Organization Resource as defined at [http://hl7.org/fhir/R4/organization.html#search](http://hl7.org/fhir/R4/organization.html#search). String parameter modifiers are defined at [http://hl7.org/fhir/R4/search.html#string](http://hl7.org/fhir/R4/search.html#string). - -``` -active -identifier -name -partof -type -_include=Organization.endpoint -_revInclude=Location:organization -_revInclude=OrganizationAffiliation:participating-organization -_revInclude=OrganizationAffiliation:primary-organization -``` - -###### 2:3.90.4.1.2.3 Location Resource Message Semantics - -The Care Services Selective Supplier shall support the following search parameters on the Location Resource as defined at [http://hl7.org/fhir/R4/location.html#search](http://hl7.org/fhir/R4/location.html#search). String parameter modifiers are defined at [http://hl7.org/fhir/R4/search.html#string](http://hl7.org/fhir/R4/search.html#string). - -``` -identifier -name -organization -partof -status -type -_include=Location:organization -``` - -###### 2:3.90.4.1.2.4 Practitioner Resource Message Semantics - -The Care Services Selective Supplier shall support the following search parameters on the Practitioner Resource as defined at [http://hl7.org/fhir/R4/practitioner.html#search](http://hl7.org/fhir/R4/practitioner.html#search). String parameter modifiers are defined at [http://hl7.org/fhir/R4/search.html#string](http://hl7.org/fhir/R4/search.html#string). - -``` -active -identifier -name -given -family -``` - -###### 2:3.90.4.1.2.5 PractitionerRole Resource Message Semantics - -The Care Services Selective Supplier shall support the following search parameters on the PractitionerRole Resource as defined at [http://hl7.org/fhir/R4/practitionerrole.html#search] (http://hl7.org/fhir/R4/practitionerrole.html#search). - -``` -active -location -organization -practitioner -role -service -specialty -_include=PractitionerRole:practitioner -``` - -###### 2:3.90.4.1.2.6 HealthcareService Resource Message Semantics - -The Care Services Selective Supplier shall support the following search parameters on the HealthcareService Resource as defined at [http://hl7.org/fhir/R4/healthcareservice.html#search](http://hl7.org/fhir/R4/healthcareservice.html#search). String parameter modifiers are defined at [http://hl7.org/fhir/R4/search.html#string](http://hl7.org/fhir/R4/search.html#string). - -``` -active -identifier -location -name -organization -service-type -``` - -###### 2:3.90.4.1.2.7 Location Distance Option Message Semantics - -The Care Services Selective Supplier supporting the Location Distance Option shall support the following search parameters on the Location Resource as defined at [http://hl7.org/fhir/R4/location.html#search](http://hl7.org/fhir/R4/location.html#search). - -``` -near -``` - -###### 2:3.90.4.1.2.8 Endpoint Resource Message Semantics - -The Care Services Selective Supplier shall support the following search parameters on the Endpoint Resource as defined at [http://hl7.org/fhir/R4/endpoint.html#search](http://hl7.org/fhir/R4/endpoint.html#search). String parameter modifiers are defined at [http://hl7.org/fhir/R4/search.html#string](http://hl7.org/fhir/R4/search.html#string). - -``` -identifier -organization -status -``` - -###### 2:3.90.4.1.2.9 OrganizationAffiliation Resource Message Semantics - -The Care Services Selective Supplier shall support the following search parameters on the OrganizationAffiliation Resource as defined at [http://hl7.org/fhir/R4/organizationaffiliation.html#search](http://hl7.org/fhir/R4/organizationaffiliation.html#search). String parameter modifiers are defined at [http://hl7.org/fhir/R4/search.html#string](http://hl7.org/fhir/R4/search.html#string). - -``` -active -date -identifier -participating-organization -primary-organization -role -_include=OrganizationAffiliation.endpoint -``` - -##### 2:3.90.4.1.3 Expected Actions - -The Care Services Selective Supplier shall process the query to discover the resources that match the search parameters given, and return a response as per Section 2:3.90.4.2 or an error as per -[http://hl7.org/fhir/R4/search.html#errors](http://hl7.org/fhir/R4/search.html#errors). - -#### 2:3.90.4.2 Find Matching Care Services Response Message - -##### 2:3.90.4.2.1 Trigger Events - -The Care Services Selective Supplier sends the Find Matching Care Services Response to the Care Services Selective Consumer when results to the query are ready. - -##### 2:3.90.4.2.2 Message Semantics - -The Care Services Selective Supplier shall support the search response message as defined at [http://hl7.org/fhir/R4/http.html#search](http://hl7.org/fhir/R4/http.html#search) on the following Resources. - - - Organization, as defined at - [http://hl7.org/fhir/R4/organization.html](http://hl7.org/fhir/R4/organization.html) - - - Location, as defined at [http://hl7.org/fhir/R4/location.html](http://hl7.org/fhir/R4/location.html) - - - Practitioner, as defined at - [http://hl7.org/fhir/R4/practitioner.html](http://hl7.org/fhir/R4/practitioner.html) - - - PractitionerRole, as defined at - [http://hl7.org/fhir/R4/practitionerrole.html](http://hl7.org/fhir/R4/practitionerrole.html) - - - HealthcareService, as defined at - [http://hl7.org/fhir/R4/healthcareservice.html](http://hl7.org/fhir/R4/healthcareservice.html) - - - Endpoint, as defined at - [http://hl7.org/fhir/R4/endpoint.html](http://hl7.org/fhir/R4/endpoint.html) - - - OrganizationAffiliation, as defined at - [http://hl7.org/fhir/R4/organizationaffiliation.html](http://hl7.org/fhir/R4/organizationaffiliation.html) - -All References (Reference.reference element) to Resources defined in this transaction shall be populated with an accessible URL (see [https://www.hl7.org/fhir/references-definitions.html#Reference.reference](https://www.hl7.org/fhir/references-definitions.html#Reference.reference)), unless the referenced resource is not available at a URL known to the server. - -###### 2:3.90.4.2.2.1 FHIR Organization Resource Constraints - -A Care Services Selective Consumer may query on Organization Resources. A Care Services Selective Supplier shall return a Bundle of matching Organization Resources. The Organization Resource shall be further constrained as described in the [Organization Profile for mCSD](StructureDefinition-IHE.mCSD.Organization.html). - -A Care Services Selective Consumer may query on Organization Resources when working with Facilities. A Care Services Selective Supplier shall return a Bundle of matching Organization Resources when working with Facilities. The FHIR Organization Resource shall be further constrained as described in the [Organization for Facilities Profile for mCSD](StructureDefinition-IHE.mCSD.FacilityOrganization.html). - -A Care Services Selective Consumer may query on Organization Resources when working with Jurisdictions. A Care Services Selective Supplier shall return a Bundle of matching Organization Resources when working with Jurisdictions. The FHIR Organization Resource shall be further constrained as described in the [Organization for Jurisdictions Profile for mCSD](StructureDefinition-IHE.mCSD.JurisdictionOrganization.html). - -###### 2:3.90.4.2.2.2 FHIR Location Resource Constraints - -A Care Services Selective Consumer may query on Location Resources. A Care Services Selective Supplier shall return a Bundle of matching Location Resources. The Location Resource shall be further constrained as described in the [Location Profile for mCSD](StructureDefinition-IHE.mCSD.Location.html). - -When the resource is a Facility, the Location Resource shall be paired with an Organization Resource using the managingOrganization element in Location. A Care Services Selective Consumer may query on Location Resources when working with Facilities. A Care Services Selective Supplier shall return a Bundle of matching Location Resources when working with Facilities. The FHIR Location Resource shall be further constrained as described in the [Location for Facilities Profile for mCSD](StructureDefinition-IHE.mCSD.FacilityLocation.html). - -When the resource is a Jurisdiction, the Location Resource shall be paired with an Organization Resource using the managingOrganization element in Location. A Care Services Selective Consumer -may query on Location Resources when working with Jurisdictions. A Care Services Selective Supplier shall return a Bundle of matching Location Resources when working with Jurisdictions. The FHIR Location Resource shall be further constrained as described in the [Location for Jurisdictions Profile for mCSD](StructureDefinition-IHE.mCSD.JurisdictionLocation.html). - -When a geographic boundary is available for the Jurisdiction Location, the location-boundary-geojson extension defined at [http://hl7.org/fhir/extension-location-boundary-geojson.html](http://hl7.org/fhir/extension-location-boundary-geojson.html) shall be used to store this information. - -When supporting the Location Distance Option, the Location Resource shall be further constrained as described in the [Location with Distance Option Profile for mCSD](StructureDefinition-IHE.mCSD.LocationDistance.html). - -###### 2:3.90.4.2.2.3 FHIR Practitioner Resource Constraints - -A Care Services Selective Consumer may query on Practitioner Resources. A Care Services Selective Supplier shall return a Bundle of matching Practitioner Resources. The Practitioner Resource shall be further constrained as described in the [Practitioner Profile for mCSD](StructureDefinition-IHE.mCSD.Practitioner.html). - -###### 2:3.90.4.2.2.4 FHIR PractitionerRole Resource Constraints - -A Care Services Selective Consumer may query on PractitionerRole Resources. A Care Services Selective Supplier shall return a Bundle of matching PractitionerRole Resources. The PractitionerRole Resource shall be further constrained as described in the -[PractitionerRole Profile for mCSD](StructureDefinition-IHE.mCSD.PractitionerRole.html). - -###### 2:3.90.4.2.2.5 FHIR HealthcareService Resource Constraints - -A Care Services Selective Consumer may query on HealthcareService Resources. A Care Services Selective Supplier shall return a Bundle of matching HealthcareService Resources. The HealthcareService Resource shall be further constrained as described in the [HealthcareService Profile for mCSD](StructureDefinition-IHE.mCSD.HealthcareService.html). - -###### 2:3.90.4.2.2.6 FHIR OrganizationAffiliation Resource Constraints - -A Care Services Selective Consumer may query on OrganizationAffiliation Resources. A Care Services Selective Supplier shall return a Bundle of matching OrganizationAffiliation Resources. The OrganizationAffiliation Resource shall be further constrained as described in the [OrganizationAffiliation Profile for mCSD](StructureDefinition-IHE.mCSD.OrganizationAffiliation.html). - -When the OrganizationAffiliation contains an Endpoint to an IHE document sharing environment, it shall further be constrained as described in the [OrganizationAffiliation for Document Sharing Profile for mCSD](StructureDefinition-IHE.mCSD.OrganizationAffiliation.DocShare.html). - -###### 2:3.90.4.2.2.7 FHIR Endpoint Resource Constraints - -A Care Services Selective Consumer may query on Endpoint Resources. A Care Services Selective Supplier shall return a Bundle of matching Endpoint Resources. The Endpoint Resource shall be further constrained as described in the [Endpoint Profile for mCSD](StructureDefinition-IHE.mCSD.Endpoint.html). - -When the Endpoint is to an IHE document sharing environment, it shall further be constrained as described in the [Endpoint for Document Sharing Profile for mCSD](StructureDefinition-IHE.mCSD.Endpoint.DocShare.html). - - -##### 2:3.90.4.2.3 Expected Actions - -The Care Services Selective Consumer has received the response and continues with its workflow. - -#### 2:3.90.4.3 Retrieve Care Services Resource message -This message represents an HTTP GET from the Care Services Selective Consumer to the Care Services Selective Supplier and provides a mechanism for retrieving a single Care Services Resource with a known resource identifier. - -##### 2:3.90.4.3.1 Trigger Events -When the Care Services Selective Consumer possesses a Care Services Resource identifier (either through query, database lookup, or other mechanism) for which it requires additional or new information, it issues a Retrieve Care Services Resource interaction. - -##### 2:3.90.4.3.2 Message Semantics -The Retrieve Care Services Resource is conducted by executing an HTTP GET against the Care Services Selective Supplier’s Care Services Resource URL, providing the resource id of the resource being retrieved. The target is formatted as: - -``` GET [base]/[resource]/[resourceId]``` - -The Care Services Selective Supplier shall respond to this query by sending a single Care Services Resource instance. - -The `resourceId` included in the request always represents the unique identifier for the Resource within the scope of the URL. For example, while `http://example1.org/ihe/Practitioner/1` and `http://example2.com/ihe/Practitioner/1` both contain the same `[resourceId]`, they reference two different resource instances. - -Note: The use of "http" or "https" in URL does not override requirements to use TLS for security purposes. - -##### 2:3.90.4.3.3 Expected Actions -The Care Services Selective Supplier shall retrieve the record indicated by the Resource identifier on the HTTP GET supplied by the Care Services Selective Consumer. The Care Services Selective Supplier shall respond to the retrieve request as described by the following cases: - -**Case 1**: The Care Services Selective Supplier finds the care services record matching the `resourceId` sent in the HTTP request. - -`HTTP 200` (OK) is returned as the HTTP status code. - -A Care Services Resource is returned representing the result. - -**Case 2**: The Care Services Selective Supplier fails to find the care services record matching the `resourceId` sent in the HTTP request. - -`HTTP 404` (Not Found) is returned as the HTTP status code - -An `OperationOutcome` Resource is returned indicating that the Care Services Resource could not be found, in an issue having: - -Attribute|Value ----|--- -severity|error -code|not-found -{:.grid} - -The Care Services Selective Supplier may return other HTTP status codes to represent specific error conditions. When HTTP error status codes are returned by the Care Services Selective Supplier, they shall conform to the HTTP standard [RFC2616](https://tools.ietf.org/html/rfc2616). Their use is not further constrained or specified by this transaction. - -#### 2:3.90.4.4 Retrieve Care Services Resource Response message - -The Care Services Selective Supplier’s response to a successful Retrieve Care Services Resource message shall be an `HTTP 200` (OK) Status code with a Care Services Resource, or an appropriate error code. See the [Retrieve Care Services Resource message expected actions](#2390433-expected-actions) for additional details. - -##### 2:3.90.4.4.1 Trigger Events -The Care Services Selective Supplier found a record matching the Resource identifier specified by the Care Services Selective Consumer. - -##### 2:3.90.4.4.2 Message Semantics -The Retrieve Care Services Resource response is sent from the Care Services Selective Supplier to the Care Services Selective Consumer as a single Care Services Resource. - -See [ITI TF-2: Appendix Z.6](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.6-populating-the-expected-response-format) for more details on response format handling. See [ITI TF-2: Appendix Z.7](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.7-guidance-on-access-denied-results) for guidance on Access Denied. - -If the Care Services Selective Supplier is unable to produce a response in the requested format, it shall respond with an `HTTP 400` error indicating that it was unable to fulfill the request. The Care Services Selective Supplier may be capable of servicing requests for response formats not listed, but shall, at minimum, be capable of producing XML and JSON encodings. - -###### 2:3.90.4.4.2.1 Care Services Resource Definition in the Context of Care Services Resource Response -The Care Services Resource definition in the context of a retrieve interaction is the FHIR definition of the various Care Services Resources. Table 2:3.90.4.4.2.1-1 lists the resources with where to find the additional constraints. - -**Table 2:3.90.4.4.2.1-1: Care Services Resource Constraints** - -| Resource | Section | -| ------------------- | --------- | -| `Organization` | [2:3.90.4.2.2.1 FHIR Organization Resource Constraints](#23904221-fhir-organization-resource-constraints) | -| `Location` | [2:3.90.4.2.2.2 FHIR Location Resource Constraints](#23904222-fhir-location-resource-constraints) | -| `Practitioner` | [2:3.90.4.2.2.3 FHIR Practitioner Resource Constraints](#23904223-fhir-practitioner-resource-constraints) | -| `PractitionerRole` | [2:3.90.4.2.2.4 FHIR PractitionerRole Resource Constraints](#23904224-fhir-practitionerrole-resource-constraints) | -| `HealthcareService` | [2:3.90.4.2.2.5 FHIR HealthcareService Resource Constraints](#23904225-fhir-healthcareservice-resource-constraints) | -{: .grid .table-striped} - -### 2:3.90.5 Security Considerations - -See [ITI TF-1: 46.5](volume-1.html#1465-mcsd-security-considerations) for security considerations for the mCSD Profile. - -See [ITI TF-2: Appendix Z.8](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.8-mobile-security-considerations) for common mobile security considerations. - -#### 2:3.90.5.1 Security Audit Considerations - -Note that the same audit message is recorded by both Care Services Selective Supplier and Care Services Selective Consumer. The -difference being the Audit Source element. Both sides record to show consistency -between the message sent by the Consumer and the action taken at the Supplier. - -The actors involved shall record audit events according to the -[Audit Event for Find Matching Care Services for Read by the Care Services Selective Supplier and Consumer](StructureDefinition-IHE.mCSD.Audit.CareServices.Read.html) -or the [Audit Event for Find Matching Care Services for Query by the Care Services Selective Supplier and Consumer](StructureDefinition-IHE.mCSD.Audit.CareServices.Query.html). diff --git a/input/pagecontent/ihepagecontent/ihe_ITI-91.md b/input/pagecontent/ihepagecontent/ihe_ITI-91.md deleted file mode 100644 index 7482e87..0000000 --- a/input/pagecontent/ihepagecontent/ihe_ITI-91.md +++ /dev/null @@ -1,136 +0,0 @@ - -### 2:3.91.1 Scope - -The Request Care Services Updates transaction is used to return a list of updated care services resources. A Care Services Update Consumer initiates a Request Care Services Updates transaction against a Care Services Update Supplier. - -### 2:3.91.2 Actor Roles - -| Actor | Role | -| ----- | ---- | -| Care Services Update Consumer | Requests a list of updated resources from the Care Services Update Supplier. | -| Care Services Update Supplier | Accepts the update request and returns a list of updated resources. | -{: .grid} - -### 2:3.91.3 Referenced Standards - - - [HL7 FHIR standard Release 4](http://hl7.org/fhir/R4/index.html) - - -### 2:3.91.4 Messages - -
-{%include ITI-91-seq.svg%} -
-
- -**Figure 2:3.91.4-1: Interaction Diagram** - -#### 2:3.91.4.1 Request Care Services Updates Request Message - -A Request Care Services Updates message is a FHIR history operation, optionally using the ```_since``` parameter, on the mCSD Resources. - -##### 2:3.91.4.1.1 Trigger Events - -A Care Services Update Consumer triggers a Request Care Services Updates Request to a Care Services Update Supplier according to the business rules for the query. These business rules are outside the scope of this transaction. - -##### 2:3.91.4.1.2 Message Semantics - -A Care Services Update Consumer initiates a history request using HTTP GET as defined at [http://hl7.org/fhir/R4/http.html#history](http://hl7.org/fhir/R4/http.html#history) on the mCSD Resources. - -A Care Services Update Supplier and Care Services Update Consumer shall support the following parameters. - -``` -_since -``` - -They shall also support the requirements in [ITI TF-2: Z.6](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.6-populating-the-expected-response-format), Populating the Expected Response Format. - -A Care Services Update Supplier shall support receiving a request for both the JSON and the XML messaging formats as defined in FHIR. A Care Services Update Consumer shall accept either the JSON or the XML messaging formats as defined in FHIR. - -See [ITI TF-2: Appendix W](https://profiles.ihe.net/ITI/TF/Volume2/ch-W.html) for informative implementation material for this transaction. - -##### 2:3.91.4.1.3 Expected Actions - -The Care Services Update Supplier shall process the query to discover the resources that match the search parameters given, and gives a response as per [Section 2:3.91.4.2](#239142-request-care-services-updates-response-message) or an error as per [http://hl7.org/fhir/R4/search.html#errors](http://hl7.org/fhir/R4/search.html#errors). - -#### 2:3.91.4.2 Request Care Services Updates Response Message - -The Request Care Services Updates \[ITI-91\] transaction uses the response semantics as defined at [http://hl7.org/fhir/R4/http.html#history](http://hl7.org/fhir/R4/http.html#history) as applicable for the resources. - -##### 2:3.91.4.2.1 Trigger Events - -The Care Services Update Supplier sends the Request Care Services Updates Response to the Care Services Update Consumer when results are ready. - -##### 2:3.91.4.2.2 Message Semantics - -The Care Services Update Supplier shall support the history response message as defined at [http://hl7.org.fhir/R4/http.html#history](http://hl7.org.fhir/R4/http.html#history) on the following Resources: - - - Organization, as defined at - [http://hl7.org/fhir/R4/organization.html](http://hl7.org/fhir/R4/organization.html) - - - Location, as defined at [http://hl7.org/fhir/R4/location.html](http://hl7.org/fhir/R4/location.html) - - - Practitioner, as defined at - [http://hl7.org/fhir/R4/practitioner.html](http://hl7.org/fhir/R4/practitioner.html) - - - PractitionerRole, as defined at - [http://hl7.org/fhir/R4/practitionerrole.html](http://hl7.org/fhir/R4/practitionerrole.html) - - - HealthcareService, as defined at - [http://hl7.org/fhir/R4/healthcareservice.html](http://hl7.org/fhir/R4/healthcareservice.html) - - All References (reference.reference element) to Resources defined in - this transaction shall be populated with an accessible URL (see - [https://www.hl7.org/fhir/references-definitions.html#Reference.reference](https://www.hl7.org/fhir/references-definitions.html#Reference.reference) - ), unless the referenced resource is not present on a server - accessible to the client. - -###### 2:3.91.4.2.2.1 FHIR Organization Resource Constraints - -A Care Services Update Consumer and a Care Services Update Supplier shall query or return an Organization Resource. The Organization Resource shall be further constrained as described in the [Organization Profile for mCSD](StructureDefinition-IHE.mCSD.Organization.html). - -When the Organization represents a Facility and is paired with a Location, the FHIR Organization Resource shall be further constrained as described in the [Organization for Facilities Profile for mCSD](StructureDefinition-IHE.mCSD.FacilityOrganization.html). - -When the Organization represents a Jurisdiction and is paired with a Location, the FHIR Organization Resource shall be further constrained as described in the [Organization for Jurisdictions Profile for mCSD](StructureDefinition-IHE.mCSD.JurisdictionOrganization.html). - -###### 2:3.91.4.2.2.2 FHIR Location Resource Constraints - -A Care Services Update Consumer and a Care Services Update Supplier shall query or return a Location Resource. The Location Resource shall be further constrained as described in the [Location Profile for mCSD](StructureDefinition-IHE.mCSD.Location.html). - -When the Location represents a Facility and is paired with an Organization, the FHIR Location Resource shall be further constrained as described in the -[Location for Facilities Profile for mCSD](StructureDefinition-IHE.mCSD.FacilityLocation.html). - -When the Location represents a Jurisdiction and is paired with an Organization, the FHIR Location Resource shall be further constrained as described in the [Location for Jurisdictions Profile for mCSD](StructureDefinition-IHE.mCSD.JurisdictionLocation.html). - -When supporting the Location Distance Option, the FHIR Location Resource shall be further constrained as described in the [Location with Distance Option Profile for mCSD](StructureDefinition-IHE.mCSD.LocationDistance.html). - -###### 2:3.91.4.2.2.3 FHIR Practitioner Resource Constraints - -A Care Services Update Consumer and a Care Services Update Supplier shall query or return a Practitioner Resource. The Practitioner Resource shall be further constrained as described in the [Practitioner Profile for mCSD](StructureDefinition-IHE.mCSD.Practitioner.html). - -###### 2:3.91.4.2.2.4 FHIR PractitionerRole Resource Constraints - -A Care Services Update Consumer and a Care Services Update Supplier shall query or return a PractitionerRole Resource. The PractitionerRole Resource shall be further constrained as described in the [PractitionerRole Profile for mCSD](StructureDefinition-IHE.mCSD.PractitionerRole.html). - -###### 2:3.91.4.2.2.5 FHIR HealthcareService Resource Constraints - -A Care Services Update Consumer and a Care Services Update Supplier shall query or return a HealthcareService Resource. The HealthcareService Resource shall be further constrained as described in the [HealthcareService Profile for mCSD](StructureDefinition-IHE.mCSD.HealthcareService.html). - -##### 2:3.91.4.2.3 Expected Actions - -The Care Services Update Consumer has received the response and continues with its workflow. - -### 2:3.91.5 Security Considerations - -See [ITI TF-1: 46.5](volume-1.html#1465-mcsd-security-considerations) for security considerations for the mCSD Profile. - -See [ITI TF-2: Appendix Z.8](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.8-mobile-security-considerations) for common mobile security considerations. - -#### 2:3.91.5.1 Security Audit Considerations - -Note that the same audit message is recorded by both Care Services Update Supplier and Care Services Update Consumer. The -difference being the Audit Source element. Both sides record to show consistency -between the message sent by the Supplier and the action taken at the Consumer. - -The actors involved shall record audit events according to the -[Audit Event for Request Care Services Updates by the Care Services Update Supplier and Consumer](StructureDefinition-IHE.mCSD.Audit.CareServices.Updates.html). diff --git a/input/pagecontent/ihepagecontent/ihe_index.md b/input/pagecontent/ihepagecontent/ihe_index.md deleted file mode 100644 index 324b538..0000000 --- a/input/pagecontent/ihepagecontent/ihe_index.md +++ /dev/null @@ -1,71 +0,0 @@ - -The Mobile Care Services Discovery (mCSD) Profile supports RESTful -queries across related care services resources. - -The loosely coupled design and flexible querying capability of the mCSD -Profile means it can be deployed within a variety of eHealth -architectures and support a wide array of care workflows. - - -
- -| [Significant Changes, Open, and Closed Issues](issues.html) | -{: .grid} - -**[Search this IG](https://www.google.com/search?q=site%3Ahttps%3A%2F%2Fprofiles.ihe.net%2FITI%2FmCSD)** - -
- -### Organization of This Guide -This guide is organized into the following four main sections: - -1. Volume 1: Profiles - 1. [mCSD Introduction](volume-1.html) - 2. [mCSD Actors, Transactions, and Content Modules](volume-1.html#1461-mcsd-actors-transactions-and-content-modules) - 3. [mCSD Actor Options](volume-1.html#1462-mcsd-actor-options) - 4. [mCSD Required Groupings](volume-1.html#1463-mcsd-required-actor-groupings) - 5. [mCSD Overview](volume-1.html#1464-mcsd-overview) - 6. [mCSD Security Considerations](volume-1.html#1465-mcsd-security-considerations) - 7. [mCSD Cross-Profile Considerations](volume-1.html#1466-mcsd-cross-profile-considerations) - 8. [mCSD Deployment Considerations](volume-1.html#1467-mcsd-deployment-considerations) - 9. [mCSD Endpoint Usage Considerations](volume-1.html#1468-mcsd-endpoint-usage-considerations) -2. Volume 2: Transaction Detail - 1. [Find Matching Care Services \[ITI-90\]](ITI-90.html) - 2. [Request Care Services Updates \[ITI-91\]](ITI-91.html) -3. [Test Plan](testplan.html) -4. [Changes to other Profiles](other.html) - -Click on any of the links above, navigate the contents using the [table of contents](toc.html), or -if you are looking for a specific artifact, check out the [index](artifacts.html). - -### Conformance Expectations - -IHE uses the normative words: Shall, Should, and May according to [standards conventions](https://profiles.ihe.net/GeneralIntro/ch-E.html). - -mCSD uses ```Must Support``` in StructureDefinition profiles. This is equivalent to the IHE use of **R2** as defined in [Appendix Z](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.10-profiling-conventions-for-constraints-on-fhir). - -### Download - -You can also download: - -* [this entire guide](full-ig.zip), -* the definition resources in [json](definitions.json.zip), [xml](definitions.xml.zip), [ttl](definitions.ttl.zip), or [csv](csvs.zip) format, or -* the example resources in [json](examples.json.zip), [xml](examples.xml.zip) or [ttl](examples.ttl.zip) format. - -The source code for this Implementation Guide can be found on [IHE GitHub](https://github.com/IHE/ITI.mCSD). - -#### Cross Version Analysis - -{% include cross-version-analysis.xhtml %} - -#### Dependency Table - -{% include dependency-table.xhtml %} - -#### Globals Table - -{% include globals-table.xhtml %} - -#### IP Statements - -{% include ip-statements.xhtml %} \ No newline at end of file diff --git a/input/pagecontent/ihepagecontent/ihe_issues.md b/input/pagecontent/ihepagecontent/ihe_issues.md deleted file mode 100644 index 3d56f4d..0000000 --- a/input/pagecontent/ihepagecontent/ihe_issues.md +++ /dev/null @@ -1,380 +0,0 @@ -
- -## Significant changes from mCSD, Rev 3.5: -- Removed Additional Hierarchy extension due to addition of OrganizationAffiliation which can fulfill that use case. -- Changed Organization.type and Location.type for Facilities and Jurisdictions to use a defined CodeSystem instead of URNs. - - Changed the cardinality and slicing of type to fix QA errors. Additional slices can be made if needed by implementors. -- Added in AuditEvent structure definitions with examples based on [Basic Audit](https://profiles.ihe.net/ITI/BALP/index.html). -- Added [Purpose Of Use](StructureDefinition-IHE.mCSD.PurposeOfUse.html) extension for Endpoint and Organization with [Search Parameter](SearchParameter-IHE.mCSD.Search.PurposeOfUse.html). - -## Significant changes from mCSD, Rev 3.4: -- Added OrganizationAffiliation and Endpoint resources to [1:46](volume-1.html#1-46-mobile-care-services-discovery-mcsd) and [1:46.1.1](volume-1.html#14611-actor-descriptions-and-actor-profile-requirements) -- Added [Use Case #5: Organization Affiliation](volume-1.html#146425-use-case-5-health-information-exchange-hie-membership-discovery), - describing how OrganizationAffiliations can represent non-hierarchical relationships between Organizations -- Added [Use Case #6: Health Information Exchange (HIE) Endpoint Discovery](volume-1.html#146426-use-case-6-health-information-exchange-hie-endpoint-discovery), showing an example of querying a directory with Endpoint resources -- Added new Section [1:46.8 mCSD Endpoint Usage Considerations](volume-1.html#1468-mcsd-endpoint-usage-considerations), - describing how to populate and use a directory with Endpoint resources to enable electronic communications -- \[ITI-90\]: added OrganizationAffiliation and Endpoint resources to [Description and Message Semantics](ITI-90.html#239041-find-matching-care-services-request-message) -- \[ITI-90\]: added expected search parameters for [Organization](ITI-90.html#23904122-organization-resource-message-semantics) to support OrganizationAffiliation and Endpoint resources -- \[ITI-90\]: added sections for expected search parameters for [Endpoint](ITI-90.html#23904128-endpoint-resource-message-semantics) and [OrganizationAffiliation](ITI-90.html#23904129-organizationaffiliation-resource-message-semantics) -- Added the following to deal with FHIR R4 Endpoint.connectionType being limited to one value from an HL7 valueSet - (see [FHIR-12342](https://jira.hl7.org/browse/FHIR-12342): need more detail to connect to an IHE Document Sharing endpoint): - - A code system [mCSD Endpoint Types](CodeSystem-MCSDEndpointTypes.html) to define IHE Endpoint types beyond those in the FHIR core, using the same abstract codes HL7 uses like "ihe-xca", but adds child codes like "XCA-RespGateway-Query" - - A [core value set](ValueSet-MCSDEndpointTypesCoreDocShareVS.html) to cover the codes at the HL7 level of detail, suitable for use in connectionType - - An [expanded value set](ValueSet-MCSDEndpointTypesVS.html) using the child codes, for use in the following extension - - An [extension for Endpoint Specific Type](StructureDefinition-ihe-endpointspecifictype.html) to carry the more-specific IHE code -- Added a [code system](CodeSystem-MCSDOrgAffTypes.html) and [value set](ValueSet-MCSDOrgAffTypesVS.html) for types of OrganizationAffiliation -- Added structure definitions for resource profiles: - - [mCSD Endpoint](StructureDefinition-IHE.mCSD.Endpoint.html): general Endpoint - - [mCSD Endpoint for Document Sharing](StructureDefinition-IHE.mCSD.Endpoint.DocShare.html): - Endpoint that supports IHE Document Sharing (e.g., XCA, MHD), using the [extension for Endpoint Specific Type](StructureDefinition-ihe-endpointspecifictype.html) - - [mCSD Organization Affiliation](StructureDefinition-IHE.mCSD.OrganizationAffiliation.html): general OrganizationAffiliation. - - [mCSD Organization Affiliation DocumentSharing](StructureDefinition-IHE.mCSD.OrganizationAffiliation.DocShare.html): OrganizationAffiliation that supports IHE Document Sharing, using a fixed code "DocShare-federate" that indicates that the affiliation implies electronic access to the participatingOrganization (see [1:46.8 mCSD Endpoint Usage Considerations](volume-1.html#1468-mcsd-endpoint-usage-considerations)) -- Added [examples](artifacts.html#example-example-instances) for OrganizationAffiliation and Endpoint - -## Issues - -IHE welcomes [New Issues](https://github.com/IHE/ITI.mCSD/issues/new/choose) -from the GitHub community. For those without GitHub access, issues may be -submitted at [ITI Public Comments](https://www.ihe.net/ITI_Public_Comments/). - -As issues are submitted they will be managed on the -[mCSD GitHub Issues](https://github.com/IHE/ITI.mCSD/issues), where discussion and -workarounds may be found. These issues, when critical, will be processed using the normal -[IHE Change Proposal](https://wiki.ihe.net/index.php/Category:CPs) management and balloting. -It is important to note that as soon as a Change Proposal is approved, it carries the same -weight as a published Implementation Guide (i.e., it is testable at an -[IHE Connectathon](https://www.ihe.net/participate/connectathon/) from the time it is -approved, even if it will not be integrated until several months later). - -### Open Issues and Questions -These issues were known as part of the publication, and IHE invites comments. - -[mCSD\_7](https://github.com/IHE/ITI.mCSD/issues/94). Should there be additional required search parameters? Should -we also require any reverse chaining (\_has) options for the search? -Should we require any reverse includes (\_revinclude)? These would add -complexity to the server and most will have similar options through -include and normal chaining. - -In \[ITI-90\], we've added a number of required search parameters to support -queries for OrganizationAffiliation and Endpoint. Is it sustainable to require this many -search parameters? Should we move some to SHOULDs or MAYs? Note that the main use case -is locating an Organization based on its business, not network, attributes (already -covered elsewhere in mCSD), then checking its Endpoints. Further, recursively searching -parents and affiliations for Endpoints is likely an edge case, not one we need to try to do -in a single request. - -[mCSD\_10](https://github.com/IHE/ITI.mCSD/issues/95). Section 1:46.8 mCSD Endpoint Usage Considerations, describes -how to populate and use an endpoint directory. Given that this IG is more -about how to deploy and use directories than what to put in them, would this -content be better as a white paper instead? And could this content be -generalized to allow usage with mCSD as well as other directory IGs like -[https://hl7.org/fhir/uv/vhdir/](https://hl7.org/fhir/uv/vhdir/)? - -[mCSD\_11](https://github.com/IHE/ITI.mCSD/issues/96). Should we assume federation of (i.e., connectivity to) child -organizations when related by .partOf? Currently the IG does -(see Section 1:46.8.2), and we believe this is what is done in practice. -The downside is that there is no way to represent a hierarchical relationship that does not imply routing. - -[mCSD\_12](https://github.com/IHE/ITI.mCSD/issues/97). Should we specify details of addressing to federated recipients, at least for some -profiles (see Section 1:46.8.2)? For example, with MHD \[ITI-65\] we could pass the Organization.identifier -in the intendedRecipient field. There is already an IG for passing a Direct address in an XDR \[ITI-41\]. - -[mCSD\_14](https://github.com/IHE/ITI.mCSD/issues/98). Consider doing something similar to what -[HL7 UDAP Security](https://build.fhir.org/ig/HL7/fhir-udap-security-ig/branches/main/) did, and -describe mCSD within the larger family of directory IGs, making clear -where compatibility is assured as well as what each IGs focus is. For example, -[https://hl7.org/fhir/uv/vhdir/](https://hl7.org/fhir/uv/vhdir/) covers -maintenance and validation of the content of directories, while mCSD -covers how to represent and search complex structures. - -[mCSD\_15](https://github.com/IHE/ITI.mCSD/issues/99). In [Section 1:46.8](volume-1.html#1468-mcsd-endpoint-usage-considerations), -we mention the US TEFCA RCE maintaining a consolidated -directory spanning multiple networks. Can we identify an international example? - -[mCSD\_16](https://github.com/IHE/ITI.mCSD/issues/100). In [Section 1:46.8.2](volume-1.html#14682-endpoint-to-a-structure), -we say that a hierarchy formed by Organization.partOf implies federation of (i.e., connectivity to) child -organizations. Should we? We believe this is what is done in practice. The downside is that -there would be no way to represent a hierarchical relationship that does not imply routing. -An alternative proposed design would require OrganizationAffiliation with a code -of “DocShare-federate” to be explicitly related to any parent-child relationship to imply connectivity. -We did not choose this because its impact on existing directory structures would be substantial. - -[mCSD\_18](https://github.com/IHE/ITI.mCSD/issues/101). Should we specify details of addressing federated recipients, at least for some -profiles (see [Section 1:46.8.2](volume-1.html#14682-endpoint-to-a-structure))? -For example, with MHD \[ITI-65\] we could pass the Organization.identifier -in the intendedRecipient field. There is already an IG for passing a Direct address in an XDR \[ITI-41\]. - -[mCSD\_20](https://github.com/IHE/ITI.mCSD/issues/102). There is minimal usage guidance for REST endpoints. -Figure [1:46.8.3-1](volume-1.html#14683-grouping-actors) shows connectionType = hl7-fhir-rest and -extension:specificType = MHD-Recipient-ProvideReg. Is this necessary? Couldn't -clients discover anything they need to know about REST from the CapabilityStatement? - -[mCSD\_21](https://github.com/IHE/ITI.mCSD/issues/103). This profile says very little about home community ID, yet it is called out -in [mCSD issue #2](https://github.com/IHE/ITI.mCSD/issues/2). -[Section 1:46.8.2](volume-1.html#14682-endpoint-to-a-structure) talks about -"identifiers of type Home Community ID". The [profile on Endpoint for Document Sharing](StructureDefinition-IHE.mCSD.Endpoint.DocShare.html) says to put the HCID in the Endpoint.identifier. The -[Example of an mCSD XCA Query Endpoint](Endpoint-ex-endpointXCAquery.json.html) shows -an Endpoint.identifier.type with coding for a HCID. But this is not specified -normatively anywhere. - -- Does HCID need to be specified to ensure interoperability? -- Should HCID be mandated on the Endpoint, the Organization, or both? -- Should federated communities behind an Endpoint be reflected in its identifier list? -- Should identifier of an Endpoint be empty? - -We have seen directories add a custom code "HCID" that shows that an identifier is a HCID, -and have seen them use the system of "urn:ietf:rfc:3986" and a URN-encoded OID. -In committee discussions, we walked this through, and the general consensus was that -for identifying an organization to meet the MHD to a Federation use cases (i.e., to -determine connectivity), whether or not an identifier happened to be a HCID -was not significant. If we were to get into more detail about addressing federated recipients -(see issue 15 in this list), we might need to make decisions like whether HCID must be -a specific identifier type and whether it should be URN-encoded. - -[mCSD\_23](https://github.com/IHE/ITI.mCSD/issues/104). In the [Resource Profile: mCSD Endpoint for Document Sharing](StructureDefinition-IHE.mCSD.Endpoint.DocShare.html), -to indicate that the endpoint is not constrained, should payloadType and payloadMimeType be empty, or fully populated? - -[mCSD\_24](https://github.com/IHE/ITI.mCSD/issues/105). In the [Resource Profile: mCSD Endpoint for Document Sharing](StructureDefinition-IHE.mCSD.Endpoint.DocShare.html), -should payloadType and payloadMimeType be required to be the same for Endpoints that reflect grouped actors (i.e., XCA/XDS/MHD Query and XCA/XDS/MHD Retrieve), thus replicating the capability at both endpoints? - -[mCSD\_25](https://github.com/IHE/ITI.mCSD/issues/106). In the [Resource Profile: mCSD Endpoint for Document Sharing](StructureDefinition-IHE.mCSD.Endpoint.DocShare.html), -should payloadType and payloadMimeType be specified for an XCA Query endpoint? It did not seem right that Query be indicated with a mimeType of ebRegistry as that is not helpful to the use-case. - -[mCSD\_26](https://github.com/IHE/ITI.mCSD/issues/107). In the [Resource Profile: mCSD Endpoint for Document Sharing](StructureDefinition-IHE.mCSD.Endpoint.DocShare.html), would a Proxy service that is supporting OrgAff be a good example of NOT putting a homeCommunityId in the endpoint.identifier? - -[mCSD\_27](https://github.com/IHE/ITI.mCSD/issues/108). Need to align and flesh out the examples better with the guidance in [Section 1:46.8.2](volume-1.html#14682-endpoint-to-a-structure). For example, could we see an example for an organization accessible via two different exchanges? - -[mCSD\_28](https://github.com/IHE/ITI.mCSD/issues/109). Grouping of actors is mentioned in [Section 1:46.8.3](volume-1.html#14683-grouping-actors). -Does Karen's Cross apply here? If so, how? Should OrganizationAffiliation be required? - -[Karen's Cross](https://wiki.directproject.org/w/images/3/3e/2011-03-09_PDF_-_XDR_and_XDM_for_Direct_Messaging_Specification_FINAL.pdf#page=6) -(see 3.0 Interaction Patterns. Also described [here](https://healthcaresecprivacy.blogspot.com/2012/08/karens-cross-or-just-minimal-metadata.html)) -is a mapping table defined by the [Direct Project](https://wiki.directproject.org/Main_Page) (not by IHE), -that tells how to get to and from different flavors of IHE Document Sharing "Push" (XDR, XDM) and the Direct Protocol. -It was done at a "whiteboard" level of detail, and resulted in specific requirements for transforming -messages more or less isomorphically from one flavor to another. Later, [additional requirements](https://docs.google.com/document/d/1U0h_mB5AQGNgSwZKRHHqg8JVFPp1MW6ptIWxYR6Mtyg/edit#heading=h.o5yl9ti9jyak) -were added for encoding Direct addresses in XDR SubmissionSet.intendedRecipient. It should be noted -that the Cross is incomplete; neither Direct nor IHE has any analogous requirements for transforming, -say, an XCA Query and Retrieve response into an XDM file. XCDR and MHD Push and Pull are also missing. -That said, IHE Document Sharing profiles (not counting Direct) are generally considered similar enough that -transformations should be obvious. - -So, when would Karen's Cross (or an expanded version) apply? Potentially anywhere two systems -need to translate between different Doc Sharing actors, but it's really only needed if transformations -are not obvious. Maybe it needs to be documented by IHE (especially if it's between IHE actors). -We'll look into this in a second. - -But first, OrganizationAffiliation shouldn't be required, because it's orthogonal -to whether translation is needed. For example: In the directory, Org A has two Endpoints: -an MHD Document Responder and an XDS Document -Registry/Repository. Behind the scenes, the MHD actor is an adapter over the XDS actors. -This is simply two APIs to the same organization. The HCID and any other -organization or author identifiers are simply copied; there is no translation needed. - -Now let's consider the other cases where there's federation to other organizations/entities -not directly reachable. OrganizationAffiliation is just one case: -- An Org allows access to others related with partOf -- An Org allows access to others related with OrganizationAffiliation -- An Org allows access to Practitioners related via mCSD links - -In these cases, there might be a translation layer behind the exposed Endpoint to get to those -other entities, or there might be some other proprietary mechanism: internal EHR messaging, -direct DB access, etc. - -So would Karen's Cross (or an expanded version) potentially apply? Yes, but likely only in making -sure that addressing of federated organizations/entities is clear. We have that as issue mCSD\_18. - -[mCSD\_29](https://github.com/IHE/ITI.mCSD/issues/110). Is OrganizationAffiliation sufficiently mature to base this profile on? -Is it appropriate to say the .organization is the "parent-like" org that rolls up content from -.participatingOrganization orgs? There is a .network field; should that be used -instead? - -We believe we are using it appropriately, but there are a couple of issues we are tracking: -- [FHIR-25406: definition of organization and participatingOrganization in OrganizationAffiliation is not clear](https://jira.hl7.org/browse/FHIR-25406) -- [FHIR-36019: OrganizationAffiliation.network unclear](https://jira.hl7.org/browse/FHIR-36019) - -[mCSD\_30](https://github.com/IHE/ITI.mCSD/issues/111). Currently there is one code in [mCSD Organization Affiliation Types](https://build.fhir.org/ig/IHE/ITI.mCSD/branches/main/CodeSystem-MCSDOrgAffTypes.html). Should there be at least two, one for transparent federation vs opaque federation? -The expectations would be different: with transparent federation, federated identifiers would be -preserved in responses and respected in requests. With opaque federation, identifiers would be -consolidated/overwritten with the identifiers of the "parent" organization. - -Probably, but the implications of opaque federation are complex. Some aspects may be consolidated -(e.g., golden patient record) while others are not (separate documents). Perhaps we could limit scope -to whether federated communities (Organizations with an ID of type HCID) are addressable in -requests and responses. Seeking input from reviewers. - -[mCSD\_31](https://github.com/IHE/ITI.mCSD/issues/112). Currently, only synchronous XDS/XCA/XDR and MHD Push are supported. This scope was limited -for the public-comment deadline. After public comment, we plan to add in asynchronous (WS-A and AS4) -and full MHD. One area that needs work is Digital Certificates to support async end-to-end security -(Not needed for sync that uses TLS). -- Currently, base FHIR doesn't include a publicKey, and recommends a local extension -[https://jira.hl7.org/browse/FHIR-10764](https://jira.hl7.org/browse/FHIR-10764). We will add an extension. -- Note VhDir has an extension http://hl7.org/fhir/uv/vhdir/StructureDefinition/digitalcertificate, -but it is very complex. Not clear if this complexity is needed. - -[mCSD\_32](https://github.com/IHE/ITI.mCSD/issues/113). In [mCSD Endpoint](StructureDefinition-IHE.mCSD.Endpoint.html), rather than managingOrganization 1..1, create an invariant so that -either managingOrganization or contact must be populated. - -[mCSD\_33](https://github.com/IHE/ITI.mCSD/issues/114). FHIR R5 will allow Endpoint.connectionType to be greater than 1, so we can use the IHE-defined codes in addition to the HL7 ones. We won't need Endpoint.extension:specificType anymore. See [Issue 89](https://github.com/IHE/ITI.mCSD/issues/89). - -[mCSD\_34](https://github.com/IHE/ITI.mCSD/issues/58). Should we add a subscription model for receiving updates instead of or in addition to \[ITI-91\] for resource updates? - -### Closed Issues -These issues have been decided and documented in the publication. - -*mCSD\_1. Should we include the FreeBusy transaction and use cases or -just remove them?* - - - Take this out, and possibly add later if needed as an option. - -*mCSD\_2. Should we include the aggregate reporting use case from Care -Services Discovery (CSD) or remove with a reference to Aggregate Data -Exchange (ADX) in cross profile considerations? This use case would -define options for the actors in this use case to return aggregate data. -* - - - At this time we do not believe these are key uses cases, but request - feedback. - -*mCSD\_3. How do we capture data about community health workers? In some -environments, there are community health workers that are associated -with a facility but don't actually work there. Such a worker might have -a set area of villages that they rotate through providing -community-based care. The villages are within the catchment area of a -Health facility, and the supervisor of the community health worker may -be based at that facility. * - -*Not quite sure the best way to capture this when looking at:* - -*[http://build.fhir.org/location.html\#bnr](http://build.fhir.org/location.html#bnr)* - -*It is clear that we have a hierarchy of locations to capture the -geographic hierarchy (jurisdictions): * - - - *The health facility in question would be situated at a location - above the village level, say at the county or district level - this - we can capture in the parent-child relationship “partOf” in the - location resource* - - - *The community health worker is providing services at several - villages - this we can capture through the location data field of - the role in the practitioner resource* - - - *The community health worker is associated to a health facility - - again we can capture this through the location field but perhaps we - would use a different role to indicate that they're community health - worker associated to this facility but not directly providing - services at the facility, only its catchment area* - - - *In case a community health worker is reporting to a supervisor - - that's not captured anywhere that I can see in FHIR. I think this is - a larger that exists beyond the community health worker context* - -Perhaps the best way to model this is to define each village as a -location, and associate that worker with each location they rotate -through. Each village is a partOf the health district. The facility is -also a location that is partOf the district. The practitioner is related -to the village locations with a "delivers care to" role; and to the -facility with a "based out of" role. - -*mCSD\_4. Do we need to include more geospatial data (such as polygons -or more complex geometry types) stored with Locations and how? This -would be so jurisdictions (such as districts or counties) could include -that data instead of just a position (latitude/longitude). -[CP\#13391](http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13391) -has been opened for this.* - -As per the request, FHIR has added a standard extension to address this: -[https://www.hl7.org/fhir/extension-location-boundary-geojson.html](https://www.hl7.org/fhir/extension-location-boundary-geojson.html) - -*mCSD\_5. With a federated deployment, data may come from multiple -sources and there can be an issue with resolving duplicate records and -maintaining the mapping. Patient has a link field and we have opened a -CP for Organization, Location, and Practitioner. CP -[GF\#13264](http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13264) -has been opened for this. There is also the Linkage resource, but it is -maturity level 0.* - -FHIR has closed the issued with the recommendation to use the Linkage -resource to handle this. - -*mCSD\_6. We need a way to deprecate identifiers. For now we can use -period and we have created a CP to add an entry to the use field: -[GF\#13265](http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13265).* - -FHIR has added an additional Identifier.use code of “old” for this case. - -*mCSD\_8. IHE has updated mCSD to add support for organizational -facilities. As part of this revision of mCSD, we have removed the -“Organization Option”, “Location Option”, “Practitioner Option”, and -“Healthcare Services Option”. These options existed to enable servers -to focus only on a small subset of the resources. The actual burden to -support all resources is small and set of options seems to add -unnecessary complexity. The result would be that servers shall support -all of the FHIR Resources, the clients can use the FHIR Resources in the -way defined. If there is concern with the removal of these options, -please submit a Public Comment.* - -No comments received so changes are being kept, but any additional comments are welcome. - -*mCSD\_9. We have added a requirement to include a meta.profile tag for -all compliant resources. This is so that in a mixed server that has -these resources as well as others, a Care Services Selective Consumer -can limit the results of Find Matching Care Service \[ITI-90\] to only -mCSD resources using the \_profile parameter. Since this type of -parameter isn’t allowed for the \_history transaction for Request Care -Services Updates \[ITI-91\] the Care Services Update Consumer may have -to filter results if required. Is this a common configuration and is -this step necessary?* - -Removed the references to meta.profile. - -*mCSD\_13. Section 1:46.8 mCSD Endpoint Usage Considerations, describes -how to populate and use an endpoint directory. Given that this IG is more -about how to deploy and use directories than what to put in them, would this -content be better as a white paper instead? And could this content be -generalized to allow usage with mCSD as well as other directory IGs like -[https://hl7.org/fhir/uv/vhdir/](https://hl7.org/fhir/uv/vhdir/)?* - -Duplicate of mCSD\_10 - -*mCSD\_17. In [Section 1:46.8.2](volume-1.html#14682-endpoint-to-a-structure), -we say that a hierarchy formed by the mCSD Additional Hierarchies extension -does not imply federation of (i.e., connectivity to) child organizations. Should it?* - -Extension has been removed. - -*mCSD\_19. In [Section 1:46.8.2](volume-1.html#14682-endpoint-to-a-structure), -why do we use OrganizationAffiliation for -an organization's membership in an HIE, as opposed to the mCSD Additional Hierarchies extension? -Because we don't wish to constrain the use of resources that define organizational structure, -rather just reflect how best to use Endpoints in these structures. OrganizationAffiliation -is already used in other use cases, and in fact, shows HIE/HIO membership as one of -its examples.* - -Extension has been removed. - -*mCSD\_22. In \[ITI-90\], we've added a number of required search parameters to support -queries for OrganizationAffiliation and Endpoint. Is it sustainable to require this many -search parameters? Should we move some to SHOULDs or MAYs? Note that the main use case -is locating an Organization based on its business, not network, attributes (already -covered elsewhere in mCSD), then checking its Endpoints. Further, recursively searching -parents and affiliations for Endpoints is likely an edge case, not one we need to try to do -in a single request.* - -Combined into related open issue 7. - -## Significant changes from mCSD, Rev 3.3: -- FHIR Implementation Guide instead of [pdf - Rev. 3.3](https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_mCSD.pdf) -- Removed inline UML text and moved it to images-source/ -- Removed reference to setting meta.profile as it is redundant -- Added sections in actor requirements describing the requirement of providing a capability statement [Volume 1](volume-1.html#14611-actor-descriptions-and-actor-profile-requirements) -- Updated the canonical URL for the organization hierarchy extension to `https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.OrganizationHierarchy` -- Added links to the structure definitions for resource profiles to [ITI-90](ITI-90.html) and [ITI-91](ITI-91.html) -- Changed structuredefinitions for Facility and Jurisdiction to use an invariant for the type requirement instead of slicing -- Added in text to show that searches can use GET or POST [ITI-90 Message Semantics](ITI-90.html#2390412-message-semantics) -- Added in retrieve (GET RESOURCE/ID) message section starting at [ITI-90](ITI-90.html#239043-retrieve-care-services-resource-message) -- Removed tables for StructureDefinitions for resources. - -
diff --git a/input/pagecontent/ihepagecontent/ihe_other.md b/input/pagecontent/ihepagecontent/ihe_other.md deleted file mode 100644 index 35967e2..0000000 --- a/input/pagecontent/ihepagecontent/ihe_other.md +++ /dev/null @@ -1,32 +0,0 @@ -
-This section contains modifications to other IHE publications and profiles, and is not a part of the mCSD Profile. The content here will be incorporated into the target narrative at a future time, usually when mCSD goes final text. -
- -## IHE Technical Frameworks General Introduction Appendix A: Actors - -|------------------------------------------------| -| Editor, add the following new or modified actors to the [IHE Technical Frameworks General Introduction Appendix A](https://profiles.ihe.net/GeneralIntro/ch-A.html): | -{:.grid .bg-info} - - -| Actor | Definition | -| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Care Services Selective Consumer | Consumes information about care services resources. | -| Care Services Selective Supplier | Supplies information about care services resources. | -| Care Services Update Consumer | Consumes the history of care services information. | -| Care Services Update Supplier | Supplies the history of care services information. | -{:.grid .table-striped} - - -## IHE Technical Frameworks General Introduction Appendix B: Transactions - -|------------------------------------------------| -| Editor, add the following new or modified transactions to the [IHE Technical Frameworks General Introduction Appendix B](https://profiles.ihe.net/GeneralIntro/ch-B.html): | -{:.grid .bg-info} - - -| Transaction | Definition | -| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Find Matching Care Services \[ITI-90\] | The Find Matching Care Services transaction is used to query for practitioners, locations, organizations, and healthcare services resources as well as links between these resources. The Find Matching Care Services transaction is initiated by the Care Services Selective Consumer against the Care Services Selective Supplier. | -| Request Care Services Updates \[ITI-91\] | The Request Care Services Updates is used to obtain practitioners, locations, organizations, and healthcare services resources that have been inserted or updated since the specified timestamp. The Request Care Services Updates is initiated by the Care Services Update Consumer against the Care Services Update Supplier. | -{:.grid .table-striped} diff --git a/input/pagecontent/ihepagecontent/ihe_testplan.md b/input/pagecontent/ihepagecontent/ihe_testplan.md deleted file mode 100644 index d63e355..0000000 --- a/input/pagecontent/ihepagecontent/ihe_testplan.md +++ /dev/null @@ -1,5 +0,0 @@ -
- -This Test Plan page is a prototype. We expect the maturity of the content will improve over time. For now, we summarize high level testing scope and available tools. Comments are welcome. -
- diff --git a/input/pagecontent/ihepagecontent/ihe_volume-1.md b/input/pagecontent/ihepagecontent/ihe_volume-1.md deleted file mode 100644 index ff3dde2..0000000 --- a/input/pagecontent/ihepagecontent/ihe_volume-1.md +++ /dev/null @@ -1,549 +0,0 @@ - -The Mobile Care Services Discovery (mCSD) Profile supports discovery of care services resources using a RESTful interface in interrelated, federated environments. - -Use cases and solutions using mCSD are outlined in the [mCSD White Paper](https://profiles.ihe.net/ITI/papers/mCSD/index.html). - -The profile supports querying for: - -1. **Organization** – Organizations are “umbrella” entities; these may be considered the administrative bodies under whose auspices care services are provided such as Healthcare Information Exchanges(HIEs), Integrated Delivery Networks (IDNs), Non-Government Organizations (NGOs), Faith-Based Organizations (FBOs) or even a one-physician family practice. An organization has a unique identifier and may have additional administrative attributes such as contact person, mailing address, etc. Departments of an institution, or other administrative units, may be represented as child Organizations of a parent Organization. - -2. **Facility** – Facilities are physical care delivery sites such as hospitals, clinics, health outposts, physician offices, labs, pharmacies, etc. A Facility has a unique identifier, geographic attributes (address, geocode), contact attributes, attributes regarding its hours of operation, etc. Each Facility is defined by a pairing of Location and Organization. - -3. **Location** – Locations are physical places where care can be delivered such as facilities, buildings, wards, rooms, or vehicles. Locations also include jurisdictions such as a village districts or regions. A Location has a unique identifier and may have geographic attributes (address, geocode), attributes regarding its hours of operation, etc. Each Location may be related to one Organization. A location may have a hierarchical relationship with other locations. - -4. **Jurisdiction** – Jurisdictions are political administrative units or other territories over which authority is exercised. A Jurisdiction has a unique identifier, geographic attributes, etc. Jurisdictions include political administrative units such as village districts or regions. Each Jurisdiction is defined by a pairing of Location and Organization. - -5. **Practitioner** – A Practitioner is a health worker such as defined by WHO (in Chapter 1 of the [World Health Report 2006](http://whqlibdoc.who.int/publications/2006/9241563176_eng.pdf)); a Practitioner might be a physician, nurse, pharmacist, community health worker, district health manager, etc. Practitioners have contact and demographic attributes. Each Practitioner may be related to one or more Organizations, one or more Locations and one or more Healthcare Services. Specific attributes may be associated with the Practitioner relationship with these other entities. - -6. **Healthcare Service** – Each healthcare service has a unique identifier. Examples include surgical services, antenatal care services, or primary care services. The combination of a Healthcare Service offered at a Location may have specific attributes including contact person, hours of operation, etc. - -7. **Endpoint** - An Organization may be reachable for electronic data exchange through electronic Endpoint(s). An Endpoint may be a FHIR server, an IHE web services actor, or some other mechanism. If an Organization does not have an Endpoint, it may still be reachable via an Endpoint at its parent Organization or an affiliated Organization. - -8. **OrganizationAffiliation** - An Organization may have relationships with other organizations that are not hierarchical. These relationships may indicate an electronic routing path to other organizations that cannot be reached directly. OrganizationAffiliation can be used to specify relationships such as supply chains or administrative reporting structures. - -The capabilities detailed in this profile support consumer-centric queries such as finding “where is the closest youth mental health services clinic” or “what are the hours of a physiotherapist near my workplace”. In addition, mCSD supports crucial health system management workflows. This can include reporting and analyses, such as “what are my health human resource capacities, by facility, by cadre,” “what are all the services offered at this facility,” or conversely, “where are all the facilities that offer this service.” The mCSD Profile may be employed to support, for example, the Provider Queries listed by the US Office of the National Coordinator as part of the [Standards and -Interoperability Framework](https://www.healthit.gov/topic/interoperability/standards-interoperability-si-framework). In addition, mCSD can enable connectivity by providing service endpoint lookup, such as "What is the FHIR server for this organization?". - -The loosely coupled design and flexible querying capability of the mCSD Profile means it can be deployed within a variety of eHealth architectures and support a wide array of care workflows. - -## 1:46.1 mCSD Actors, Transactions, and Content Modules - -This section defines the actors, transactions, and/or content modules in this profile. Further information about actor and transaction definitions can be found in the IHE Technical Frameworks General Introduction [Appendix A: Actors](https://profiles.ihe.net/GeneralIntro/ch-A.html) and [Appendix B: Transactions](https://profiles.ihe.net/GeneralIntro/ch-B.html). - -Figure 1:46.1-1 shows the actors directly involved in the mCSD Profile and the relevant transactions between them. If needed for context, other actors that may be indirectly involved due to their participation in other related profiles are shown in dotted lines. Actors which have a mandatory grouping are shown in conjoined boxes. - -
-{%include ActorsAndTransactions.svg%} -
-
-**Figure 1:46.1-1: mCSD Actor Diagram** - -Table 1:46.1-1 lists the transactions for each actor directly involved in the mCSD Profile. To claim compliance with this profile, an actor shall support all required transactions (labeled “R”) and may support the optional transactions (labeled “O”). - -**Table 1:46.1-1: mCSD Profile - Actors and Transactions** - -| Actors | Transactions | Initiator or Responder | Optionality | Reference | -| -------------------------------- | ---------------------------------------- | ---------------------- | ----------- | --------------- | -| Care Services Selective Consumer | Find Matching Care Services \[ITI-90\] | Initiator | R | [ITI TF-2: 3.90](ITI-90.html) | -| Care Services Selective Supplier | Find Matching Care Services \[ITI-90\] | Responder | R | [ITI TF-2: 3.90](ITI-90.html) | -| Care Services Update Consumer | Request Care Services Updates \[ITI-91\] | Initiator | R | [ITI TF-2: 3.91](ITI-91.html) | -| Care Services Update Supplier | Request Care Services Updates \[ITI-91\] | Responder | R | [ITI TF-2: 3.91](ITI-91.html) | -{: .grid .table-striped} - -### 1:46.1.1 Actor Descriptions and Actor Profile Requirements - -Most requirements are documented in ITI TF-2: Transactions. This section documents any additional requirements on mCSD actors. - -mCSD supports querying for Organization, Facility, Location, Practitioner, Healthcare Service, OrganizationAffiliation, and Endpoint. However, a Care Services Selective Supplier or Care Service Update Supplier is not required to contain data on all of these. - -#### 1:46.1.1.1 Care Services Selective Consumer - -The Care Services Selective Consumer queries the Care Services Selective Supplier for information about mCSD resources. - -No additional requirements. The following are two example capability statement resources that a Care Services Selective Consumer could support: - -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Selective Consumer](CapabilityStatement-IHE.mCSD.CareServicesSelectiveConsumer.html) -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Selective Consumer Location Distance Option](CapabilityStatement-IHE.mCSD.CareServicesSelectiveConsumer.LocationDistance.html) - -#### 1:46.1.1.2 Care Services Selective Supplier - -The Care Services Selective Supplier processes received queries from Care Services Selective Consumers and returns information about mCSD resources. - -The Care Services Selective Supplier shall publish an `instance` CapabilityStatement at the metadata endpoint following [ITI Appendix Z.3](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.3-capabilitystatement-resource) using the [FHIR capabilities interaction](http://hl7.org/fhir/R4/http.html#capabilities). All supported search parameters and search methods (GET, POST) shall be specified. The [search parameters](ITI-90.html#2390412-message-semantics) and [message semantics](ITI-90.html#2390422-message-semantics) defined in \[ITI-90\] shall be supported, other parameters may be supported. - -This capabilities response will typically include all of the capabilities inclusive of all grouped actors and additional functionality. The following are two examples: - -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Selective Supplier](CapabilityStatement-IHE.mCSD.CareServicesSelectiveSupplier.html) -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Selective Supplier Location Distance Option](CapabilityStatement-IHE.mCSD.CareServicesSelectiveSupplier.LocationDistance.html) - -#### 1:46.1.1.3 Care Services Update Consumer - -The Care Services Update Consumer can query for updates since a previous refresh, to information about mCSD resources from one -or more Care Services Update Suppliers. - -No additional requirements. The following are two example capability statement resources that a Care Services Update Consumer could support: - -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Update Consumer](CapabilityStatement-IHE.mCSD.CareServicesUpdateConsumer.html) -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Update Consumer Location Distance Option](CapabilityStatement-IHE.mCSD.CareServicesUpdateConsumer.LocationDistance.html) - -#### 1:46.1.1.4 Care Services Update Supplier - -The Care Services Update Supplier can provide updates about mCSD resources in response to a refresh request from a Care Services Update Consumer. The updates include new or modified information since a previous refresh. - -The Care Services Update Supplier shall publish an `instance` CapabilityStatement at the metadata endpoint following [ITI Appendix Z.3](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.3-capabilitystatement-resource) using the [FHIR capabilities interaction](http://hl7.org/fhir/R4/http.html#capabilities). -All supported interactions shall be specified. The [search parameters](ITI-91.html#2391412-message-semantics) and [message semantics](ITI-91.html#2391422-message-semantics) defined in \[ITI-91\] shall be supported, other parameters may be supported. - -This capabilities response will typically include all of the capabilities inclusive of all grouped actors and additional functionality. The following are two examples: - -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Update Supplier](CapabilityStatement-IHE.mCSD.CareServicesUpdateSupplier.html) -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Update Supplier Location Distance Option](CapabilityStatement-IHE.mCSD.CareServicesUpdateSupplier.LocationDistance.html) - -## 1:46.2 mCSD Actor Options - -Options that may be selected for each actor in this profile, if any, are listed in Table 1:46.2-1. Dependencies between options when applicable are specified in notes. - -**Table 1:46.2-1: mCSD - Actors and Options** - -| Actor | Option Name | Reference | -| -------------------------------- | ------------------------ | -------------- | -| Care Services Selective Consumer | Location Distance Option | [Section 1:46.2.1](#14621-location-distance-option) | -| Care Services Selective Supplier | Location Distance Option | [Section 1:46.2.1](#14621-location-distance-option) | -| Care Services Update Consumer | No options defined | \-- | -| Care Services Update Supplier | No options defined | \-- | -{: .grid .table-striped} - -### 1:46.2.1 Location Distance Option - -The Location Distance Option enables querying Location resources based on relative distances. - -A Care Services Selective Consumer or Care Services Selective Supplier that supports the Location Distance Option will implement the semantics for the Location Distance Option of the Find Matching Care Services \[ITI-90\] transaction. See [ITI TF-2: 2:3.90.4.1.2.2](ITI-90.html#23904122-organization-resource-message-semantics) and [ITI TF-2: 2:3.90.4.2.2.2](ITI-90.html#23904222-fhir-location-resource-constraints). - -## 1:46.3 mCSD Required Actor Groupings - -An actor from this profile (Column 1) shall implement all of the required transactions and/or content modules in this profile ***in addition to*** ***all*** of the requirements for the grouped actor (Column 2). - -[Section 1:46.5](#1465-mcsd-security-considerations) describes some optional groupings that may be of interest for security considerations and [Section 1:46.6](#1466-mcsd-cross-profile-considerations) describes some optional groupings in other related profiles. - -**Table 1:46.3-1: mCSD - Required Actor Groupings** - -| mCSD Actor | Actor to be grouped with | Reference | Content Bindings Reference | -| -------------------------------- | ------------------------ | --------- | -------------------------- | -| Care Services Selective Consumer | None | \-- | \-- | -| Care Services Selective Supplier | None | \-- | \-- | -| Care Services Update Consumer | None | \-- | \-- | -| Care Services Update Supplier | None | \-- | \-- | -{: .grid .table-striped} - -## 1:46.4 mCSD Overview - -### 1:46.4.1 Concepts - -The Mobile Care Services Discovery (mCSD) Profile supports queries for resources related to care services discovery. The relationship between these entities is illustrated in Figure 1:46.4.1-1. - -![Top-level Relationships between Care Services Entities](mCSDRelationships.png) -
- -**Figure 1:46.4.1-1: Top-level Relationships between Care Services Entities** - -#### 1:46.4.1.1 Create, Update, and Delete Services - -This profile enables tracking of changes to, searching for, and retrieval of, a set of resources. The creation, update, deletion and other maintenance activities of those resources is out of the scope of this profile. - -### 1:46.4.2 Use Cases - -#### 1:46.4.2.1 Use Case \#1: Practitioner Query - -##### 1:46.4.2.1.1 Practitioner Query Use Case Description - -The patient, Vera Brooks, consults with her physician who recommends surgery. The physician can assist the patient in finding a suitable surgeon, taking into consideration the location and specialty of the surgeon. - -##### 1:46.4.2.1.2 Practitioner Query Process Flow - -- Vera Brooks sees her family physician, Dr. West, regarding a recent knee injury. - -- Dr. West diagnoses the problem as a torn ACL and decides to refer Vera to an orthopedic surgeon. - -- Dr. West uses her EMR query tool, which implements a Care Services Selective Consumer to search for orthopedic surgeons within 30km of Vera’s home. - -- The EMR retrieves the information from a Healthcare Worker Registry (HWR) and displays it to Dr. West. - -- Vera and Dr. West decide on an orthopedic surgeon; Dr. West prepares a referral. - -The interactions between the various actors in this use case are shown in Figure 1:46.4.2.1.2-1. - -
-{%include usecase1-processflow.svg%} -
-
- -**Figure 1:46.4.2.1.2-1: Provider Query Use Case** - -#### 1:46.4.2.2 Use Case \#2: Provider Lookup During an Emergency Event - -##### 1:46.4.2.2.1 Provider Lookup During an Emergency Event Use Case Description - -During an emergency event, medical volunteers may report to assist. At an emergency site, the mCSD service can be queried to quickly identify and grant permission to credentialed providers to enter the scene. - -During Hurricane Katrina, health care volunteers were turned away from disaster sites because there was no means available to verify their credentials. During the Ebola outbreak in West Africa, it was unclear which health workers were available and had been trained in clinical care techniques. - -Resources from jurisdictional areas can be reported up to a central location so there is a single point of access. This would make it easier for responders on location to verify the credentials of a reporting health worker. - -##### 1:46.4.2.2.2 Provider Lookup During an Emergency Event Process Flow - - - A jurisdictional (state/district) Care Services Update Supplier will provide data to a central Care Services Update Consumer (National HIE). - - - The National HIE will be a Care Services Update Consumer grouped with a Care Services Selective Supplier. - - - An emergency responder (e.g., police on site controlling access) can use a Care Services Selective Consumer to validate the credentials of a reporting health worker from the central Care Services Update Supplier. - - - Based on the result, the emergency responder can allow or deny access to the reporting health worker. - -The interactions between the various actors in this use case are shown in Figure 1:46.4.2.2.2-1. - -
-{%include usecase2-processflow.svg%} -
-
- -**Figure 1:46.4.2.2.2-1: Federated Data Site Management Workflow** - -#### 1:46.4.2.3 Use Case \#3: Cross-jurisdictional Site Management - -##### 1:46.4.2.3.1 Cross-jurisdictional Site Management Description - -Projects like the U.S. President's Emergency Plan for AIDS Relief (PEPFAR)’s Data for Accountability, Transparency, and Impact (DATIM) need to have public health and service delivery indicators reported from a large number of sites (health facilities, communities, warehouses) within an Operating Unit (country/region). Within an Operating Unit, there are multiple, possibly overlapping, jurisdictions in operation which are managed by multiple organizations (e.g., ministries of health (MoH), faith-based organizations, international non-governmental organizations). The project needs to receive indicator submissions from pre-existing data systems hosted by these organizations. This data exchange requires a way to share site lists and implement identifier mapping between the sites in these lists. - - -
-{%include usecase3-diagram.svg%} -
-
- -**Figure 1:46.4.2.3.1-1: Cross-Jurisdictional Data Exchange** - -##### 1:46.4.2.3.2 Cross-jurisdictional Site Management Process Flow - -An Operating Unit (OU) will run a Care Services Update Consumer and Care Services Update Supplier for a specific geographic area (e.g., country). This Update Consumer will query other organizations (ministries of health, partners) operating in the geographic area to get updated site data for the sites managed by the OU. - - - An OU Update Consumer will query a sub-unit Care Services Update Suppliers (e.g., MoH) to get an updated list of sites under the sub-unit. - - - An OU Update Consumer will query a subunit Care Services Update Suppliers (e.g., partner) to get an updated list of sites under the subunit. - - - The OU Update Consumer will use entity matching to determine if there are duplicated sites in the combined data and flag them for review. (See - [https://wiki.ohie.org/display/documents/OpenHIE+Entity+Matching+Service](https://wiki.ohie.org/display/documents/OpenHIE+Entity+Matching+Service).) - -The interactions between the various actors in this use case are shown -in Figure 1:46.4.2.3.2-1. - -
-{%include usecase3-processflow.svg%} -
-
- -**Figure 1:46.4.2.3.2-1: Cross-jurisdictional Site Management Workflow** - -#### 1:46.4.2.4 Use Case \#4: Master Facility List - -##### 1:46.4.2.4.1 Master Facility List Description - -A developing country has decided to implement a Master Facility List (MFL) based on recommendations from the WHO in the [MFL Resource Package](https://www.who.int/publications/i/item/9789241516495). This resource includes a minimum data set to uniquely identify, locate, and contact a specific facility. Since this will be a single source of information for the country, there may be differing hierarchies that need to be supported for the facilities. For example, one hierarchy would be the administrative hierarchy for the country (region, district, county). Another would be the supply chain hierarchy where hubs may be located separately from administrative regions. Yet another could be a reporting hierarchy used to send data to international organizations. - -##### 1:46.4.2.4.2 Master Facility List Process Flow - -A Master Facility List (MFL) will run a Care Services Update Supplier and Care Services Selective Supplier for an entire country. A Human Resources Information System (HRIS) will run a Care Services Update Consumer to retrieve the list of facilities. A Logistics Management Information System (LMIS) will run a Care Services Update Consumer to retrieve the list of facilities. - -- An HRIS will query the MFL for an updated list of facilities where Practitioners can provide care. - -- An LMIS will query the MFL for an updated list of facilities for the supply chain to deliver health care supplies. - -- The MFL will return updated facilities to each of these systems with multiple hierarchies. - -The interactions between the various actors in this use case are shown in Figure 1:46.4.2.4.1-1. - -
-{%include usecase4-processflow.svg%} -
-
- -**Figure 1:46.4.2.4.2-1: Master Facility List Workflow** - -#### 1:46.4.2.5 Use Case \#5: Health Information Exchange (HIE) Membership Discovery - -##### 1:46.4.2.5.1 Health Information Exchange (HIE) Membership Discovery Description - -In this use case, a healthcare worker needs to identify the organizations active in the State/Province Health Information Exchange (HIE) that have been added since 2017, to make contact with new organizations and negotiate future clinical exchange. - -Membership in an HIE is a more dynamic and transitory business relationship than the "parent-child" hierarchy represented by Organization.partOf. For these more flexible business relationships, the [OrganizationAffiliation](http://hl7.org/fhir/R4/organizationaffiliation.html) resource allows for organizations to relate to each other in non-hierarchical and more dynamic business relationships. Unlike partOf, the relationship is itself a resource, so it can be categorized with codes, status, etc. - -In the example below: -- Organization B has a parent Organization A. -- Organization B has been a part of its State/Province HIE since 2018 and is a member in good standing. - -The `organization` defines a role for the relationship, e.g., "HIE/HIO" or "member", and the `participatingOrganization` fills the role. - -
-{%include usecase5-diagram.svg%} -
-
- -**Figure 1:46.4.2.5.1-1: Organization.partOf vs. Affiliation** - -##### 1:46.4.2.5.2 Health Information Exchange (HIE) Membership Discovery Process Flow - -- A healthcare worker searches for organizations active in the State/Province HIE that have been added since 2017. -- The EMR searches for OrganizationAffiliations where the `organization` is the HIE, `active` is true, and `period.start` is 2017 or later. -- The EMR searches for details on the participating Organizations. -- The EMR presents the results to the healthcare worker. - -The interactions between the various actors in this use case are shown in Figure 1:46.4.2.5.2-1. - -
-{%include usecase5-processflow.svg%} -
-
- -**Figure 1:46.4.2.5.2-1: Health Information Exchange (HIE) Membership Discovery Workflow** - -#### 1:46.4.2.6 Use Case \#6: Health Information Exchange (HIE) Endpoint Discovery - -##### 1:46.4.2.6.1 Health Information Exchange (HIE) Endpoint Discovery Description - -Users in Health IT systems often need to be able to obtain clinical information electronically from outside systems, for example, in preparation for an encounter. This use case describes how a user in a system identifies the organizations a patient has received care from, as well as criteria for the kinds of clinical documents of interest, and then how their EMR queries the directory for a Health Information Exchange (HIE) to search for each organization and a compatible services endpoint the EMR can use. - -An HIE publishes a directory that contains all of its member organizations and their electronic endpoints. - -Note: Guidance for usage of endpoints in directories is provided [here](#1468-mcsd-endpoint-usage-considerations). - -- Endpoints are not limited to RESTful FHIR servers; they may point to systems that implement other mechanisms. This IG provides two profiles: - [a general endpoint](StructureDefinition-IHE.mCSD.Endpoint.html), and - [an endpoint to an IHE Document Sharing actor](StructureDefinition-IHE.mCSD.Endpoint.DocShare.html). -- Organizations might support one or many communication channels, each of which might have one or more distinct endpoints. For example, a FHIR communication channel might require only a single endpoint (i.e., a single [Service Base URL](https://www.hl7.org/fhir/http.html#general)), while an IHE XCA communication channel might require separate endpoints for each transaction. - -The diagram below shows an excerpt of the HIE directory, showing one participant in the HIE that implements IHE XCA with two Endpoints, and another that only uses one. - -
-{%include usecase6-diagram.svg%} -
-
- -**Figure 1:46.4.2.6.1-1: Health Information Exchange** - -##### 1:46.4.2.6.2 Health Information Exchange (HIE) Endpoint Discovery Process Flow - -- In preparation for a patient visit, a healthcare worker knows and identifies the organizations that have provided care for this patient, and identifies document types of interest. -- The EMR will query the HIE directory for the relevant organizations and their endpoints. -- For each organization obtained, the EMR will check for endpoints that support the needed XCA transactions, and make requests against these endpoints to obtain clinical documents. -- The EMR presents the obtained documents to the healthcare worker, who reviews them. - -The interactions between the various actors in this use case are shown in Figure 1:46.4.2.6.2-1. - -
-{%include usecase6-processflow.svg%} -
-
- -**Figure 1:46.4.2.6.2-1: Health Information Exchange (HIE) Endpoint Discovery Workflow** - -## 1:46.5 mCSD Security Considerations - -Actors are expected to follow the recommendations and requirements found in [ITI TF-2: Appendix Z.8 “Mobile Security Considerations”](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.8-mobile-security-considerations). - -The resources exchanged in this profile may contain information which pose a privacy risk, or in some cases, a safety risk, to providers and other personnel, as well as patients. For example, practitioner phone numbers and home addresses may be conveyed. Implementers should determine what data will be exposed by the system and what level of public access there will be if any. - -The Endpoint Resources exchanged in this profile will expose information about the particular APIs and web services running on the underlying host systems. This might attract malicious activity or provide hints to potential attackers on how to attack a particular host system. Implementers should consider this when determining the access policies for these Resources. System administrators for the underlying host systems must follow industry best practices for authentication, authorization, auditing, timely application of software patches, etc. - -There are many reasonable methods of security for interoperability transactions which can be implemented without modifying the characteristics of the transactions in the mCSD Profile. The use of TLS is encouraged, specifically the use of the ATNA Profile (see [ITI TF-1: 9](https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html)). - -User authentication on mobile devices and browsers is typically handled by more lightweight authentication schemes such as HTTP Authentication, OAuth 2.0, or OpenID Connect. IHE has a set of profiles for user authentication including Internet User Authentication (IUA) for REST-based authentication. The network communication security and user authentication are layered in the HTTP transport layer. - -## 1:46.6 mCSD Cross Profile Considerations - -### 1:46.6.1 Aggregate Data Exchange – ADX - -The IHE QRPH Aggregate Data Exchange (ADX) Profile enables reporting of public health and service delivery indicators in various locations. A reporting system may play the role of a Care Services Update Consumer to ensure that it has an updated list of the resources for the reporting locations. - -Additionally, a service that contains information on practitioners (and may be a Care Services Selective Supplier or Care Services Update Supplier) can also be used to generate an ADX message to satisfy the use case of a district health manager running an aggregate report on staffing levels by facility and health worker type from the ITI Care Services Discovery (CSD) Profile. - -### 1:46.6.2 Care Services Discovery – CSD - -A Care Services Directory in the CSD Profile can be grouped with the Care Services Update Supplier from mCSD. The CSD Care Services InfoManager could implement the mCSD Care Services Update Consumer and the Care Services Selective Supplier Actors. The CSD Service Finder could implement the mCSD Care Services Selective Consumer. This enables the CSD actors to allow RESTful transactions without having to change the underlying data store. - -### 1:46.6.3 Health Provider Directory – HPD - -A Provider Information Source in HPD can also implement the Care Services Update Supplier from mCSD. Note that in this case the Provider Information Source would be queried for updates instead of pushing the updates to the Consumer. The HPD Provider Information Directory could implement the mCSD Care Services Update Consumer and the Care Services Selective Supplier Actors. The HPD Provider Information Consumer could implement the mCSD Care Services Selective Consumer. This enables the HPD actors to allow RESTful transactions without having to change the underlying data store. - -### 1:46.6.4 Mobile Alert Communication Management – mACM - -The mACM Profile defines the means to send an alert to practitioners. The mCSD Profile provides a way to query that list of practitioners. A mACM Alert Reporter can be grouped with a Care Services Update Consumer or a Care Services Selective Consumer to ensure that it has an updated list of practitioners. - -## 1:46.7 mCSD Deployment Considerations - -### 1:46.7.1 Simple Deployment - -A deployment may only have a single server that will maintain data. In this case, you would only need the Care Services Selective Supplier (or Care Services Update Supplier) to send search results back to one or more Care Services Selective Consumers (or Care Services Update Consumer). See Figure 1:46.7.1-1 below. - -
-{%include simple-deployment.svg%} -
-
- -**Figure 1:46.7.1-1: Simple Deployment** - -### 1:46.7.2 Federated and Cross-Jurisdictional Deployments - -A Federated Deployment has multiple levels of the Care Services Update Suppliers linked to Care Services Update Consumers. These Update Consumers may also support being Care Services Update Suppliers so that higher level Update Consumers can receive their updates. They may also support being a Care Services Selective Supplier so that Selective Consumer clients can query that level of information. See Figure 1:46.7.2-1 below. - -Interrelated content is maintained by the Care Services Update Consumer. The Care Services Update Consumer routinely obtains new or updated content from Care Services Update Suppliers by polling them. These updates may refresh a data cache which the Update Consumer maintains. The Update Consumer’s cache is refreshed at an appropriate interval specified by the implementing jurisdiction. The implementing jurisdiction will consider the implications of out of date information when setting the refresh interval between cache updates. The normal delays in updating listings will also be part of this consideration. - -The various data sources would maintain definitive data regarding one or more of: Organization, Location, Healthcare Service, or Practitioner and implement the Care Services Update Supplier. These Care Services Update Suppliers would respond to a Care Services Update Consumer’s request for new or updated content since a specified date and time. To support this capability, a Care Services Update Supplier should support time stamped updates. Data elements that are deprecated should not simply be deleted, but rather are updated to an appropriate status indicating their deprecation. - -This deployment may also have cross-jurisdictional considerations if any of the Update Suppliers have overlap in the data they manage. In this instance, the Care Services Update Consumer would need to resolve any conflicts before sharing this information as either a Care Services Update Supplier or a Care Services Selective Supplier. The way in which these conflicts are resolved is defined by the implementing jurisdiction of the Care Services Update Consumer. - -![Federated and Cross Jurisdictional Deployment](FederatedDeployment.png) -
- -**Figure 1:46.7.2-1: Federated and Cross Jurisdictional Deployment** - -The Care Services Selective Consumer is the actor that queries for information about interrelated care services. These queries are sent to the Care Services Selective Supplier who develops a response based on the content in its local data store. When a Care Services Selective Supplier is combined with a Care Services Update Consumer (Global and Country servers from Figure 1:46.7.2-1), it should maintain a cache of the aggregated information from all the configured Care Services Update Suppliers it is linked to. - -In order for the Care Services Update Consumer’s (Global and Country servers) cached content to be able to serve its role as an interlinked data source, the following conditions should be met by Care Services Update Suppliers who maintain content. - -1. Implementing jurisdictions may mandate terminologies for Organization Type, Service Type, Location Type, Location Status, Practitioner Type, Practitioner Status, Contact Point Type, Credential Type, Specialization Code, and language code. Care Services Update Suppliers would be configurable to use these terminologies, where mandated. In the case of a cross jurisdictional deployment, mapping between the terminology used by the various jurisdictions may need to be maintained. - -2. Implementing jurisdictions may mandate conventions regarding the types, components and formatting of Name, Address and Address Line elements. Care Services Update Suppliers would be configurable to use these formatting conventions, where mandated. - -3. Implementing jurisdictions may mandate the source of truth regarding Organization ID, Healthcare Service ID, Location ID and Practitioner ID. Care Services Update Suppliers would ensure that all cross-referenced IDs match corresponding resources in the jurisdictionally mandated sources of truth. - -For guidance on handling challenges regarding the representation of names across multiple languages and in different cultures, refer to the [ITI TF-2: 3.24.5.2.3.1](https://profiles.ihe.net/ITI/TF/Volume2/ITI-24.html#3.24.5.2.3.1). This section in the ITI Technical Framework describes the use of the language tag as documented in IETF RFC1766 and the HL7 XCN name data type. - -#### 1:46.7.2.1 Terminology Services - -All referenced terminologies from a Care Services Selective Supplier or Care Services Update Supplier may be pre-coordinated or they may be resolvable from one or more terminology services. Though it is out of scope of the mCSD Profile to define the means of interacting with a terminology service, this could be provided, for example, through the -[Sharing Valuesets, Codes, and Maps (SVCM) Profile](https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_SVCM.pdf). - -## 1:46.8 mCSD Endpoint Usage Considerations - -This section provides guidance for populating and using Endpoint resources in an mCSD directory to enable electronic communication, for example defining local points of connectivity within a community, or defining a Health Information Exchange (HIE) that allows multiple communities to interoperate. - -Many current Endpoint directories based on FHIR are purpose-built, which is to say they are deployed to a server that only hosts Organization and Endpoint resources, and only for the use case of Endpoint lookup. For this reason, directories often reflect network details directly in the Organization resource, such as: -- The organization's role in the network, like participant or sub-participant, expressed as the type of organization. -- The organization's relationship to its connectivity vendor, expressed as the organization hierarchy (i.e., partOf). -- The organization's connectivity state as an extension. -- Supported profiles, purposes of use, etc. as extensions. -- The organization's identity as a home community ID, for use in IHE Document Sharing profiles. - -When the organization's structure and its network capabilities need to vary independently (e.g., an organization uses two connectivity vendors), directories typically handle this by creating parallel instances of the Organization resource that then have to be merged by custom code to display. - -We anticipate these conflicts increasing over time due to many forces: -- Implementers taking advantage of profiles like mCSD to represent more comprehensive organizational and personnel structures. -- Implementers scaling by delegating maintenance of organization sub-trees to the organizations themselves. -- Directories consolidating/federating over time into more comprehensive "phonebooks", where a given organization participates in multiple HIEs. One example would be the USA ONC TEFCA Recognized Coordinating Entity, which will be maintaining a directory that consists of entries supplied by each Qualified Health Information Network (QHIN). - -In this guidance, we allow organization structure and network details to vary independently by moving network details out of the Organization and into the Endpoint and OrganizationAffiliation resources. - -##### 1:46.8.1 Endpoint to an Organization - -The simplest usage model for a client is when the organization it needs to contact has a dedicated Endpoint resource in Organization.endpoint. Because this Endpoint is Organization-specific, it does not matter to the client who hosts it. Some examples follow. - -Note: The managingOrganization of an Endpoint is who users need to contact for support. It may or may not be the same as the organization that hosts it. Since hosting is not reflected in the directory, we are indicating it in the diagrams below by the URLs. - -Organization A hosts its own Endpoint: -
-{%include dir-org-specific-endpoint-self.svg%} -
-
-**Figure 1:46.8.1-1: Organization-specific Endpoint Hosted by the Organization** - -Organization A is directly reachable by an endpoint hosted by its parent Organization B: -
-{%include dir-org-specific-endpoint-parent.svg%} -
-
-**Figure 1:46.8.1-2: Organization-specific Endpoint Hosted by Parent** - -Organization C is directly reachable by an endpoint hosted by its affiliated Organization D: -
-{%include dir-org-specific-endpoint-affil.svg%} -
-
-**Figure 1:46.8.1-3: Organization-specific Endpoint Hosted by Affiliation** - -Organization E is directly reachable by an endpoint hosted by a hidden (i.e., not in the directory) Intermediary F: -
-{%include dir-org-specific-endpoint-inter.svg%} -
-
-**Figure 1:46.8.1-4: Organization-specific Endpoint Hosted by Hidden Intermediary** - -##### 1:46.8.2 Endpoint to a Structure - -When an Organization with an Endpoint has a complex structure, for example, sub-organizations, clients can often make use of this structure: - -
-{%include dir-endpoint-to-org-hierarchy.svg%} -
-
- -**Figure 1:46.8.2-1: Endpoint to Organizational Hierarchy** - -Typical directories will take an organizational hierarchy to imply accessibility to parts of the structure, for example: -- For FHIR REST endpoints, the URL is simply the Service Base URL as specified in [FHIR R4 3.1.0.1.2](http://hl7.org/fhir/R4/http.html#general). Clients can expect to find resources related to Organizations A, B and C. -- For XCA endpoints, a client querying Organization A for documents (e.g., using \[ITI-38\]) may receive documents from Organizations A, B and C. If these organizations have identifiers of type Home Community ID in the directory, clients can expect to see these identifiers in the returned document metadata. -- For XDR endpoints, a client sending a Provide and Register Document Set-b (\[ITI-41\]) request to Organization A can optionally specify Organizations B and/or C in intendedRecipient. -- For MHD endpoints, a client sending a Provide Document Bundle (\[ITI-65\]) request to Organization A can optionally specify Organizations B and/or C in intendedRecipient. - -Specific details of addressing to federated recipients are out of the scope of this IG. - -Examples of this kind of federated structure are shown in [ITI TF-1: Appendix E.9](https://profiles.ihe.net/ITI/TF/Volume1/ch-E.html#E.9.3), for XCA Responding Gateways. - -By contrast, OrganizationAffiliations by themselves do not necessarily imply this kind of electronic accessibility. For this reason, this IG defines the code "DocShare-federate", which explicitly declares that the participatingOrganization is accessible as a federated organization via the OrganizationAffiliation.endpoint. - -The following diagram shows the same accessibility, but using OrganizationAffiliation. - -
-{%include dir-endpoint-to-org-affiliates.svg%} -
-
- -**Figure 1:46.8.2-2: Endpoint to Organizational Affiliates** - -In addition, these mechanisms may be combined. This may be useful, for example, when adding an existing organizational structure to an HIE. - -
-{%include dir-endpoint-to-hybrid-org-structure.svg%} -
-
- -**Figure 1:46.8.2-3: Endpoint to Hybrid Organizational Structure** - -##### 1:46.8.3 Grouping Actors - -Grouped actors may be represented as well, although not explicitly. In the following example, Participant A is reachable by either an MHD endpoint or XDR endpoints. The directory -does not reflect which endpoint is the adapter or the adaptee. - -
-{%include dir-endpoint-xdr-mhd.svg%} -
-
- -**Figure 1:46.8.3-1: Endpoints to Grouped Actors** - -##### 1:46.8.4 Endpoint Discovery Usage - -The following example shows the steps used by a Care Services Selective Consumer to navigate a directory to find suitable electronic service Endpoints to some desired Organizations. In this example, a "suitable" Endpoint means it supports an IHE Document Sharing profile, and is based on .connectionType, .extension:specificType, .payloadType, .payloadMimeType, and status (both Endpoint.status as well as the actual status of the electronic service). The example uses the [mCSD-profiled OrganizationAffiliation] StructureDefinition-IHE.mCSD.OrganizationAffiliation.DocShare.html) that indicates federated connectivity for Document Sharing (e.g., affiliated organizations may be addressed as intendedRecipient). The pseudocode below uses a depth-first, first-match search, and does not protect against loops. - -Until a suitable Endpoint is found or the search is complete, check the following in this order: -- Locate the desired Organization resource. -- Check if it has a suitable Organization.endpoint. -- Find OrganizationAffiliation resources where the Organization is the .participatingOrganization, and OrganizationAffiliation.code = DocShare-federate. -- For each OrganizationAffiliation found: - - Check if it has a suitable OrganizationAffiliation.endpoint. - - Check if it has a suitable OrganizationAffiliation.organization.endpoint. - - Continue searching for a suitable Endpoint by traversing the OrganizationAffiliation resources recursively (i.e., where the OrganizationAffiliation.organization of the current resource is the .participatingOrganization of the next resource). -- If there is an Organization.partOf (i.e., a parent), check if it has a suitable Organization.endpoint. - - Continue searching for a suitable Endpoint by traversing Organization.partOf recursively. - -Rather than a first-match search, the Care Services Selective Consumer might search for and decide among multiple electronic paths to the same Organization. For example: -- It finds a suitable Endpoint resource for the target Organization, but instead uses an Endpoint for an Organization two levels higher to make a broader search for records. -- It finds suitable Endpoint resources for equivalent mechanisms, XDR \[ITI-41\] and MHD \[ITI-65\], and chooses MHD as the preferred transaction. -- It finds suitable Endpoint resources to the same Organization via two different HIEs, and prefers one HIE based on lower fees and authorization differences. diff --git a/input/pagecontent/ihepagecontent/sor-volume-1.md b/input/pagecontent/ihepagecontent/sor-volume-1.md deleted file mode 100644 index 0452c92..0000000 --- a/input/pagecontent/ihepagecontent/sor-volume-1.md +++ /dev/null @@ -1,559 +0,0 @@ - -The Mobile Care Services Discovery (mCSD) Profile supports discovery of care services resources using a RESTful interface in interrelated, federated environments. - -Use cases and solutions using mCSD are outlined in the [mCSD White Paper](https://profiles.ihe.net/ITI/papers/mCSD/index.html). - -The profile supports querying for: - -1. **Organization** – Organizations are “umbrella” entities; these may be considered the administrative bodies under whose auspices care services are provided such as Healthcare Information Exchanges(HIEs), Integrated Delivery Networks (IDNs), Non-Government Organizations (NGOs), Faith-Based Organizations (FBOs) or even a one-physician family practice. An organization has a unique identifier and may have additional administrative attributes such as contact person, mailing address, etc. Departments of an institution, or other administrative units, may be represented as child Organizations of a parent Organization. - - **SOR IE Organization** – is reflected as a Jurisdiction instead of Organization (see [Jurisdiction](Jurisdiction)) - - **SOR SI Organization** – is reflected as a Facility instead of Organization (see [Facility](Facility)) - - **SOR OE Organization** – is reflected as a real Organization with [Location](Location)s and [Endpoint](Endpoint)s - -2. **Facility** – Facilities are physical care delivery sites such as hospitals, clinics, health outposts, physician offices, labs, pharmacies, etc. A Facility has a unique identifier, geographic attributes (address, geocode), contact attributes, attributes regarding its hours of operation, etc. Each Facility is defined by a pairing of Location and Organization. - - **SOR SI Organization** – is reflected as a Facility instead of Organization (see [Facility](Facility)) - -3. **Location** – Locations are physical places where care can be delivered such as facilities, buildings, wards, rooms, or vehicles. Locations also include jurisdictions such as a village districts or regions. A Location has a unique identifier and may have geographic attributes (address, geocode), attributes regarding its hours of operation, etc. Each Location may be related to one Organization. A location may have a hierarchical relationship with other locations. - -4. **Jurisdiction** – Jurisdictions are political administrative units or other territories over which authority is exercised. A Jurisdiction has a unique identifier, geographic attributes, etc. Jurisdictions include political administrative units such as village districts or regions. Each Jurisdiction is defined by a pairing of Location and Organization. - - **SOR IE Organization** – is reflected as a Jurisdiction instead of Organization (see [Jurisdiction](Jurisdiction)) - -5. **Practitioner** – A Practitioner is a health worker such as defined by WHO (in Chapter 1 of the [World Health Report 2006](http://whqlibdoc.who.int/publications/2006/9241563176_eng.pdf)); a Practitioner might be a physician, nurse, pharmacist, community health worker, district health manager, etc. Practitioners have contact and demographic attributes. Each Practitioner may be related to one or more Organizations, one or more Locations and one or more Healthcare Services. Specific attributes may be associated with the Practitioner relationship with these other entities. - -6. **Healthcare Service** – Each healthcare service has a unique identifier. Examples include surgical services, antenatal care services, or primary care services. The combination of a Healthcare Service offered at a Location may have specific attributes including contact person, hours of operation, etc. - -7. **Endpoint** - An Organization may be reachable for electronic data exchange through electronic Endpoint(s). An Endpoint may be a FHIR server, an IHE web services actor, or some other mechanism. If an Organization does not have an Endpoint, it may still be reachable via an Endpoint at its parent Organization or an affiliated Organization. - -8. **OrganizationAffiliation** - An Organization may have relationships with other organizations that are not hierarchical. These relationships may indicate an electronic routing path to other organizations that cannot be reached directly. OrganizationAffiliation can be used to specify relationships such as supply chains or administrative reporting structures. - -The capabilities detailed in this profile support consumer-centric queries such as finding “where is the closest youth mental health services clinic” or “what are the hours of a physiotherapist near my workplace”. In addition, mCSD supports crucial health system management workflows. This can include reporting and analyses, such as “what are my health human resource capacities, by facility, by cadre,” “what are all the services offered at this facility,” or conversely, “where are all the facilities that offer this service.” The mCSD Profile may be employed to support, for example, the Provider Queries listed by the US Office of the National Coordinator as part of the [Standards and -Interoperability Framework](https://www.healthit.gov/topic/interoperability/standards-interoperability-si-framework). In addition, mCSD can enable connectivity by providing service endpoint lookup, such as "What is the FHIR server for this organization?". - -The loosely coupled design and flexible querying capability of the mCSD Profile means it can be deployed within a variety of eHealth architectures and support a wide array of care workflows. - -## 1:46.1 mCSD Actors, Transactions, and Content Modules - -This section defines the actors, transactions, and/or content modules in this profile. Further information about actor and transaction definitions can be found in the IHE Technical Frameworks General Introduction [Appendix A: Actors](https://profiles.ihe.net/GeneralIntro/ch-A.html) and [Appendix B: Transactions](https://profiles.ihe.net/GeneralIntro/ch-B.html). - -Figure 1:46.1-1 shows the actors directly involved in the mCSD Profile and the relevant transactions between them. If needed for context, other actors that may be indirectly involved due to their participation in other related profiles are shown in dotted lines. Actors which have a mandatory grouping are shown in conjoined boxes. - -
-{%include ActorsAndTransactions.svg%} -
-
-**Figure 1:46.1-1: mCSD Actor Diagram** - -Table 1:46.1-1 lists the transactions for each actor directly involved in the mCSD Profile. To claim compliance with this profile, an actor shall support all required transactions (labeled “R”) and may support the optional transactions (labeled “O”). - -**Table 1:46.1-1: mCSD Profile - Actors and Transactions** - -| Actors | Transactions | Initiator or Responder | Optionality | Reference | -| -------------------------------- | ---------------------------------------- | ---------------------- | ----------- | --------------- | -| Care Services Selective Consumer | Find Matching Care Services \[ITI-90\] | Initiator | R | [ITI TF-2: 3.90](ITI-90.html) | -| Care Services Selective Supplier | Find Matching Care Services \[ITI-90\] | Responder | R | [ITI TF-2: 3.90](ITI-90.html) | -| Care Services Update Consumer | Request Care Services Updates \[ITI-91\] | Initiator | R | [ITI TF-2: 3.91](ITI-91.html) | -| Care Services Update Supplier | Request Care Services Updates \[ITI-91\] | Responder | R | [ITI TF-2: 3.91](ITI-91.html) | -{: .grid .table-striped} - -### 1:46.1.1 Actor Descriptions and Actor Profile Requirements - -Most requirements are documented in ITI TF-2: Transactions. This section documents any additional requirements on mCSD actors. - -mCSD supports querying for Organization, Facility, Location, Practitioner, Healthcare Service, OrganizationAffiliation, and Endpoint. However, a Care Services Selective Supplier or Care Service Update Supplier is not required to contain data on all of these. - -#### 1:46.1.1.1 Care Services Selective Consumer - -The Care Services Selective Consumer queries the Care Services Selective Supplier for information about mCSD resources. - -No additional requirements. The following are two example capability statement resources that a Care Services Selective Consumer could support: - -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Selective Consumer](CapabilityStatement-IHE.mCSD.CareServicesSelectiveConsumer.html) -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Selective Consumer Location Distance Option](CapabilityStatement-IHE.mCSD.CareServicesSelectiveConsumer.LocationDistance.html) - -#### 1:46.1.1.2 Care Services Selective Supplier - -The Care Services Selective Supplier processes received queries from Care Services Selective Consumers and returns information about mCSD resources. - -The Care Services Selective Supplier shall publish an `instance` CapabilityStatement at the metadata endpoint following [ITI Appendix Z.3](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.3-capabilitystatement-resource) using the [FHIR capabilities interaction](http://hl7.org/fhir/R4/http.html#capabilities). All supported search parameters and search methods (GET, POST) shall be specified. The [search parameters](ITI-90.html#2390412-message-semantics) and [message semantics](ITI-90.html#2390422-message-semantics) defined in \[ITI-90\] shall be supported, other parameters may be supported. - -This capabilities response will typically include all of the capabilities inclusive of all grouped actors and additional functionality. The following are two examples: - -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Selective Supplier](CapabilityStatement-IHE.mCSD.CareServicesSelectiveSupplier.html) -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Selective Supplier Location Distance Option](CapabilityStatement-IHE.mCSD.CareServicesSelectiveSupplier.LocationDistance.html) - -#### 1:46.1.1.3 Care Services Update Consumer - -The Care Services Update Consumer can query for updates since a previous refresh, to information about mCSD resources from one -or more Care Services Update Suppliers. - -No additional requirements. The following are two example capability statement resources that a Care Services Update Consumer could support: - -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Update Consumer](CapabilityStatement-IHE.mCSD.CareServicesUpdateConsumer.html) -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Update Consumer Location Distance Option](CapabilityStatement-IHE.mCSD.CareServicesUpdateConsumer.LocationDistance.html) - -#### 1:46.1.1.4 Care Services Update Supplier - -The Care Services Update Supplier can provide updates about mCSD resources in response to a refresh request from a Care Services Update Consumer. The updates include new or modified information since a previous refresh. - -The Care Services Update Supplier shall publish an `instance` CapabilityStatement at the metadata endpoint following [ITI Appendix Z.3](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.3-capabilitystatement-resource) using the [FHIR capabilities interaction](http://hl7.org/fhir/R4/http.html#capabilities). -All supported interactions shall be specified. The [search parameters](ITI-91.html#2391412-message-semantics) and [message semantics](ITI-91.html#2391422-message-semantics) defined in \[ITI-91\] shall be supported, other parameters may be supported. - -This capabilities response will typically include all of the capabilities inclusive of all grouped actors and additional functionality. The following are two examples: - -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Update Supplier](CapabilityStatement-IHE.mCSD.CareServicesUpdateSupplier.html) -- [IHE ITI Mobile Care Services Discovery (mCSD) - Care Services Update Supplier Location Distance Option](CapabilityStatement-IHE.mCSD.CareServicesUpdateSupplier.LocationDistance.html) - -## 1:46.2 mCSD Actor Options - -Options that may be selected for each actor in this profile, if any, are listed in Table 1:46.2-1. Dependencies between options when applicable are specified in notes. - -**Table 1:46.2-1: mCSD - Actors and Options** - -| Actor | Option Name | Reference | -| -------------------------------- | ------------------------ | -------------- | -| Care Services Selective Consumer | Location Distance Option | [Section 1:46.2.1](#14621-location-distance-option) | -| Care Services Selective Supplier | Location Distance Option | [Section 1:46.2.1](#14621-location-distance-option) | -| Care Services Update Consumer | No options defined | \-- | -| Care Services Update Supplier | No options defined | \-- | -{: .grid .table-striped} - -### 1:46.2.1 Location Distance Option - -The Location Distance Option enables querying Location resources based on relative distances. - -A Care Services Selective Consumer or Care Services Selective Supplier that supports the Location Distance Option will implement the semantics for the Location Distance Option of the Find Matching Care Services \[ITI-90\] transaction. See [ITI TF-2: 2:3.90.4.1.2.2](ITI-90.html#23904122-organization-resource-message-semantics) and [ITI TF-2: 2:3.90.4.2.2.2](ITI-90.html#23904222-fhir-location-resource-constraints). - -## 1:46.3 mCSD Required Actor Groupings - -An actor from this profile (Column 1) shall implement all of the required transactions and/or content modules in this profile ***in addition to*** ***all*** of the requirements for the grouped actor (Column 2). - -[Section 1:46.5](#1465-mcsd-security-considerations) describes some optional groupings that may be of interest for security considerations and [Section 1:46.6](#1466-mcsd-cross-profile-considerations) describes some optional groupings in other related profiles. - -**Table 1:46.3-1: mCSD - Required Actor Groupings** - -| mCSD Actor | Actor to be grouped with | Reference | Content Bindings Reference | -| -------------------------------- | ------------------------ | --------- | -------------------------- | -| Care Services Selective Consumer | None | \-- | \-- | -| Care Services Selective Supplier | None | \-- | \-- | -| Care Services Update Consumer | None | \-- | \-- | -| Care Services Update Supplier | None | \-- | \-- | -{: .grid .table-striped} - -## 1:46.4 mCSD Overview - -### 1:46.4.1 Concepts - -The Mobile Care Services Discovery (mCSD) Profile supports queries for resources related to care services discovery. The relationship between these entities is illustrated in Figure 1:46.4.1-1. - -![Top-level Relationships between Care Services Entities](mCSDRelationships.png) -
- -**Figure 1:46.4.1-1: Top-level Relationships between Care Services Entities** - -#### 1:46.4.1.1 Create, Update, and Delete Services - -This profile enables tracking of changes to, searching for, and retrieval of, a set of resources. The creation, update, deletion and other maintenance activities of those resources is out of the scope of this profile. - -### 1:46.4.2 Use Cases - -#### 1:46.4.2.1 Use Case \#1: Practitioner Query - -##### 1:46.4.2.1.1 Practitioner Query Use Case Description - -The patient, Vera Brooks, consults with her physician who recommends surgery. The physician can assist the patient in finding a suitable surgeon, taking into consideration the location and specialty of the surgeon. - -##### 1:46.4.2.1.2 Practitioner Query Process Flow - -- Vera Brooks sees her family physician, Dr. West, regarding a recent knee injury. - -- Dr. West diagnoses the problem as a torn ACL and decides to refer Vera to an orthopedic surgeon. - -- Dr. West uses her EMR query tool, which implements a Care Services Selective Consumer to search for orthopedic surgeons within 30km of Vera’s home. - -- The EMR retrieves the information from a Healthcare Worker Registry (HWR) and displays it to Dr. West. - -- Vera and Dr. West decide on an orthopedic surgeon; Dr. West prepares a referral. - -The interactions between the various actors in this use case are shown in Figure 1:46.4.2.1.2-1. - -
-{%include usecase1-processflow.svg%} -
-
- -**Figure 1:46.4.2.1.2-1: Provider Query Use Case** - -#### 1:46.4.2.2 Use Case \#2: Provider Lookup During an Emergency Event - -##### 1:46.4.2.2.1 Provider Lookup During an Emergency Event Use Case Description - -During an emergency event, medical volunteers may report to assist. At an emergency site, the mCSD service can be queried to quickly identify and grant permission to credentialed providers to enter the scene. - -During Hurricane Katrina, health care volunteers were turned away from disaster sites because there was no means available to verify their credentials. During the Ebola outbreak in West Africa, it was unclear which health workers were available and had been trained in clinical care techniques. - -Resources from jurisdictional areas can be reported up to a central location so there is a single point of access. This would make it easier for responders on location to verify the credentials of a reporting health worker. - -##### 1:46.4.2.2.2 Provider Lookup During an Emergency Event Process Flow - - - A jurisdictional (state/district) Care Services Update Supplier will provide data to a central Care Services Update Consumer (National HIE). - - - The National HIE will be a Care Services Update Consumer grouped with a Care Services Selective Supplier. - - - An emergency responder (e.g., police on site controlling access) can use a Care Services Selective Consumer to validate the credentials of a reporting health worker from the central Care Services Update Supplier. - - - Based on the result, the emergency responder can allow or deny access to the reporting health worker. - -The interactions between the various actors in this use case are shown in Figure 1:46.4.2.2.2-1. - -
-{%include usecase2-processflow.svg%} -
-
- -**Figure 1:46.4.2.2.2-1: Federated Data Site Management Workflow** - -#### 1:46.4.2.3 Use Case \#3: Cross-jurisdictional Site Management - -##### 1:46.4.2.3.1 Cross-jurisdictional Site Management Description - -Projects like the U.S. President's Emergency Plan for AIDS Relief (PEPFAR)’s Data for Accountability, Transparency, and Impact (DATIM) need to have public health and service delivery indicators reported from a large number of sites (health facilities, communities, warehouses) within an Operating Unit (country/region). Within an Operating Unit, there are multiple, possibly overlapping, jurisdictions in operation which are managed by multiple organizations (e.g., ministries of health (MoH), faith-based organizations, international non-governmental organizations). The project needs to receive indicator submissions from pre-existing data systems hosted by these organizations. This data exchange requires a way to share site lists and implement identifier mapping between the sites in these lists. - - -
-{%include usecase3-diagram.svg%} -
-
- -**Figure 1:46.4.2.3.1-1: Cross-Jurisdictional Data Exchange** - -##### 1:46.4.2.3.2 Cross-jurisdictional Site Management Process Flow - -An Operating Unit (OU) will run a Care Services Update Consumer and Care Services Update Supplier for a specific geographic area (e.g., country). This Update Consumer will query other organizations (ministries of health, partners) operating in the geographic area to get updated site data for the sites managed by the OU. - - - An OU Update Consumer will query a sub-unit Care Services Update Suppliers (e.g., MoH) to get an updated list of sites under the sub-unit. - - - An OU Update Consumer will query a subunit Care Services Update Suppliers (e.g., partner) to get an updated list of sites under the subunit. - - - The OU Update Consumer will use entity matching to determine if there are duplicated sites in the combined data and flag them for review. (See - [https://wiki.ohie.org/display/documents/OpenHIE+Entity+Matching+Service](https://wiki.ohie.org/display/documents/OpenHIE+Entity+Matching+Service).) - -The interactions between the various actors in this use case are shown -in Figure 1:46.4.2.3.2-1. - -
-{%include usecase3-processflow.svg%} -
-
- -**Figure 1:46.4.2.3.2-1: Cross-jurisdictional Site Management Workflow** - -#### 1:46.4.2.4 Use Case \#4: Master Facility List - -##### 1:46.4.2.4.1 Master Facility List Description - -A developing country has decided to implement a Master Facility List (MFL) based on recommendations from the WHO in the [MFL Resource Package](https://www.who.int/publications/i/item/9789241516495). This resource includes a minimum data set to uniquely identify, locate, and contact a specific facility. Since this will be a single source of information for the country, there may be differing hierarchies that need to be supported for the facilities. For example, one hierarchy would be the administrative hierarchy for the country (region, district, county). Another would be the supply chain hierarchy where hubs may be located separately from administrative regions. Yet another could be a reporting hierarchy used to send data to international organizations. - -##### 1:46.4.2.4.2 Master Facility List Process Flow - -A Master Facility List (MFL) will run a Care Services Update Supplier and Care Services Selective Supplier for an entire country. A Human Resources Information System (HRIS) will run a Care Services Update Consumer to retrieve the list of facilities. A Logistics Management Information System (LMIS) will run a Care Services Update Consumer to retrieve the list of facilities. - -- An HRIS will query the MFL for an updated list of facilities where Practitioners can provide care. - -- An LMIS will query the MFL for an updated list of facilities for the supply chain to deliver health care supplies. - -- The MFL will return updated facilities to each of these systems with multiple hierarchies. - -The interactions between the various actors in this use case are shown in Figure 1:46.4.2.4.1-1. - -
-{%include usecase4-processflow.svg%} -
-
- -**Figure 1:46.4.2.4.2-1: Master Facility List Workflow** - -#### 1:46.4.2.5 Use Case \#5: Health Information Exchange (HIE) Membership Discovery - -##### 1:46.4.2.5.1 Health Information Exchange (HIE) Membership Discovery Description - -In this use case, a healthcare worker needs to identify the organizations active in the State/Province Health Information Exchange (HIE) that have been added since 2017, to make contact with new organizations and negotiate future clinical exchange. - -Membership in an HIE is a more dynamic and transitory business relationship than the "parent-child" hierarchy represented by Organization.partOf. For these more flexible business relationships, the [OrganizationAffiliation](http://hl7.org/fhir/R4/organizationaffiliation.html) resource allows for organizations to relate to each other in non-hierarchical and more dynamic business relationships. Unlike partOf, the relationship is itself a resource, so it can be categorized with codes, status, etc. - -In the example below: -- Organization B has a parent Organization A. -- Organization B has been a part of its State/Province HIE since 2018 and is a member in good standing. - -The `organization` defines a role for the relationship, e.g., "HIE/HIO" or "member", and the `participatingOrganization` fills the role. - -
-{%include usecase5-diagram.svg%} -
-
- -**Figure 1:46.4.2.5.1-1: Organization.partOf vs. Affiliation** - -##### 1:46.4.2.5.2 Health Information Exchange (HIE) Membership Discovery Process Flow - -- A healthcare worker searches for organizations active in the State/Province HIE that have been added since 2017. -- The EMR searches for OrganizationAffiliations where the `organization` is the HIE, `active` is true, and `period.start` is 2017 or later. -- The EMR searches for details on the participating Organizations. -- The EMR presents the results to the healthcare worker. - -The interactions between the various actors in this use case are shown in Figure 1:46.4.2.5.2-1. - -
-{%include usecase5-processflow.svg%} -
-
- -**Figure 1:46.4.2.5.2-1: Health Information Exchange (HIE) Membership Discovery Workflow** - -#### 1:46.4.2.6 Use Case \#6: Health Information Exchange (HIE) Endpoint Discovery - -##### 1:46.4.2.6.1 Health Information Exchange (HIE) Endpoint Discovery Description - -Users in Health IT systems often need to be able to obtain clinical information electronically from outside systems, for example, in preparation for an encounter. This use case describes how a user in a system identifies the organizations a patient has received care from, as well as criteria for the kinds of clinical documents of interest, and then how their EMR queries the directory for a Health Information Exchange (HIE) to search for each organization and a compatible services endpoint the EMR can use. - -An HIE publishes a directory that contains all of its member organizations and their electronic endpoints. - -Note: Guidance for usage of endpoints in directories is provided [here](#1468-mcsd-endpoint-usage-considerations). - -- Endpoints are not limited to RESTful FHIR servers; they may point to systems that implement other mechanisms. This IG provides two profiles: - [a general endpoint](StructureDefinition-IHE.mCSD.Endpoint.html), and - [an endpoint to an IHE Document Sharing actor](StructureDefinition-IHE.mCSD.Endpoint.DocShare.html). -- Organizations might support one or many communication channels, each of which might have one or more distinct endpoints. For example, a FHIR communication channel might require only a single endpoint (i.e., a single [Service Base URL](https://www.hl7.org/fhir/http.html#general)), while an IHE XCA communication channel might require separate endpoints for each transaction. - -The diagram below shows an excerpt of the HIE directory, showing one participant in the HIE that implements IHE XCA with two Endpoints, and another that only uses one. - -
-{%include usecase6-diagram.svg%} -
-
- -**Figure 1:46.4.2.6.1-1: Health Information Exchange** - -##### 1:46.4.2.6.2 Health Information Exchange (HIE) Endpoint Discovery Process Flow - -- In preparation for a patient visit, a healthcare worker knows and identifies the organizations that have provided care for this patient, and identifies document types of interest. -- The EMR will query the HIE directory for the relevant organizations and their endpoints. -- For each organization obtained, the EMR will check for endpoints that support the needed XCA transactions, and make requests against these endpoints to obtain clinical documents. -- The EMR presents the obtained documents to the healthcare worker, who reviews them. - -The interactions between the various actors in this use case are shown in Figure 1:46.4.2.6.2-1. - -
-{%include usecase6-processflow.svg%} -
-
- -**Figure 1:46.4.2.6.2-1: Health Information Exchange (HIE) Endpoint Discovery Workflow** - -## 1:46.5 mCSD Security Considerations - -Actors are expected to follow the recommendations and requirements found in [ITI TF-2: Appendix Z.8 “Mobile Security Considerations”](https://profiles.ihe.net/ITI/TF/Volume2/ch-Z.html#z.8-mobile-security-considerations). - -The resources exchanged in this profile may contain information which pose a privacy risk, or in some cases, a safety risk, to providers and other personnel, as well as patients. For example, practitioner phone numbers and home addresses may be conveyed. Implementers should determine what data will be exposed by the system and what level of public access there will be if any. - -The Endpoint Resources exchanged in this profile will expose information about the particular APIs and web services running on the underlying host systems. This might attract malicious activity or provide hints to potential attackers on how to attack a particular host system. Implementers should consider this when determining the access policies for these Resources. System administrators for the underlying host systems must follow industry best practices for authentication, authorization, auditing, timely application of software patches, etc. - -There are many reasonable methods of security for interoperability transactions which can be implemented without modifying the characteristics of the transactions in the mCSD Profile. The use of TLS is encouraged, specifically the use of the ATNA Profile (see [ITI TF-1: 9](https://profiles.ihe.net/ITI/TF/Volume1/ch-9.html)). - -User authentication on mobile devices and browsers is typically handled by more lightweight authentication schemes such as HTTP Authentication, OAuth 2.0, or OpenID Connect. IHE has a set of profiles for user authentication including Internet User Authentication (IUA) for REST-based authentication. The network communication security and user authentication are layered in the HTTP transport layer. - -## 1:46.6 mCSD Cross Profile Considerations - -### 1:46.6.1 Aggregate Data Exchange – ADX - -The IHE QRPH Aggregate Data Exchange (ADX) Profile enables reporting of public health and service delivery indicators in various locations. A reporting system may play the role of a Care Services Update Consumer to ensure that it has an updated list of the resources for the reporting locations. - -Additionally, a service that contains information on practitioners (and may be a Care Services Selective Supplier or Care Services Update Supplier) can also be used to generate an ADX message to satisfy the use case of a district health manager running an aggregate report on staffing levels by facility and health worker type from the ITI Care Services Discovery (CSD) Profile. - -### 1:46.6.2 Care Services Discovery – CSD - -A Care Services Directory in the CSD Profile can be grouped with the Care Services Update Supplier from mCSD. The CSD Care Services InfoManager could implement the mCSD Care Services Update Consumer and the Care Services Selective Supplier Actors. The CSD Service Finder could implement the mCSD Care Services Selective Consumer. This enables the CSD actors to allow RESTful transactions without having to change the underlying data store. - -### 1:46.6.3 Health Provider Directory – HPD - -A Provider Information Source in HPD can also implement the Care Services Update Supplier from mCSD. Note that in this case the Provider Information Source would be queried for updates instead of pushing the updates to the Consumer. The HPD Provider Information Directory could implement the mCSD Care Services Update Consumer and the Care Services Selective Supplier Actors. The HPD Provider Information Consumer could implement the mCSD Care Services Selective Consumer. This enables the HPD actors to allow RESTful transactions without having to change the underlying data store. - -### 1:46.6.4 Mobile Alert Communication Management – mACM - -The mACM Profile defines the means to send an alert to practitioners. The mCSD Profile provides a way to query that list of practitioners. A mACM Alert Reporter can be grouped with a Care Services Update Consumer or a Care Services Selective Consumer to ensure that it has an updated list of practitioners. - -## 1:46.7 mCSD Deployment Considerations - -### 1:46.7.1 Simple Deployment - -A deployment may only have a single server that will maintain data. In this case, you would only need the Care Services Selective Supplier (or Care Services Update Supplier) to send search results back to one or more Care Services Selective Consumers (or Care Services Update Consumer). See Figure 1:46.7.1-1 below. - -
-{%include simple-deployment.svg%} -
-
- -**Figure 1:46.7.1-1: Simple Deployment** - -### 1:46.7.2 Federated and Cross-Jurisdictional Deployments - -A Federated Deployment has multiple levels of the Care Services Update Suppliers linked to Care Services Update Consumers. These Update Consumers may also support being Care Services Update Suppliers so that higher level Update Consumers can receive their updates. They may also support being a Care Services Selective Supplier so that Selective Consumer clients can query that level of information. See Figure 1:46.7.2-1 below. - -Interrelated content is maintained by the Care Services Update Consumer. The Care Services Update Consumer routinely obtains new or updated content from Care Services Update Suppliers by polling them. These updates may refresh a data cache which the Update Consumer maintains. The Update Consumer’s cache is refreshed at an appropriate interval specified by the implementing jurisdiction. The implementing jurisdiction will consider the implications of out of date information when setting the refresh interval between cache updates. The normal delays in updating listings will also be part of this consideration. - -The various data sources would maintain definitive data regarding one or more of: Organization, Location, Healthcare Service, or Practitioner and implement the Care Services Update Supplier. These Care Services Update Suppliers would respond to a Care Services Update Consumer’s request for new or updated content since a specified date and time. To support this capability, a Care Services Update Supplier should support time stamped updates. Data elements that are deprecated should not simply be deleted, but rather are updated to an appropriate status indicating their deprecation. - -This deployment may also have cross-jurisdictional considerations if any of the Update Suppliers have overlap in the data they manage. In this instance, the Care Services Update Consumer would need to resolve any conflicts before sharing this information as either a Care Services Update Supplier or a Care Services Selective Supplier. The way in which these conflicts are resolved is defined by the implementing jurisdiction of the Care Services Update Consumer. - -![Federated and Cross Jurisdictional Deployment](FederatedDeployment.png) -
- -**Figure 1:46.7.2-1: Federated and Cross Jurisdictional Deployment** - -The Care Services Selective Consumer is the actor that queries for information about interrelated care services. These queries are sent to the Care Services Selective Supplier who develops a response based on the content in its local data store. When a Care Services Selective Supplier is combined with a Care Services Update Consumer (Global and Country servers from Figure 1:46.7.2-1), it should maintain a cache of the aggregated information from all the configured Care Services Update Suppliers it is linked to. - -In order for the Care Services Update Consumer’s (Global and Country servers) cached content to be able to serve its role as an interlinked data source, the following conditions should be met by Care Services Update Suppliers who maintain content. - -1. Implementing jurisdictions may mandate terminologies for Organization Type, Service Type, Location Type, Location Status, Practitioner Type, Practitioner Status, Contact Point Type, Credential Type, Specialization Code, and language code. Care Services Update Suppliers would be configurable to use these terminologies, where mandated. In the case of a cross jurisdictional deployment, mapping between the terminology used by the various jurisdictions may need to be maintained. - -2. Implementing jurisdictions may mandate conventions regarding the types, components and formatting of Name, Address and Address Line elements. Care Services Update Suppliers would be configurable to use these formatting conventions, where mandated. - -3. Implementing jurisdictions may mandate the source of truth regarding Organization ID, Healthcare Service ID, Location ID and Practitioner ID. Care Services Update Suppliers would ensure that all cross-referenced IDs match corresponding resources in the jurisdictionally mandated sources of truth. - -For guidance on handling challenges regarding the representation of names across multiple languages and in different cultures, refer to the [ITI TF-2: 3.24.5.2.3.1](https://profiles.ihe.net/ITI/TF/Volume2/ITI-24.html#3.24.5.2.3.1). This section in the ITI Technical Framework describes the use of the language tag as documented in IETF RFC1766 and the HL7 XCN name data type. - -#### 1:46.7.2.1 Terminology Services - -All referenced terminologies from a Care Services Selective Supplier or Care Services Update Supplier may be pre-coordinated or they may be resolvable from one or more terminology services. Though it is out of scope of the mCSD Profile to define the means of interacting with a terminology service, this could be provided, for example, through the -[Sharing Valuesets, Codes, and Maps (SVCM) Profile](https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_SVCM.pdf). - -## 1:46.8 mCSD Endpoint Usage Considerations - -This section provides guidance for populating and using Endpoint resources in an mCSD directory to enable electronic communication, for example defining local points of connectivity within a community, or defining a Health Information Exchange (HIE) that allows multiple communities to interoperate. - -Many current Endpoint directories based on FHIR are purpose-built, which is to say they are deployed to a server that only hosts Organization and Endpoint resources, and only for the use case of Endpoint lookup. For this reason, directories often reflect network details directly in the Organization resource, such as: -- The organization's role in the network, like participant or sub-participant, expressed as the type of organization. -- The organization's relationship to its connectivity vendor, expressed as the organization hierarchy (i.e., partOf). -- The organization's connectivity state as an extension. -- Supported profiles, purposes of use, etc. as extensions. -- The organization's identity as a home community ID, for use in IHE Document Sharing profiles. - -When the organization's structure and its network capabilities need to vary independently (e.g., an organization uses two connectivity vendors), directories typically handle this by creating parallel instances of the Organization resource that then have to be merged by custom code to display. - -We anticipate these conflicts increasing over time due to many forces: -- Implementers taking advantage of profiles like mCSD to represent more comprehensive organizational and personnel structures. -- Implementers scaling by delegating maintenance of organization sub-trees to the organizations themselves. -- Directories consolidating/federating over time into more comprehensive "phonebooks", where a given organization participates in multiple HIEs. One example would be the USA ONC TEFCA Recognized Coordinating Entity, which will be maintaining a directory that consists of entries supplied by each Qualified Health Information Network (QHIN). - -In this guidance, we allow organization structure and network details to vary independently by moving network details out of the Organization and into the Endpoint and OrganizationAffiliation resources. - -##### 1:46.8.1 Endpoint to an Organization - -The simplest usage model for a client is when the organization it needs to contact has a dedicated Endpoint resource in Organization.endpoint. Because this Endpoint is Organization-specific, it does not matter to the client who hosts it. Some examples follow. - -Note: The managingOrganization of an Endpoint is who users need to contact for support. It may or may not be the same as the organization that hosts it. Since hosting is not reflected in the directory, we are indicating it in the diagrams below by the URLs. - -Organization A hosts its own Endpoint: -
-{%include dir-org-specific-endpoint-self.svg%} -
-
-**Figure 1:46.8.1-1: Organization-specific Endpoint Hosted by the Organization** - -Organization A is directly reachable by an endpoint hosted by its parent Organization B: -
-{%include dir-org-specific-endpoint-parent.svg%} -
-
-**Figure 1:46.8.1-2: Organization-specific Endpoint Hosted by Parent** - -Organization C is directly reachable by an endpoint hosted by its affiliated Organization D: -
-{%include dir-org-specific-endpoint-affil.svg%} -
-
-**Figure 1:46.8.1-3: Organization-specific Endpoint Hosted by Affiliation** - -Organization E is directly reachable by an endpoint hosted by a hidden (i.e., not in the directory) Intermediary F: -
-{%include dir-org-specific-endpoint-inter.svg%} -
-
-**Figure 1:46.8.1-4: Organization-specific Endpoint Hosted by Hidden Intermediary** - -##### 1:46.8.2 Endpoint to a Structure - -When an Organization with an Endpoint has a complex structure, for example, sub-organizations, clients can often make use of this structure: - -
-{%include dir-endpoint-to-org-hierarchy.svg%} -
-
- -**Figure 1:46.8.2-1: Endpoint to Organizational Hierarchy** - -Typical directories will take an organizational hierarchy to imply accessibility to parts of the structure, for example: -- For FHIR REST endpoints, the URL is simply the Service Base URL as specified in [FHIR R4 3.1.0.1.2](http://hl7.org/fhir/R4/http.html#general). Clients can expect to find resources related to Organizations A, B and C. -- For XCA endpoints, a client querying Organization A for documents (e.g., using \[ITI-38\]) may receive documents from Organizations A, B and C. If these organizations have identifiers of type Home Community ID in the directory, clients can expect to see these identifiers in the returned document metadata. -- For XDR endpoints, a client sending a Provide and Register Document Set-b (\[ITI-41\]) request to Organization A can optionally specify Organizations B and/or C in intendedRecipient. -- For MHD endpoints, a client sending a Provide Document Bundle (\[ITI-65\]) request to Organization A can optionally specify Organizations B and/or C in intendedRecipient. - -Specific details of addressing to federated recipients are out of the scope of this IG. - -Examples of this kind of federated structure are shown in [ITI TF-1: Appendix E.9](https://profiles.ihe.net/ITI/TF/Volume1/ch-E.html#E.9.3), for XCA Responding Gateways. - -By contrast, OrganizationAffiliations by themselves do not necessarily imply this kind of electronic accessibility. For this reason, this IG defines the code "DocShare-federate", which explicitly declares that the participatingOrganization is accessible as a federated organization via the OrganizationAffiliation.endpoint. - -The following diagram shows the same accessibility, but using OrganizationAffiliation. - -
-{%include dir-endpoint-to-org-affiliates.svg%} -
-
- -**Figure 1:46.8.2-2: Endpoint to Organizational Affiliates** - -In addition, these mechanisms may be combined. This may be useful, for example, when adding an existing organizational structure to an HIE. - -
-{%include dir-endpoint-to-hybrid-org-structure.svg%} -
-
- -**Figure 1:46.8.2-3: Endpoint to Hybrid Organizational Structure** - -##### 1:46.8.3 Grouping Actors - -Grouped actors may be represented as well, although not explicitly. In the following example, Participant A is reachable by either an MHD endpoint or XDR endpoints. The directory -does not reflect which endpoint is the adapter or the adaptee. - -
-{%include dir-endpoint-xdr-mhd.svg%} -
-
- -**Figure 1:46.8.3-1: Endpoints to Grouped Actors** - -##### 1:46.8.4 Endpoint Discovery Usage - -The following example shows the steps used by a Care Services Selective Consumer to navigate a directory to find suitable electronic service Endpoints to some desired Organizations. In this example, a "suitable" Endpoint means it supports an IHE Document Sharing profile, and is based on .connectionType, .extension:specificType, .payloadType, .payloadMimeType, and status (both Endpoint.status as well as the actual status of the electronic service). The example uses the [mCSD-profiled OrganizationAffiliation] StructureDefinition-IHE.mCSD.OrganizationAffiliation.DocShare.html) that indicates federated connectivity for Document Sharing (e.g., affiliated organizations may be addressed as intendedRecipient). The pseudocode below uses a depth-first, first-match search, and does not protect against loops. - -Until a suitable Endpoint is found or the search is complete, check the following in this order: -- Locate the desired Organization resource. -- Check if it has a suitable Organization.endpoint. -- Find OrganizationAffiliation resources where the Organization is the .participatingOrganization, and OrganizationAffiliation.code = DocShare-federate. -- For each OrganizationAffiliation found: - - Check if it has a suitable OrganizationAffiliation.endpoint. - - Check if it has a suitable OrganizationAffiliation.organization.endpoint. - - Continue searching for a suitable Endpoint by traversing the OrganizationAffiliation resources recursively (i.e., where the OrganizationAffiliation.organization of the current resource is the .participatingOrganization of the next resource). -- If there is an Organization.partOf (i.e., a parent), check if it has a suitable Organization.endpoint. - - Continue searching for a suitable Endpoint by traversing Organization.partOf recursively. - -Rather than a first-match search, the Care Services Selective Consumer might search for and decide among multiple electronic paths to the same Organization. For example: -- It finds a suitable Endpoint resource for the target Organization, but instead uses an Endpoint for an Organization two levels higher to make a broader search for records. -- It finds suitable Endpoint resources for equivalent mechanisms, XDR \[ITI-41\] and MHD \[ITI-65\], and chooses MHD as the preferred transaction. -- It finds suitable Endpoint resources to the same Organization via two different HIEs, and prefers one HIE based on lower fees and authorization differences. diff --git a/input/pagecontent/index.md b/input/pagecontent/index.md index 3b07055..87aa08e 100644 --- a/input/pagecontent/index.md +++ b/input/pagecontent/index.md @@ -1,135 +1,98 @@ -# EHMI Endpoint Register (EER) +# EER Endpoint Register (EER) -The EHMI Endpoint Register (EER) Profile supports discovery of Endpoint adresses related to a SOR Unit in Danish Healthcare using a RESTful interface. +The EER Endpoint Register (EER) Profile supports discovery of Endpoint adresses related to a SOR Organizational Unit in Danish Healthcare using a RESTful interface. -The profile is based upen IHE mCSD profile and the use cases and solutions using mCSD are outlined in the [mCSD White Paper](https://profiles.ihe.net/ITI/papers/mCSD/index.html). +This version of the profile supports registration of and querying for the following use cases: -This profile supports registration of and querying for: +**EHMI Core** +- Registration of communicating SOR organizational units +- Registration of endpoints correlating with a SOR organizational unit -## 1. Organization + **ehmiSMP** + - registration of eDelivery Access Points (AP) as Devices for a SOR organizational unit and its EHMI Endpoint + - registration of SMP metadata for the SMP lookup service for certain messages (documents) for a given EHMI Endpoint -Organizations are “umbrella” entities; these may be considered the administrative bodies under whose auspices care services are provided such as Healthcare Information Exchanges(HIEs), Integrated Delivery Networks (IDNs), Non-Government Organizations (NGOs), Faith-Based Organizations (FBOs) or even a one-physician family practice. An organization has a unique identifier and may have additional administrative attributes such as contact person, mailing address, etc. Departments of an institution, or other administrative units, may be represented as child Organizations of a parent Organization. - - **SOR IE Organization** – is reflected as a Jurisdiction instead of Organization (see [Jurisdiction](Jurisdiction)) - - **SOR SI Organization** – is reflected as a Facility instead of Organization (see [Facility](Facility)) - - **SOR OE Organization** – is reflected as a real Organization with [Location](Location)s and [Endpoint](Endpoint)s - -## 2. Facility - -Facilities are physical care delivery sites such as hospitals, clinics, health outposts, physician offices, labs, pharmacies, etc. A Facility has a unique identifier, geographic attributes (address, geocode), contact attributes, attributes regarding its hours of operation, etc. Each Facility is defined by a pairing of Location and Organization. - - **SOR SI Organization** – is reflected as a Facility instead of Organization (see [Facility](Facility)) - -## 3. Location - -Locations are physical places where care can be delivered such as facilities, buildings, wards, rooms, or vehicles. Locations also include jurisdictions such as a village districts or regions. A Location has a unique identifier and may have geographic attributes (address, geocode), attributes regarding its hours of operation, etc. Each Location may be related to one Organization. A location may have a hierarchical relationship with other locations. - -## 4. Jurisdiction - -Jurisdictions are political administrative units or other territories over which authority is exercised. A Jurisdiction has a unique identifier, geographic attributes, etc. Jurisdictions include political administrative units such as village districts or regions. Each Jurisdiction is defined by a pairing of Location and Organization. - - **SOR IE Organization** – is reflected as a Jurisdiction instead of Organization [See more...](Jurisdiction)) - -## 5. Practitioner - -A Practitioner is a health worker such as defined by WHO (in Chapter 1 of the [World Health Report 2006](http://whqlibdoc.who.int/publications/2006/9241563176_eng.pdf)); a Practitioner might be a physician, nurse, pharmacist, community health worker, district health manager, etc. Practitioners have contact and demographic attributes. Each Practitioner may be related to one or more Organizations, one or more Locations and one or more Healthcare Services. Specific attributes may be associated with the Practitioner relationship with these other entities. - -## 6. Healthcare Service - -Each healthcare service has a unique identifier. Examples include surgical services, antenatal care services, or primary care services. The combination of a Healthcare Service offered at a Location may have specific attributes including contact person, hours of operation, etc. [See more...](Healthcare-Service) - -## 7. Endpoint - -An Organization may be reachable for electronic data exchange through electronic Endpoint(s). An Endpoint may be a FHIR server, an IHE web services actor, or some other mechanism. If an Organization does not have an Endpoint, it may still be reachable via an Endpoint at its parent Organization or an affiliated Organization. [See more...](Endpoint) - -## 8. OrganizationAffiliation -An Organization may have relationships with other organizations that are not hierarchical. These relationships may indicate an electronic routing path to other organizations that cannot be reached directly. OrganizationAffiliation can be used to specify relationships such as supply chains or administrative reporting structures. +**EHMI Addressing Service** +- getReceiverDataBySORID -The capabilities detailed in this profile support consumer-centric queries such as finding “where is the closest youth mental health services clinic” or “what are the hours of a physiotherapist near my workplace”. In addition, EHMI CSD supports crucial health system management workflows. This can include reporting and analyses, such as “what are my health human resource capacities, by facility, by cadre,” “what are all the services offered at this facility,” or conversely, “where are all the facilities that offer this service.” The EHMI CSD Profile may be employed to support, for example, the Provider Queries listed by the US Office of the National Coordinator as part of the [Standards and -Interoperability Framework](https://www.healthit.gov/topic/interoperability/standards-interoperability-si-framework). In addition, EHMI CSD can enable connectivity by providing service endpoint lookup, such as "What is the FHIR server for this organization?". +**EHMI Delivery Status** +- registration of reporting Devices for a "station" in the messageflow. +- getting data for reporting Devices in the messageflow. -The loosely coupled design and flexible querying capability of the EHMI CSD Profile means it can be deployed within a variety of eHealth architectures and support a wide array of care workflows. -## 1:46.4.1 Concepts +## Relationship with and scoping to IHE MCSD -The EHMI Endpoint Register (EER) Profile supports queries for resources related to care services discovery. The relationship between these entities is illustrated in Figure 1:46.4.1-1. +The profile is based upon and inspired by the IHE mCSD profile and the use cases and solutions using mCSD are outlined in the [mCSD White Paper](https://profiles.ihe.net/ITI/papers/mCSD/index.html). -![Top-level Relationships between Care Services Entities](mCSDRelationships.png) -
+Currently supported profiles of the IE MSCD profiles stated in [1:46 Mobile Care Services Discovery (mCSD)](https://profiles.ihe.net/ITI/mCSD/volume-1.html#1-46-mobile-care-services-discovery-mcsd) are: -**Figure 1:46.4.1-1: Top-level Relationships between Care Services Entities** +**1. Organization** -# Core Profiles - -[EHMI SOR Organization](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/StructureDefinition-EHMI.SOR.Organization.html) - -EHMI SOR General Organization - -[EHMI SOR Institution Owner Organization](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/StructureDefinition-EHMI.SOR.InstitutionOwner.Organization.html) - -EHMI SOR Institution Owner Organization IO (DK:IE) - -[EHMI SOR Healthcare Institution Organization](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/StructureDefinition-EHMI.SOR.HealthcareInstitution.Organization.html) - -EHMI SOR Healthcare Institution Organization HI (DK:SI) - -[EHMI SOR Organizational Unit](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/StructureDefinition-EHMI.SOR.OrganizationalUnit.Organization.html) - -EHMI SOR Organizational Unit OU (DK:OE) - -[SOR HealthcareService](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/StructureDefinition-medcom.sor.HealthcareService.html) - -A profile on the HealthcareService resource for SOR. - -[EerMessageDefinition](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/StructureDefinition-EerMessageDefinition.html) - -A profile on the MessageDefinition resource for EHMI SOR. (Attempting to replace entries in the standardcatalogues from both MedCom and SDS) - - -## Extended Profiles - -### SOR IO (DK: IE) - -[EHMI SOR Institution Owner Municipality Organization](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/StructureDefinition-EHMI.SOR.InstitutionOwner.Municipality.Organization.html) +Organizations are “umbrella” entities; these may be considered the administrative bodies under whose auspices care services are provided such as Healthcare Information Exchanges(HIEs), Integrated Delivery Networks (IDNs), Non-Government Organizations (NGOs), Faith-Based Organizations (FBOs) or even a one-physician family practice. An organization has a unique identifier and may have additional administrative attributes such as contact person, mailing address, etc. Departments of an institution, or other administrative units, may be represented as child Organizations of a parent Organization. -EHMI SOR Institution Owner Municipality Organization IO (DK:IE), a specialization of "EHMI SOR Institution Owner Organization IO (DK:IE)" focused on the municipality's profile. +**7. Endpoint** -[EHMI SOR Institution Owner Regional Organization](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/StructureDefinition-EHMI.SOR.InstitutionOwner.Regional.Organization.html) +An Organization may be reachable for electronic data exchange through electronic Endpoint(s). An Endpoint may be a FHIR server, an IHE web services actor, or some other mechanism. If an Organization does not have an Endpoint, it may still be reachable via an Endpoint at its parent Organization or an affiliated Organization. -EHMI SOR Institution Owner Regional Organization IO (DK:IE), a specialization of "EHMI SOR Institution Owner Organization IO (DK:IE)" focused on the region's profile. +**Other MCSD Profiles** -### SOR HI (DK: SI) +Other profiles like the following will be considered supported in the coming versions of EER. -[EHMI SOR Healthcare Institution Hospital Organization](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/StructureDefinition-EHMI.SOR.HealthcareInstitution.Hospital.Organization.html) + 2. Facility + 3. Location + 4. Jurisdiction + 5. Practitioner + 6. Healthcare Service + 8. OrganizationAffiliation -EHMI SOR Healthcare Institution Hospital Organization HI (DK:SI), a specialization of "EHMI SOR Healthcare Institution Organization HI (DK:SI)" focused on the hospital's profile. +## EER actors and transactions -### SOR OU (DK: OE) +EER will support the following MCSD actors and their transactions in this version: -[EHMI SOR Organizational Unit Hospital Organization](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/StructureDefinition-EHMI.SOR.HospitalOUOrganization.Organization.html) +Table 1: EER Profile - Actors and Transactions -EHMI SOR Organizational Unit Hospital Organization OU (DK:OE), a specialization of "EHMI SOR Organizational Unit OU (DK:OE)" focused on the hospital's department profile. +| Actors | Transactions | Initiator or Responder | Optionality | Reference | +| ------ | ------------ | ---------------------- | ----------- | --------- | +| Care Services Selective Consumer | Find Matching Care Services [ITI-90] | Initiator | R | ITI TF-2: 3.90 +| Care Services Selective Supplier | Find Matching Care Services [ITI-90] | Responder | R | ITI TF-2: 3.90 +| Care Services Update Consumer Request | Care Services Updates [ITI-91] | Initiator | R | ITI TF-2: 3.91 +| Care Services Update Supplier Request | Care Services Updates [ITI-91] | Responder | R | ITI TF-2: 3.91 +While Consumer Actors (clients) will implement the Initiator transactions, EER as a Supplier Actor will implement the Responder transactions. -## Instances +## EER enhancements of MCSD -### SOR IO (DK: IE) +While MCSD is a great framework for an organizational directory of healthcare providers, it lacks a few things to be able to replace part of the Danish SOR Directory. -[EHMI.SOR.IO-AAR-Kommune as a SOR IO Organization](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/branches/main/Organization-EHMI.SOR.IO-AAR-Kommune.311000016009.html) +SOR includes: -An instance of the "EHMI SOR Institution Owner Municipality Organization IO (DK:IE)" profile +- software solutions (in FHIR: Devices) for the organizational units both as the direct end-user application (EUA) and the network access points (AP) serving a particular organizational unit +- messages supported by the Endpoints -### SOR HI (DK: SI) +EER enheances MCSD with what SOR includes and adds furthermore: -[AAR SOR HI Organization - Sundhed og Omsorg](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/branches/main/Organization-EHMI.SOR.HI-AAR-Kommune.937961000016000.html) +- Devices and their corresponding DeviceDefinitions + - eerDevice and its derivations: + - End User Applications (eerDeviceEUA) + - Network Access Point devices (eerDeviceAP) + - Message Service Handlers (eerDeviceMSH) (might be software solutions standing alone or built ino EUAs or APs) +- Messages defined as MessageDefinitions -An instance of the "EHMI SOR Healthcare Institution Organization HI (DK:SI)" profile +Message Service Handlers (eerDeviceMSH) are software solutions standing alone or built ino EUAs or APs. When stand-alone solutions, it is helpful to see them acting in the diagrams. Below the two diagrams show EER with and without MSHs. -### SOR OU (DK: OE) +
+ EER Diagram without MSH +
EER Diagram without MSH
+
+
-[EHMI.SOR.OU-AAR-Kommune.937971000016005](https://build.fhir.org/ig/medcomdk/dk-ehmi-mCSD/branches/main/Organization-EHMI.SOR.OU-AAR-Kommune.937971000016005.html) + + -An instance of the "EHMI SOR Organizational Unit OU (DK:OE)" profile +
+ EER Diagram including MSH +
EER Diagram including MSH
+
+
diff --git a/input/pagecontent/mCSDRelationships.png b/input/pagecontent/mCSDRelationships.png deleted file mode 100644 index a38bd60..0000000 Binary files a/input/pagecontent/mCSDRelationships.png and /dev/null differ diff --git a/sushi-config.yaml b/sushi-config.yaml index 440a657..514b5f2 100644 --- a/sushi-config.yaml +++ b/sushi-config.yaml @@ -5,11 +5,11 @@ # ╰────────────────────────────────────────────────────────────────────────────────────────────────╯ id: dk.ehmi.eer canonical: http://medcomehmi.dk/ig/dk-ehmi-eer -name: EHMI Endpoint Register (EER) IG -title: "DK EHMI Endpoint Register (EER)" -description: The EHMI Endpoint Register (EER) IG +name: EER Endpoint Register (EER) IG +title: "DK EER Endpoint Register (EER)" +description: The EER Endpoint Register (EER) IG status: draft # draft | active | retired | unknown -version: 0.3.0 +version: 0.8.0 fhirVersion: 4.0.1 # https://www.hl7.org/fhir/valueset-FHIR-version.html copyrightYear: 2024+ releaseLabel: ci-build # ci-build | draft | qa-preview | ballot | trial-use | release | update | normative+trial-use @@ -27,12 +27,16 @@ jurisdiction: urn:iso:std:iso:3166#DK "Denmark" dependencies: ihe.iti.mcsd: 3.8.0 hl7.fhir.dk.core: 2.0.0 - # dk.medcom.ehmi.eds: current +# dk.medcom.ehmi.eds: current dk.ehmi.terminology: current # dk.ehmi.core: current - medcom.fhir.dk.core: 2.3.0 - medcom.fhir.dk.messaging: 2.0.0 - medcom.fhir.dk.terminology: 1.6.0 + # medcom.fhir.dk.core: 2.4.0 + # medcom.fhir.dk.messaging: 2.2.0 + # medcom.fhir.dk.terminology: 1.7.0 + medcom.fhir.dk.core: current + medcom.fhir.dk.messaging: current + medcom.fhir.dk.terminology: current + # medcom.fhir.dk.acknowledgement: dev ## # The pages property corresponds to IG.definition.page. SUSHI can # auto-generate the page list, but if the author includes pages in @@ -78,15 +82,18 @@ dependencies: # ╰────────────────────────────────────────────────────────────────────────────────────────────────╯ menu: Home: index.html - Table of Contents: toc.html + EER and SOR: SOR-EER-mapping.html +## Table of Contents: toc.html Profiles: profiles.html Extensions: extensions.html Artifacts: artifacts.html Downloads: downloads.html Terminology: terminology.html + Use-cases: + EER-EAS Use case 1: eas-Use-case-1.html User-stories: - EHMI User Stories: EHMI-User-Stories.html - mCSD User-stories: EHMI-CSD-User-Stories.html + EHMI User Stories: EHMI-User-Stories.html +# mCSD User-stories: EHMI-CSD-User-Stories.html # ╭───────────────────────────Less Common Implementation Guide Properties──────────────────────────╮ # │ Uncomment the properties below to configure additional properties on the ImplementationGuide │ # │ resource. These properties are less commonly needed than those above. │ @@ -220,3 +227,4 @@ menu: # if InstanceOf references a profile: # # setId: always # always | standalone-only +