Profile Comparison between http://fhir.ch/ig/ch-etoc/StructureDefinition/ch-etoc-servicerequest vs http://fhir.ch/ig/ch-etoc/StructureDefinition/ch-etoc-servicerequest

Left:CH eToc Service Request (http://fhir.ch/ig/ch-etoc/StructureDefinition/ch-etoc-servicerequest)
Right:CH eTOC Service Request (http://fhir.ch/ig/ch-etoc/StructureDefinition/ch-etoc-servicerequest)

Messages

ErrorStructureDefinition.versionValues for version differ: '1.0.0' vs '2.0.0-ballot'
InformationStructureDefinition.titleValues for title differ: 'CH eToc Service Request' vs 'CH eTOC Service Request'
InformationStructureDefinition.dateValues for date differ: '2022-04-13T09:54:48+02:00' vs '2023-06-29T23:41:13+02:00'
InformationStructureDefinition.copyrightValues for copyright differ: 'CC-BY-SA-4.0' vs 'CC0-1.0'
WarningServiceRequestElements differ in definition: 'This IG adheres to the FHIR International Patient Summary (IPS) Implementation Guide. Clinical content uses mostly the same resources as th IPS; some minor differences are explained in comments to the resources affected. The resouce definitions are however constrained from FHIR base definitions and Swiss Core definitions and NOT from UVIPS. This decision was made in order to minimize unexpected impact of future changes in IPS and for compatibility with Swiss Core. eToc adds a ServiceReequest resource to the clinical content (according to the IPS) in order to depict the reason for a referral, the requested service and some additional information (e.g. coverage, room preferance etc.). Resources for such purpose are referenced by the ServiceRequest resource. Header information such as sender, receiver etc. are condsidered as Generic Elements (to all sorts of referral, orders etc.) and follow the definition in the ORF Implementation Guide. This IG follows the Swiss eHealth Exchange Format Handbook Part I: Service Requests V 0.13. The Questionnaire resource gives gudiance for the implementaion of the user interface.' vs 'This IG adheres to the FHIR International Patient Summary (IPS) Implementation Guide. Clinical content uses mostly the same resources as the IPS; some minor differences are explained in comments to the resources affected. The resource definitions are however constrained from FHIR base definitions and Swiss Core definitions and NOT from UVIPS. This decision was made in order to minimize unexpected impact of future changes in IPS and for compatibility with Swiss Core. eTOC adds a ServiceRequest resource to the clinical content (according to the IPS) in order to depict the reason for a referral, the requested service and some additional information (e.g. coverage, room preferance etc.). Resources for such purpose are referenced by the ServiceRequest resource. Header information such as sender, receiver etc. are condsidered as Generic Elements (to all sorts of referral, orders etc.) and follow the definition in the ORF Implementation Guide. This IG follows the Swiss eHealth Exchange Format Handbook Part I: Service Requests V 0.13. The Questionnaire resource gives gudiance for the implementaion of the user interface.'
WarningServiceRequest.codeElements differ in short: 'Ziel' vs 'What is being requested/ordered'
WarningServiceRequest.codeElements differ in binding.description: 'Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available [here].' vs 'Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is preferred.'
WarningServiceRequest.reasonCodeElements differ in short: 'Begründung' vs 'Explanation/Justification for procedure or service'
WarningServiceRequest.reasonReferenceElements differ in short: 'Reason for the referral (primary diagnosis)' vs 'Explanation/Justification for service or service (primary diagnosis)'

Metadata

NameValueComments
.abstractfalse
    .baseDefinitionhttp://fhir.ch/ig/ch-orf/StructureDefinition/ch-orf-servicerequest
      .copyrightCC-BY-SA-4.0CC0-1.0
      • Values Differ
      .date2022-04-13T09:54:48+02:002023-06-29T23:41:13+02:00
      • Values Differ
      .descriptionDefinition for the ServiceRequest resource in the context of electronic transition of care.
        .experimental
          .fhirVersion4.0.1
            .jurisdiction
              ..jurisdiction[0]urn:iso:std:iso:3166#CH
                .kindresource
                  .nameChEtocServiceRequest
                    .publisherHL7 Switzerland
                      .purpose
                        .statusactive
                          .titleCH eToc Service RequestCH eTOC Service Request
                          • Values Differ
                          .typeServiceRequest
                            .urlhttp://fhir.ch/ig/ch-etoc/StructureDefinition/ch-etoc-servicerequest
                              .version1.0.02.0.0-ballot
                              • Values Differ

                              Structure

                              NameL FlagsL Card.L TypeL Description & ConstraintsR FlagsR Card.L TypeL Description & ConstraintsCommentsdoco
                              .. ServiceRequest C0..*ChOrfServiceRequestCH eToc Service Request
                              C0..*ChOrfServiceRequestCH eTOC Service Request
                              • Elements differ in definition: 'This IG adheres to the FHIR International Patient Summary (IPS) Implementation Guide. Clinical content uses mostly the same resources as th IPS; some minor differences are explained in comments to the resources affected. The resouce definitions are however constrained from FHIR base definitions and Swiss Core definitions and NOT from UVIPS. This decision was made in order to minimize unexpected impact of future changes in IPS and for compatibility with Swiss Core. eToc adds a ServiceReequest resource to the clinical content (according to the IPS) in order to depict the reason for a referral, the requested service and some additional information (e.g. coverage, room preferance etc.). Resources for such purpose are referenced by the ServiceRequest resource. Header information such as sender, receiver etc. are condsidered as Generic Elements (to all sorts of referral, orders etc.) and follow the definition in the ORF Implementation Guide. This IG follows the Swiss eHealth Exchange Format Handbook Part I: Service Requests V 0.13. The Questionnaire resource gives gudiance for the implementaion of the user interface.' vs 'This IG adheres to the FHIR International Patient Summary (IPS) Implementation Guide. Clinical content uses mostly the same resources as the IPS; some minor differences are explained in comments to the resources affected. The resource definitions are however constrained from FHIR base definitions and Swiss Core definitions and NOT from UVIPS. This decision was made in order to minimize unexpected impact of future changes in IPS and for compatibility with Swiss Core. eTOC adds a ServiceRequest resource to the clinical content (according to the IPS) in order to depict the reason for a referral, the requested service and some additional information (e.g. coverage, room preferance etc.). Resources for such purpose are referenced by the ServiceRequest resource. Header information such as sender, receiver etc. are condsidered as Generic Elements (to all sorts of referral, orders etc.) and follow the definition in the ORF Implementation Guide. This IG follows the Swiss eHealth Exchange Format Handbook Part I: Service Requests V 0.13. The Questionnaire resource gives gudiance for the implementaion of the user interface.'
                              ... id Σ0..1stringLogical id of this artifactΣ0..1idLogical id of this artifact
                                ... meta Σ0..1MetaMetadata about the resourceΣ0..1MetaMetadata about the resource
                                  ... implicitRules ?!Σ0..1uriA set of rules under which this content was created?!Σ0..1uriA set of rules under which this content was created
                                    ... language 0..1codeLanguage of the resource content
                                    Binding: ?? (preferred): A human language.

                                    Additional BindingsPurpose
                                    ??Max Binding
                                    0..1codeLanguage of the resource content
                                    Binding: ?? (preferred): A human language.

                                    Additional BindingsPurpose
                                    ??Max Binding
                                      ... text 0..1NarrativeText summary of the resource, for human interpretation0..1NarrativeText summary of the resource, for human interpretation
                                        ... contained 0..*ResourceContained, inline Resources
                                        0..*ResourceContained, inline Resources
                                          ... Slices for extension 0..*ExtensionExtension
                                          Slice: Unordered, Open by value:url
                                          0..*ExtensionExtension
                                          Slice: Unordered, Open by value:url
                                            ... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
                                            ?!0..*ExtensionExtensions that cannot be ignored
                                              ... Slices for identifier SΣ1..*IdentifierIdentifiers assigned to this order
                                              Slice: Unordered, Open by pattern:$this
                                              SΣ1..*IdentifierIdentifiers assigned to this order
                                              Slice: Unordered, Open by pattern:$this
                                                ... instantiatesCanonical Σ0..*canonical(ActivityDefinition | PlanDefinition)Instantiates FHIR protocol or definition
                                                Σ0..*canonical(ActivityDefinition | PlanDefinition)Instantiates FHIR protocol or definition
                                                  ... instantiatesUri Σ0..*uriInstantiates external protocol or definition
                                                  Σ0..*uriInstantiates external protocol or definition
                                                    ... basedOn Σ0..*Reference(CarePlan | ServiceRequest | MedicationRequest)What request fulfills
                                                    Σ0..*Reference(CarePlan | ServiceRequest | MedicationRequest)What request fulfills
                                                      ... replaces Σ0..*Reference(ServiceRequest)What request replaces
                                                      Σ0..*Reference(ServiceRequest)What request replaces
                                                        ... requisition Σ0..1IdentifierComposite Request IDΣ0..1IdentifierComposite Request ID
                                                          ... status ?!SΣ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
                                                          Binding: ?? (required): The status of a service order.

                                                          ?!SΣ1..1codedraft | active | on-hold | revoked | completed | entered-in-error | unknown
                                                          Binding: ?? (required): The status of a service order.

                                                            ... intent ?!SΣ1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
                                                            Binding: ?? (required): The kind of service request.

                                                            ?!SΣ1..1codeproposal | plan | directive | order | original-order | reflex-order | filler-order | instance-order | option
                                                            Binding: ?? (required): The kind of service request.

                                                              ... category Σ0..*CodeableConceptClassification of service
                                                              Binding: ?? (example): Classification of the requested service.


                                                              Σ0..*CodeableConceptClassification of service
                                                              Binding: ?? (example): Classification of the requested service.


                                                                ... priority SΣ0..1codeOrder priority
                                                                Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.

                                                                SΣ0..1codeOrder priority
                                                                Binding: ?? (required): Identifies the level of importance to be assigned to actioning the request.

                                                                  ... doNotPerform ?!Σ0..1booleanTrue if service/procedure should not be performed?!Σ0..1booleanTrue if service/procedure should not be performed
                                                                    ... code SΣ0..1CodeableConceptZiel
                                                                    Binding: ?? (example): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is preferred and a valueset using LOINC Order codes is available here.

                                                                    SΣ0..1CodeableConceptWhat is being requested/ordered
                                                                    Binding: ?? (example): Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is preferred.

                                                                    • Elements differ in short: 'Ziel' vs 'What is being requested/ordered'
                                                                    • Elements differ in binding.description: 'Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is (preferred)[http://build.fhir.org/terminologies.html#preferred] and a valueset using LOINC Order codes is available [here].' vs 'Codes for tests or services that can be carried out by a designated individual, organization or healthcare service. For laboratory, LOINC is preferred.'
                                                                    .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                      .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                      Slice: Unordered, Open by value:url
                                                                      0..*ExtensionAdditional content defined by implementations
                                                                      Slice: Unordered, Open by value:url
                                                                        .... coding Σ0..*CodingCode defined by a terminology system
                                                                        Σ0..*CodingCode defined by a terminology system
                                                                          .... text SΣ0..1stringPlain text representation of the conceptSΣ0..1stringPlain text representation of the concept
                                                                            ... orderDetail ΣC0..*CodeableConceptAdditional order information
                                                                            Binding: ?? (example): Codified order entry details which are based on order context.


                                                                            ΣC0..*CodeableConceptAdditional order information
                                                                            Binding: ?? (example): Codified order entry details which are based on order context.


                                                                              ... quantity[x] Σ0..1Quantity, Ratio, RangeService amountΣ0..1Quantity, Ratio, RangeService amount
                                                                                ... subject SΣ1..1Reference(CH Core Patient Profile)PatientSΣ1..1Reference(CH Core Patient)Patient
                                                                                  ... encounter Σ0..1Reference(Encounter)Encounter in which the request was createdΣ0..1Reference(Encounter)Encounter in which the request was created
                                                                                    ... occurrence[x] Σ0..1dateTime, Period, TimingWhen service should occurΣ0..1dateTime, Period, TimingWhen service should occur
                                                                                      ... asNeeded[x] Σ0..1boolean, CodeableConceptPreconditions for service
                                                                                      Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.

                                                                                      Σ0..1boolean, CodeableConceptPreconditions for service
                                                                                      Binding: ?? (example): A coded concept identifying the pre-condition that should hold prior to performing a procedure. For example "pain", "on flare-up", etc.

                                                                                        ... authoredOn Σ0..1dateTimeDate request signedΣ0..1dateTimeDate request signed
                                                                                          ... requester SΣ0..1Reference(CH Core Practitioner Role Profile)The person/organization responsible for the form contentSΣ0..1Reference(CH Core PractitionerRole)The person/organization responsible for the form content
                                                                                            ... performerType Σ0..1CodeableConceptPerformer role
                                                                                            Binding: ?? (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

                                                                                            Σ0..1CodeableConceptPerformer role
                                                                                            Binding: ?? (example): Indicates specific responsibility of an individual within the care team, such as "Primary physician", "Team coordinator", "Caregiver", etc.

                                                                                              ... performer Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson)Requested performer
                                                                                              Σ0..*Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson)Requested performer
                                                                                                ... locationCode Σ0..*CodeableConceptRequested location
                                                                                                Binding: ?? (example): A location type where services are delivered.


                                                                                                Σ0..*CodeableConceptRequested location
                                                                                                Binding: ?? (example): A location type where services are delivered.


                                                                                                  ... locationReference Σ0..*Reference(Location)Requested location
                                                                                                  Σ0..*Reference(Location)Requested location
                                                                                                    ... reasonCode SΣ0..*CodeableConceptBegründung
                                                                                                    Binding: ?? (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.


                                                                                                    SΣ0..*CodeableConceptExplanation/Justification for procedure or service
                                                                                                    Binding: ?? (example): Diagnosis or problem codes justifying the reason for requesting the service investigation.


                                                                                                    • Elements differ in short: 'Begründung' vs 'Explanation/Justification for procedure or service'
                                                                                                    .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                      .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                                      Slice: Unordered, Open by value:url
                                                                                                      0..*ExtensionAdditional content defined by implementations
                                                                                                      Slice: Unordered, Open by value:url
                                                                                                        .... coding Σ0..*CodingCode defined by a terminology system
                                                                                                        Σ0..*CodingCode defined by a terminology system
                                                                                                          .... text SΣ0..1stringPlain text representation of the conceptSΣ0..1stringPlain text representation of the concept
                                                                                                            ... reasonReference SΣ0..*Reference(CH eToc Primary Diagnosis Condition)Reason for the referral (primary diagnosis)
                                                                                                            SΣ0..*Reference(CH eTOC Primary Diagnosis Condition)Explanation/Justification for service or service (primary diagnosis)
                                                                                                            • Elements differ in short: 'Reason for the referral (primary diagnosis)' vs 'Explanation/Justification for service or service (primary diagnosis)'
                                                                                                            ... insurance S0..*Reference(CH ORF Coverage)Associated insurance coverage
                                                                                                            S0..*Reference(CH ORF Coverage)Associated insurance coverage
                                                                                                              ... Slices for supportingInfo S0..*Reference(Resource)Additional clinical information
                                                                                                              Slice: Unordered, Open by profile:resolve()
                                                                                                              S0..*Reference(Resource)Additional clinical information
                                                                                                              Slice: Unordered, Open by profile:resolve()
                                                                                                                ... specimen Σ0..*Reference(Specimen)Procedure Samples
                                                                                                                Σ0..*Reference(Specimen)Procedure Samples
                                                                                                                  ... bodySite Σ0..*CodeableConceptLocation on Body
                                                                                                                  Binding: ?? (example): Codes describing anatomical locations. May include laterality.


                                                                                                                  Σ0..*CodeableConceptLocation on Body
                                                                                                                  Binding: ?? (example): Codes describing anatomical locations. May include laterality.


                                                                                                                    ... note S0..*AnnotationComments
                                                                                                                    S0..*AnnotationComments
                                                                                                                      .... id 0..1stringUnique id for inter-element referencing0..1stringUnique id for inter-element referencing
                                                                                                                        .... Slices for extension 0..*ExtensionAdditional content defined by implementations
                                                                                                                        Slice: Unordered, Open by value:url
                                                                                                                        0..*ExtensionAdditional content defined by implementations
                                                                                                                        Slice: Unordered, Open by value:url
                                                                                                                          .... author[x] Σ0..1Reference(Practitioner | Patient | RelatedPerson | Organization), stringIndividual responsible for the annotationΣ0..1Reference(Practitioner | Patient | RelatedPerson | Organization), stringIndividual responsible for the annotation
                                                                                                                            .... time Σ0..1dateTimeWhen the annotation was madeΣ0..1dateTimeWhen the annotation was made
                                                                                                                              .... text SΣ1..1markdownThe annotation - text content (as markdown)SΣ1..1markdownThe annotation - text content (as markdown)
                                                                                                                                ... patientInstruction Σ0..1stringUse Appointment.patientInstruction (referenced via ServiceRequest.extension) for patient-oriented instructionsΣ0..1stringUse Appointment.patientInstruction (referenced via ServiceRequest.extension) for patient-oriented instructions
                                                                                                                                  ... relevantHistory 0..*Reference(Provenance)Request provenance
                                                                                                                                  0..*Reference(Provenance)Request provenance

                                                                                                                                    doco Documentation for this format