Loading...
Help
Login
Busy
Search
CH-PHARM - Project Information
 
Warning
Select building block repository
Select user
Select user
Version: Edit
Add/change logo
Remove File
Compare: Releases


Edit
Edit publication parameters

Warning
Edit
Edit
Previous release
 
Name
CH-PHARM
Description
CH-PHARM is the Building Block Repository for CDA-CH-EMED which defines the document exchange formats.

CH-PHARM consists of two parts:
  • Model of the IHE Pharmacy Technical Framework 2017 (PHARM; i.e. PRE, PADV, DIS, PML, MTP content profiles, IHE Pharmacy Content Profiles).
  • Swiss specializations of the IHE Pharmacy templates which can be used in other Swiss exchange formats and are used in CDA-CH-EMED

PropertiesPrefix: ch-pharm-Default language: English (en-US)Contains reusable content?The contents of this 'project' are considered suitable for re-use by other projects when this setting is active.Is private?The project is not listed in the menus and ignored in searches when this setting is active. This useful for projects in incubation fase. You may still work in the project based on direct URLsExperimental/Test?Project is experimental or meant to test things rather than aimed at production useNotifier: Determines the project global issue notifier setting (on/off - default is 'on'). Note: changes to this setting are immediately saved.
Publication location
http://ehealthsuisse.art-decor.org/
Project overviewProject Index
Project Id2.16.756.5.30.1.127.77.4
Project Last modified2021-04-14 12:18:43
Repository reference
PrefixURLFormat
ad1bbr-http://art-decor.org/decor/services/DECOR
ad2bbr-http://art-decor.org/decor/services/DECOR
ch-pcc-http://art-decor.org/decor/services/DECOR
ch-epr-http://art-decor.org/decor/services/DECOR
hl7chcda-http://art-decor.org/decor/services/DECOR
RESTful Service
Contributors/Copyright
ContributorTypeLogoCopyright years
eHealth Suisse
Schwarzenburgstrasse 165
CH-3003 Bern
Author2016-2017
Authors
NameEmailSubscribe to all issuesEvery author is notified by default for events on issues where he is the author or from the moment he is assigned to an issue. If you would like to keep track of all issue updates, set this to 'on'
AdministratorNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Oliver EggerNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Tony SchallerNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Dr. Kai HeitmannNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Johannes GnaegiNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Michaela ZieglerNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Quentin LigierNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Pero GrgicNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Annatina FoppaNot visibleThis info is only visible to this author and any decor-admin authorNot visibleThis info is only visible to this author and any decor-admin author
Versions / Releases
Warning



ReadyBusyError
DateByDescriptionStatusPublication
2021-02-22 19:52:43Annatina FoppaRelease: 0.97 (22.02.2021)
Release in preparation of eMedication test event, taking place in March 2021.

