Ch emed epr/emediplan #187
Conversation
…h copying changed medication statements between different subtypes of observations (e.g. when copying a PADV observation to a PML).
|
@qligier IIRC you also use |
Indeed, I'll check that. Thanks!
It is already released: https://emediplan.ch/vorstand-genehmigt-chmed23a/ |
The JSON specification is out, the paper/print layout specification - which they decided to publish separately for ChMed23A - is not out yet. We'll have to wait a tad bit more. |
...ative/src/main/java/org/projecthusky/fhir/emed/ch/epr/narrative/pdf/HtmlToPdfAConverter.java
Show resolved
Hide resolved
| "nmol", | ||
| "nmol", | ||
| "nmol", | ||
| "nmol"), |
There was a problem hiding this comment.
Sorry, I failed to update this enum while updating the value sets. From c029d01#diff-41404c6413bed2afac45c3d235788fb6917739dac0a8b5051cf9f106c92134a5, it seems we are also missing APPLICATION_UNIT_OF_PRODUCT_USAGE_QUALIFIER_VALUE (413568008) here.
There was a problem hiding this comment.
In fact those are too new for the currently published version of the CH EMED EPR value set... I will remove NMOL from this PR and from the CdTyp9 conversion and will have to be added back with the next version of CH EMED EPR based on CH EMED 5.0.0. The enum units affected will be:
...med-ch-epr/src/main/java/org/projecthusky/fhir/emed/ch/epr/model/emediplan/enums/CdTyp9.java
Show resolved
Hide resolved
.../main/java/org/projecthusky/fhir/emed/ch/epr/model/emediplan/posology/EMediplanPosology.java
Outdated
Show resolved
Hide resolved
.../main/java/org/projecthusky/fhir/emed/ch/epr/model/emediplan/posology/EMediplanPosology.java
Outdated
Show resolved
Hide resolved
...ecthusky/fhir/emed/ch/epr/model/emediplan/posology/detail/application/ApplicationAtTime.java
Outdated
Show resolved
Hide resolved
…gy#start and EMediplanPosology#end json format pattern.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| private static final Pattern LANGUAGE_CODE_PATTERN = Pattern.compile("[a-zA-Z]{2}" ); | ||
| private static final Pattern PHONE_NUMBER_PATTERN = Pattern.compile("\\+?[0-9]+[ 0-9]*"); | ||
| private static final Pattern EMAIL_PATTERN = | ||
| Pattern.compile("^(?=.{1,64}@)[\\\\p{L}0-9_-]+(\\\\.[\\\\p{L}0-9_-]+)*@[^-][\\\\p{L}0-9-]+(\\\\.[\\\\p{L}0-9-]+)*(\\\\.[\\\\p{L}]{2,})$"); |
Check failure
Code scanning / CodeQL
Inefficient regular expression High
| private static final Pattern LANGUAGE_CODE_PATTERN = Pattern.compile("[a-zA-Z]{2}" ); | ||
| private static final Pattern PHONE_NUMBER_PATTERN = Pattern.compile("\\+?[0-9]+[ 0-9]*"); | ||
| private static final Pattern EMAIL_PATTERN = | ||
| Pattern.compile("^(?=.{1,64}@)[\\\\p{L}0-9_-]+(\\\\.[\\\\p{L}0-9_-]+)*@[^-][\\\\p{L}0-9-]+(\\\\.[\\\\p{L}0-9-]+)*(\\\\.[\\\\p{L}]{2,})$"); |
Check failure
Code scanning / CodeQL
Inefficient regular expression High
…nd implementors about expected context variables
…der#usePdfUaAccessbility, deprecated, with the typo-free usePdfUaAccessibility
…p9#fromRegularUnitCodeAmbu since not yet in current published version fo the CH EMED EPR value set. Will be added back with the next version of CH EMED EPR.
This PR addresses the changes needed to implement the new feature requested with #181 .
This work includes:
What has not been done/tested and is left for future development:
emediplan_medications_table.htmlinhusky-fhir-emed-ch-epr-narrativehas a few TODO comments. These will be addressed once the ChMed23A paper specification is released (AFAIK this is a current WIP and should be released before the end of this year) and a review of the layout in husky is performed to ensure it is compliant.