Comments (8)
the medication card example needs to add the dosagetype
from cda-fhir-maps.
actually the card.json was not conformant to the 'http://fhir.ch/ig/ch-emed/StructureDefinition/ch-emed-dosage-structured', that's why the normal dosing was not added.
from cda-fhir-maps.
and marcoumar has no dosage, so "normal dosage" template does not apply
from cda-fhir-maps.
How do we represent non-structured dosing in CDA?
- 6.3.4.6 Dosage Instructions Content Module (1.3.6.1.4.1.19376.1.9.1.3.6) (page 44)
- Dosage Instructions may be provided structured and/or narrative.
- If dosage instructions are provided narrative only, the Dosage Instructions data elements SHALL NOT be present as a whole.
- 6.3.4.6.3.3 Dosage Instructions Additional Template ID (page 46)
- In case (structured) dosage instructions are not provided (e.g., because they are only provided as narrative text), this element SHALL be set to “Normal Dosing”.
- So wie ich es verstehe, sollten wir die unstrukturierte Dosierung mit der templateId für Normal Dosing ergänzen.
- Und der Text der unstrukturierten Dosierung müsste templateId=2.16.756.5.30.1.1.10.4.52 anstelle templateId=2.16.756.5.30.1.1.10.4.37 sein oder? (Dosage Instructions Non Structured Entry Content Module)
<entryRelationship typeCode="COMP">
<substanceAdministration classCode="SBADM" moodCode="INT">
<!--<templateId root="2.16.756.5.30.1.1.10.4.37"/>-->
<templateId root="2.16.756.5.30.1.1.10.4.52"/>
<text>Take one every two weeks (unstructured dosage)
<reference value="#refpdf"/>
</text>
<consumable>
<manufacturedProduct>
<manufacturedMaterial nullFlavor="NA"/>
</manufacturedProduct>
</consumable>
</substanceAdministration>
</entryRelationship>
from cda-fhir-maps.
- verify the behavior with quentin for normal dosing
- we have to check with quentin for what 2.16.756.5.30.1.1.10.4.52 / 2.16.756.5.30.1.1.10.4.37 are used and if we should switch to 2.16.756.5.30.1.1.10.4.52 (and if the other is used?)
from cda-fhir-maps.
@qligier i forgot to mention this for the call today, could you have a quick look? for normal dosing if only unstructured and which templateId to use?
from cda-fhir-maps.
So wie ich es verstehe, sollten wir die unstrukturierte Dosierung mit der templateId für Normal Dosing ergänzen.
That seems right.
For the templateIds, they're not defined by IHE so there's not much description to read about. As I understand it, 2.16.756.5.30.1.1.10.4.52
is for completely unstructured dosage and 2.16.756.5.30.1.1.10.4.37
is a reference to the dosage intake mode (so the narrative description of routeCode
and approachSiteCode
I guess). We only used the former in structured dosage, but I can't guarantee it's right.
So I'd go with 2.16.756.5.30.1.1.10.4.52
in this case. I've opened a ticket to improve description of these templates.
Edit: we only used the former (.52), not the latter.
from cda-fhir-maps.
drop 2.16.756.5.30.1.1.10.4.37
from cda-fhir-maps.
Related Issues (20)
- Mapping MedStat/MedReq.note vs. Dosage.text (unstructured)
- CH-EMED-PMP mapping additions
- CH-EMED-PMP: Referenz auf Narrative
- CH-EMED-PMP: invalid text.reference in AnnotationComment HOT 1
- pharm:asContent only when amount and code
- CH-EMED-PMP: Mapping if author = device
- CH-EMED-PMP: Unstructured dosage - start and end date on dosage
- CH-EMED-PMP: medication in reserve
- Improve mapping for MedicationStatement.note HOT 1
- Mapping document author if device to wrong resource type HOT 1
- Missing author on entry level HOT 1
- Missing mapping for different authors (on different levels) HOT 1
- Adjust mapping for PADV documents
- add mapping (cda->fhir) for externalDocumentId and id in the Medication List elements
- templateId missing fhir -> cda
- Practitioner.address/name are not mapped (CDA -> FHIR) HOT 1
- mapping ext (ch-emed-ext-dispense) HOT 2
- list CDA -> FHIR: Composition section missing HOT 3
- empty narrative HOT 5
- Map files need to be updated to align with latest cda logical model 2.0.0-sd-snapshot1 HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cda-fhir-maps.