There have been changes to the following 22 issues since the last intermediate version or release.
  • Issue 2 "Wrong annotation of the substitution permission entryRelationship" with status "Closed". Last event (2020-05-14T10:01:16):
    1.3.6.1.4.1.19376.1.9.1.3.2 Containment draft IHE Prescription Item Entry Content Module (2020)
    1.3.6.1.4.1.19376.1.9.1.3.7 Containment draft IHE Medication Treatment Plan Item Entry Content Module (2020)
    2.16.756.5.30.1.1.10.4.34 Containment draft Medication Treatment Plan Item Entry Content Module (2020)

    2.16.756.5.30.1.1.10.4.43 Containment draft Prescription Item Entry Content Module (2020)

    fixed templates for schematron generation
  • Issue 3 "rateQuantity and doseQuantity should be constrained" with status "Open". Last event (2020-08-04T20:14:53):
    Finding:

    In IHE PCC TF2 (revision 11.0), p.187, the dose (doseQuantity) and rate (rateQuantity) are defined by their low and high bounds that are different if a range is given, or equal otherwise (<doseQuantity><low value='' unit=''/><high value='' unit=''/></doseQuantity). 
    In IHE PHARM PRE (revision 1.9), pp.47-48, they are only defined by their value and unit (<doseQuantity value='' unit=''/>).
    In IHE PCC CDA (revision 2.6), p.141 and p.144, low+high is given in the definition and @value + @unit is shown in the example.

    The two standards disagree on the correct structure, Stéphane is investigating why PHARM is not following PCC here.

    In any case, the rateQuantity and doseQuantity IVL_PQ structure should be restrained to either @value + @unit or low + high. The examples that show a doseQuantity with a center are wrong for both PHARM and PCC.

    I guess the same correction should be applied to the template Dosage Instructions Dosage Change.

    -

    Suggestion:

    Wait for IHE guidance on this, then constrain both rateQuantity and doseQuantity to the chosen structure.
    -

    Further explanation:

    -

  • Issue 4 "Fulfillment instructions missing content" with status "Closed". Last event (2021-02-11T15:46:07):
    <entryRelationship> "fulfillment instructions" is now  containing  the template  1.3.6.1.4.1.19376.1.5.3.1.4.3.1 .
  • Issue 5 "Fulfillment instructions missing content" with status "Closed". Last event (2021-02-18T11:25:04):
    <entryRelationship> "fulfillment notes" changed to  (DYNAMIC).
  • Issue 6 "repeatNumber should be mandatory" with status "Closed". Last event (2021-02-19T09:49:02):
    the element hl7:repeatNumber is set to 1…1
  • Issue 7 "Missing definition of 'Changed MTP Item'" with status "Closed". Last event (2021-02-18T15:50:24):
    substanceAdministration in 'Changed Medication Treatment Plan Item' is fixed.
  • Issue 8 "Suspicious definition of 'Changed PRE Items'" with status "Closed". Last event (2021-02-11T17:19:55):
    Inclusion changed from IHE Prescription Item Entry Content Module to  Prescription Item Entry Content Module.
  • Issue 9 "invalid SNOMET CT Code 1.01296E+15" with status "Closed". Last event (2021-02-10T14:33:51):
    Code of Lonoctocog alfa (substance) corrected.
  • Issue 10 "Values with white space" with status "Closed". Last event (2021-02-10T14:35:16):
    White spaces deleted.
  • Issue 11 "Suspicious cardinality for precondition criterion text" with status "Closed". Last event (2021-02-18T11:15:47):
    Cardinality of inner  reference  tag of  precondition/criterion/text  in  Medication Treatment Plan item entry content module fixed
  • Issue 12 "Incomplete description of repeatNumber" with status "Closed". Last event (2021-02-15T16:31:31):
  • Issue 13 "Wrong cardinality for the inner pharm:ingredient" with status "Closed". Last event (2021-02-19T00:39:12):
    The cardinality of the inner pharm:ingredient changed to 1…1
  • Issue 14 "Wrong typeCode for Patient Medication Instructions" with status "Open". Last event (2021-02-18T15:39:18):
    Element fixed with @typeCode="COMP".  @inversionInd="true" needs an unique ID Quentin will check with Stépahne.
  • Issue 15 "Invalid code system for Retinol" with status "Closed". Last event (2021-02-10T13:59:04):
    OID of Retinol corrected 
  • Issue 16 "Wrong cardinality for 'Changed Medication Treatment Plan Item'" with status "Closed". Last event (2021-02-18T23:37:26):
    Cardinality of  hl7:entryRelationship   " Changed Medication Treatment Plan Item"  set to  0…1
  • Issue 17 "Improve cardinalities of ingredient quantities" with status "Closed". Last event (2021-02-19T00:47:09):
    hl7:numerator: @value & @unit attribute added

    hl7:denominator: @value & @unit attribute added
  • Issue 18 "Element order may be wrong" with status "Open". Last event (2021-02-15T18:15:20):
    The IHE PCC specification (§6.3.4.16.2) specifies the following element order: routeCode, doseQuantity, approachSiteCode and rateQuantity.
    The IHE PRE profile (§6.3.4.6.3) has a different (presumably wrong) element order: routeCode, approachSiteCode, doseQuantity and rateQuantity.
    Stéphane will open the discussion at IHE PHARM and presumably propose a CP to change the approachSiteCode element position and match the PCC ordering.
    I'll update the issue if/when it's voted.
  • Issue 19 "Errors in UCUM codes" with status "Open". Last event (2021-02-17T21:53:49):
    All brackets that were present have disappear from the codes: tbs_m, 10*6.iU, PPM, CFU, iU, tsp_m

    I've been unable to find the code U{PIECE(S)} anywhere.

    The code umol has an error in its display name, it should be "micromole" (the final "e" is missing).

    The second should be s, not S (Siemens).
    The minute should be min, not MIN.
    The hour should be h, not HR.
    The day should be d, not D.
    Parts per million should be [ppm], not PPM.

    U is not unit but enzyme unit (that could be very confusing). 10*3.U and 10*6.U are also wrong.

    I've not found the code kJ in any other value set or in the search service but it seems to be valid, k and J being defined as prefix and unit.
  • Issue 20 "TimingEvent VS differs from EventTiming in CH EMED" with status "Open". Last event (2021-02-18T17:46:15):
    Finding:

    At the projectathon 2020, the following problem popped up: The value set for timing event (such as before meal. After meal etc.) is not the same in FHIR and CDA-CH-EMED. But both value sets are required (by FHIR and IHE PCC, respectively)

    Suggestion:

    - inquire on the international level to resolve this issue

    Further explanation:

    -

  • Issue 21 "Section code and attributes are required" with status "Closed". Last event (2021-02-19T00:58:31):
    section code set to required
  • Issue 22 "Section code and attributes are required" with status "Closed". Last event (2021-02-19T01:01:12):
    section code is set to required
  • Issue 23 "Section code attributes are required" with status "Closed". Last event (2021-02-19T01:06:33):
     section code attributes set required
