Loading...
Help
Login
Busy
Search
Luxembourg CDA specifications - Project Information
 
Warning
Select building block repository
Select user
Select user

Add/change logo
Remove File
Compare: Releases


Edit
Edit publication parameters

Warning
Edit
Edit
Name
Luxembourg CDA specifications
Description
Specification of CDA documents in Luxembourg
PropertiesPrefix: lux-gh-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
https://art-decor.agence-esante.lu/publication/lux-gh/
Project overviewProject Index
Project Id1.3.182.7.3.2
Project Last modified2021-04-08 13:31:35
Repository reference
PrefixURLFormat
ad1bbr-http://art-decor.org/decor/services/DECOR
ad3bbr-http://art-decor.org/decor/services/DECOR
ad2bbr-http://art-decor.org/decor/services/DECOR
ccd1-http://art-decor.org/decor/services/DECOR
IHE-PCC-https://art-decor.ihe-europe.net/decor/services/DECOR
XDLAB-https://art-decor.ihe-europe.net/decor/services/DECOR
epsos-http://art-decor.org/decor/services/DECOR
RESTful Service
Contributors/Copyright
ContributorTypeLogoCopyright years
eSanté
Author2017
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
Heiko ZimmermannNot 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
SamuelNot 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
Geoffrey OlejniczakNot 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
Alexander HenketNot 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
HeikoNot 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
Ferring JensNot 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
Abderrazek BoufahjaNot 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
2019-07-02 09:19:04Administrator
There have been changes to the following 59 issues since the last intermediate version or release.
  • Issue 1 "Validation @use prüfen" with status "Open". Last event (2017-11-08T14:20:37):
    Befund:

    - In den Tests sollten wir prüfen ob die Regel das @use nicht mandatory ist wenn addr nullFlavor hat, funktioniert

    Vorschlag:

    - Tests der generierten Schematron

    Nähere Erläuterung:

    -

  • Issue 2 "Country code, three letters code from ISO-3166 alpha 3" with status "Closed". Last event (2018-01-03T15:54:01):
    Done
  • Issue 3 "Representation of Telecom" with status "Closed". Last event (2018-01-04T14:49:40):
    Fixed, separated representation of Telecom and added Schematron rule for usage of valueset
  • Issue 4 "Datatypes for prefix and suffix" with status "Open". Last event (2017-11-13T14:45:06):
    Finding:

    - The datatypes for prefix and suffix are in our Word specification EN.PREFIX and EN.SUFFIX here they need to be ENXP

    Suggestion:

    - Check compliance

    Further explanation:

    -

  • Issue 5 "Add eSanté_URLScheme" with status "Closed". Last event (2017-11-14T17:40:19):
    Finding:

    - Value - should start with value from value-set eSanté_URLScheme

    Suggestion:

    -

    Further explanation:

    -

  • Issue 6 "Country code need to be verified with ISO-3166 alpha3" with status "Rejected". Last event (2018-01-03T15:54:54):
    No more applicable as ADDR-2 has been cancelled
  • Issue 7 "Candidat for removal" with status "Closed". Last event (2018-01-03T13:44:18):
    ADDR-1 not used anymore, status cancelled
  • Issue 8 "Candidat for removal" with status "Closed". Last event (2018-01-03T13:44:43):
    ADDR-2 not used anymore, status cancelled
  • Issue 9 "II - datatype ID column -- strict --" with status "Open". Last event (2017-12-11T13:56:56):
    Finding:

    - The situation that the ID column with II datatype is checked strict, means the information about the same id must not be given twice, may cause problems with already existing documents created in DSP. 

    Suggestion:

    - Please verify with Abderrazek if this rule can be changed not to being so "strict" and allow double values

    Further explanation:

    -

  • Issue 10 "Template-Ids and header representation" with status "Closed". Last event (2018-01-04T14:51:04):
    Decision has been taken to separate the Headers per document, using correct set of TemplateIds
  • Issue 11 "Representation of OID" with status "Open". Last event (2017-12-27T09:18:53):
    Finding:

    - Constraints on id datataype related to OID and mandatoryness as mentioned within the written spec, seem to be fulfilled by oid type and "R" of root

    Suggestion:

    - No need for further check constraint, to be tested, nullFlavor test also

    Further explanation:

    -

  • Issue 12 "Check 1.3.182.10.10.1 eSante_DocType (DYNAMIC)" with status "Closed". Last event (2018-01-04T15:13:33):
    Verified with EBX Version and committed
  • Issue 13 "CE Datatype Displayname and Codesystemname" with status "Closed". Last event (2018-01-04T16:00:21):
    Decision has been taken to allow relaxation, so that displayname and codesystemname are not checked
    codeSystemIdentifier and code are relevant.
  • Issue 14 "Add condition on versionNumber " with status "Closed". Last event (2018-01-03T14:18:44):
    Done on CDA DSP and ePrescription
  • Issue 15 "Add Birthplace condition" with status "Closed". Last event (2018-01-03T14:37:02):
    Done
  • Issue 16 "Datatype for time" with status "Open". Last event (2017-12-27T13:29:04):
    Finding:

    - Check if the datatype for time can be changed to TS.DATETIMETZ.MIN in future, when datatype can be chosen from dropdown

    Suggestion:

    - Ask Abderrazek about the delivery of the new version

    Further explanation:

    -

  • Issue 17 "Assigned author id" with status "Closed". Last event (2018-01-03T15:07:32):
    Done by using the default II type from Art-Decor and deleting the attributes list.
    Also applied to:
    componentOf/encompassingEncounter/id
    informationRecipient/id
    organization/id
    recordTarget/patientRole/guardian/id
  • Issue 18 "Allowed nullFlavors for ID element" with status "Open". Last event (2017-12-27T13:56:47):
    Finding:

    - This may occur for other elements too. The restriction to the allowed nullFlavor within the list in Chapter 2.1 need to be taken into account

    Suggestion:

    - Should we add as constraint in Schematron rules or should we add value list for that?

    Further explanation:

    -

  • Issue 19 "Why assignedEntity with R" with status "Open". Last event (2017-12-27T14:15:17):
    Finding:

    - Both entities, the assignedEntity as well as the relatedEntity are marked as optional in the original specification. Why is assignedEntity here marked as required "R"

    Suggestion:

    -

    Further explanation:

    -

  • Issue 20 "nullFlavor value limitations" with status "Open". Last event (2017-12-27T14:30:35):
    Finding:

    - Check for limited value set of nullFlavor 's allowed for elements

    Suggestion:

    -

    Further explanation:

    -

  • Issue 21 "Recheck after tests of V 1.0" with status "Open". Last event (2017-12-27T14:44:44):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 22 "Check with tests if multiple id element really needed" with status "Open". Last event (2017-12-27T15:22:40):
    Finding:

    - The multiple ID elements in patient are used to present three different types of identifiers in sequence. The Schematron rule is checking about the used / to use root id. 

    Suggestion:

    - I guess it is not needed to have 3 times the id element or at least change the cardinality of each one to 1..1

    Further explanation:

    -

  • Issue 23 "Test sequence of id" with status "Open". Last event (2017-12-27T15:29:35):
    Finding:

    - Test if the sequence of id is correct encoded with the max. of three elements

    Suggestion:

    - Should be ok, if so check representation of recordTarget/patient/id

    Further explanation:

    -

  • Issue 24 "Why 2.16.840.1.113883.5.4 as Codesystem for Code attribute??" with status "Closed". Last event (2018-01-03T15:10:41):
    This has been deleted
  • Issue 25 "Check Attribute typeCode" with status "Closed". Last event (2018-01-03T16:17:04):
    We only accept RPLC so far, so a constant is now set
  • Issue 26 "Should we really keep 2.16.840.1.113883.5.4" with status "Closed". Last event (2018-01-03T16:06:20):
    Changed to use 1.3.182.10.31.1
  • Issue 27 "Check if the contains elements are ok" with status "Open". Last event (2017-12-27T16:05:03):
    Finding:

    - Check if the contains elements are ok or if they should be exchanged to includes

    Suggestion:

    -

    Further explanation:

    -

  • Issue 28 "Schematron rule to add" with status "Closed". Last event (2018-01-03T15:48:32):
    Done based on what was present in the original Schematron file
  • Issue 29 "Modification on postalCode, city, country" with status "Open". Last event (2017-12-29T14:05:41):
    Finding:

    - While testing having cardinality 1..1 on postalcode, city and country, nullFlavor for addr was not possible. Changed cardinality to 0..1 for those three elements
      Check with former specification (Word - document)

    Suggestion:

    -

    Further explanation:

    -

  • Issue 30 "ValueSet for Country-Codes" with status "Closed". Last event (2018-01-03T13:43:03):
    Done !
  • Issue 31 "Problem using TEL datatype" with status "Open". Last event (2018-01-31T13:21:00):
    Finding:

    - We have old documents which are not valid if they are validated against these new rules, due to the fact that URI is not ensured as value.
    Some source-systems do provide data with "space".

    Suggestion:

    -

    Further explanation:

    -

  • Issue 32 "ContextControlCode fixed value" with status "Open". Last event (2018-02-01T10:54:01):
    Finding:

    - In our former CDA specifications we haven't used @contextControlCode as mandatory 1..1, so for purpose of backward compatibility we changed to 0..1 here.

    Suggestion:

    - In new Version of CDA - Header Template restrict to 1..1

    Further explanation:

    -

  • Issue 33 "Define ValueSet for RouteCodes" with status "Open". Last event (2018-02-26T16:12:55):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 34 "Define ValueSet for approachSiteCode" with status "Open". Last event (2018-02-26T16:25:56):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 35 "Define ValueSet for immunization" with status "Open". Last event (2018-02-27T13:32:23):
    Finding:

    - define value - set for vaccinations based on SNOMED-CT under consumable/manufacturedProduct/manufacturedMaterial/code

    Suggestion:

    -

    Further explanation:

    -

  • Issue 36 "ValueSet definition for code element needed" with status "Open". Last event (2018-05-08T14:15:48):
    Finding:

    - Different types of event types for the Allergy should come from ValueSet

    Suggestion:

    - Take SNOMED-CT codes as in AdverseEventType

    Further explanation:

    -

  • Issue 37 "value Element cardinality" with status "Open". Last event (2018-05-08T15:27:00):
    Finding:

    - In eHDSI specifications we see cardinality as 0..*, whereas we change to 1..1 as it seems more reasonable for us

    Suggestion:

    - We keep 1..1 and will see Feedback from eHDSI PS specification https://ec.europa.eu/cefdigital/tracker/browse/EHOPERATIONS-378

    Further explanation:

    -

  • Issue 38 "Create valueSet for value Element" with status "Open". Last event (2018-05-08T15:33:38):
    Finding:

    - For the Lux representation, create a value set which contains the list of allergies/problems, if possible

    Suggestion:

    -

    Further explanation:

    -

  • Issue 39 "Add Schematron rule on participant" with status "Open". Last event (2018-05-08T16:19:08):
    Finding:

    - For enabling the constraint

    Suggestion:

    - Add Schematron assert

    Further explanation:

    -

  • Issue 40 "Test Schematron for statusCode" with status "Open". Last event (2018-06-05T11:48:42):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 41 "Add ValueSet for code element" with status "Closed". Last event (2018-08-14T10:29:43):
    used 1.3.6.1.4.1.12559.11.10.1.3.1.42.23 epSOSCodeProb (DYNAMIC)
  • Issue 42 "Add ValueSet for value element" with status "Closed". Last event (2018-08-16T12:08:44):
    used:
    The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.11 epSOSReactionAllergy (DYNAMIC)
    or
    The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.17 epSOSUnknownInformation (DYNAMIC)
    or
    The value of @code shall be drawn from value set 1.3.6.1.4.1.12559.11.10.1.3.1.42.5 epSOSIllnessesandDisorders (DYNAMIC)
  • Issue 43 "Add a valueSet for the Allergen" with status "Open". Last event (2018-06-13T09:08:27):
    Finding:

    - playingEntity/code

    Suggestion:

    -

    Further explanation:

    -

  • Issue 44 "Problem entry relationship" with status "Open". Last event (2018-06-13T11:55:41):
    Finding:

    -Note: the 1.3.6.1.4.1.19376.1.5.3.1.4.5 requires that also the template ID '2.16.840.1.113883.10.20.1.28' is included.


    Suggestion:

    - Should also be  2.16.840.1.113883.10.20.1.54 additionally to signalize that this is an allergic reaction

    Problem entry element now contains as well the templateId 2.16.840.1.113883.10.20.1.54 optionally, means it would possibly make sense to add a Schematron rule here to ensure that in such cases the templateId within the problem entry shall be set.


    Further explanation:

    - In Problem entry now there is a constraint on the second templateId, maybe it is needed to add an additional check constraint on the entryRelationship to verify that the right templateId is used below.

  • Issue 45 "Problem Entry 2nd Template Id" with status "Open". Last event (2018-06-14T14:53:57):
    Finding:

    - Template should signalize in case of an allergic reaction as a problem

    Suggestion:

    - Add in that case the templateId @root="2.16.840.1.113883.10.20.1.54"

    Template must either signalize a allergic reaction or problem
    This may need to be checked within a Schematron rule/Constraint on the level of the Allergies and Intolerances Entry

    Further explanation:

    -

  • Issue 46 "ValueSet needed for ProblemStatusObservation_value" with status "Closed". Last event (2018-08-14T09:33:59):
    used 1.3.6.1.4.1.12559.11.10.1.3.1.42.15 epSOSStatusCode (DYNAMIC)
  • Issue 47 "ValueSet to be defined" with status "Closed". Last event (2018-08-14T09:31:08):
    Used: 1.3.6.1.4.1.12559.11.10.1.3.1.42.30 epSOSResolutionOutcome (DYNAMIC)
  • Issue 48 "Check to add ID constraint" with status "Open". Last event (2018-12-18T12:11:16):
    Finding:

    - Take into account if we should add schematron rule for restriction of values for id, as they are described in the description part of this.

    Suggestion:

    -

    Further explanation:

    -

  • Issue 49 "Should we add constraint/rule on id ?" with status "Open". Last event (2018-12-18T14:50:42):
    Finding:

    -

    Suggestion:

    -

    Further explanation:

    -

  • Issue 50 "Clarification with GT Médicale needed" with status "Open". Last event (2019-01-09T13:50:49):
    Finding:

    - Clarify the statusCode if we only accept "Active" and clarify about the effectiveTime to reduce to low value for "active" state. 

    Suggestion:

    - Not visualizing in the PS if there is an Allergy concern in the state of "completed"

    Further explanation:

    -

  • Issue 51 "Value Sets assignment" with status "Open". Last event (2019-01-09T14:17:24):
    Finding:

    -

    Suggestion:

    - Assign Valueset for Participant/code
    - Create own ValueSet for the others which currently refer to eHDSI ones

    Further explanation:

    -

  • Issue 52 "Usage of effectiveTime high" with status "Open". Last event (2019-01-10T15:28:46):
    Finding:

    - We need to be clear what listing within this, as the statusCode is foreseen as being in status "completed", means the observation state. We need to be clear with the effectiveTime "High" if it should be present, as by this definition it means that it indicates the time at which the observation was no longer known to be true => so the resolution of the problem. Is it then really relevant to put it into the Résumé Patient?

    Suggestion:

    -

    Further explanation:

    -

  • Issue 53 "Participant" with status "Open". Last event (2019-01-10T15:54:21):
    Finding:

    - Probably exchange by Author structure and review if we shouldn't add more fields like e.g. the functionCode or other id

    Suggestion:

    -

    Further explanation:

    -

  • Issue 54 "Procedure unique identifier" with status "Open". Last event (2019-01-10T16:07:22):
    Finding:

    - Shouldn't we add a unique identifier for the procedure, generated by the source system 

    Suggestion:

    -

    Further explanation:

    -

  • Issue 55 "statusCode values" with status "Open". Last event (2019-01-10T16:12:03):
    Finding:

    - Is it really only relevant to have "complete"? What about ongoing procedures in status "active" they may also be interesting for the Patient Summary

    Suggestion:

    -

    Further explanation:

    -

  • Issue 56 "routeCode codesystem" with status "Open". Last event (2019-03-12T16:30:02):
    Finding:

    -

    Suggestion:

    - Codesystem need to reflect the "No information" or we allow nullFlavor

    Further explanation:

    -

  • Issue 57 "siteCode" with status "Open". Last event (2019-03-12T16:33:08):
    Finding:

    -

    Suggestion:

    - check mandatory or if we add nullFlavor, proposal was to have optional

    Further explanation:

    -

  • Issue 58 "expirationDate" with status "Open". Last event (2019-03-12T16:39:40):
    Finding:

    - Check the format

    Suggestion:

    -

    Further explanation:

    -

  • Issue 59 "Add constraint" with status "Open". Last event (2019-06-28T15:01:38):
    Finding:

    - a Constraint need to be added

    Suggestion:

    - In case the negationInd = "true", the field reasonNotGiven shall be given and comment can be given

    Further explanation:

    -

2015-08-27 01:30:00Alexander Henket
  • Added missing namespace prefix on name part elements in template id="1.3.182.11.3" name="CDArecordTarget" effectiveDate="2014-10-08T16:45:14"
  • Added missing namespace prefix on name part elements in template id="1.3.182.11.4" name="CDAPerson" effectiveDate="2014-10-09T09:48:04"
  • Added missing namespace prefix on name part elements in template id="1.3.182.11.10" name="CDAcustodian" effectiveDate="2014-10-09T10:08:39" - note that organization names will never have a given/family name part
  • Added missing namespace prefix on name part elements in template id="1.3.182.11.20" name="CDAOrganization" effectiveDate="2014-10-09T14:29:56" - note that organization names will never have a given/family name part. Also fixed circular reference in same template from inclusion to containment.
  • Removed extra call in template id="1.3.182.11.19" name="CDAcomponentOf" effectiveDate="2014-10-09T10:35:42", to the ADDR template inside element serviceOrganization. This ADDR doesn't belong there but is already contained in the CDAorganization template that is contained.
Busy

MyCommunity
Display NameNameDescription
BusyRetrieving…
Governance Groups
BusyRetrieving…
ART-DECOR Applications (ADA)
Application