Under pre-publication review
2020-05-08 13:51:46Oliver EggerRelease: 0.96 (8.5.2020)
0.96 (8.5.2020)
Retired
2018-05-03 17:01:25Oliver EggerRelease: 0.95.2 (30.04.2018)
labeled pre-publication review
Retired
2018-04-29 08:49:13Oliver EggerRelease: 0.95.1
adjusted samples
Cancelled
2018-04-26 20:35:56Oliver EggerRelease: 0.95.0
  • update to IHE Pharmacy Framework 2017
  • EDQM valusets
  • integration of feedback for hearing of ordonnance of appendix 4
Cancelled
2017-07-07 17:13:46Oliver EggerRelease: V0.91.4
adjusted samples and schematron rules
Cancelled
2017-07-05 10:47:31Oliver EggerRelease: V0.91.3
Fixes for schematron errors
Cancelled
2017-07-01 11:35:39Johannes GnaegiRelease: V0.91.2 - für Vernehmlassung
There have been no changes to issues since the last intermediate version or release.
Under pre-publication review
2017-07-01 11:28:04Johannes GnaegiRelease: V0.91.1 - für Vernehmlassung
There have been no changes to issues since the last intermediate version or release.
Cancelled
2017-06-29 22:25:38Oliver EggerRelease: V0.91
Modelling adjustments for June 2017 IPAG Report
Cancelled
2017-06-29 22:23:51Oliver EggerRelease: V0.01
Modelling adjustments for June 2017 IPAG Report
2017-06-29 14:00:58Oliver EggerRelease: V0.9
Initial Release after moving from CDA-CH-EMED to CH-PHARM
Cancelled
Busy
MyCommunity
Display NameNameDescription
BusyRetrieving…
Governance Groups
BusyRetrieving…
ART-DECOR Applications (ADA)
Application