Following are the contract level changes that we have fixed for our bundles to be parseable.
...
Composition
new mandatory fields added:
- type,
- author,
- confidentiality => http://hl7.org/fhir/v3/Confidentiality - code system
Encounter
subject => patient
(Fields removed )
indication
Condition
RelatedItem is replaced by dueTo and occurredFollowing.
status is replaced by "clinicalStatus"
dateAsserted date takes only date without tim component. -> Need to investigate how to map bahmni chief complaint duration after this change.
Changes in active development branch
Observation [breaking]
- name ==> code.
Immunization [breaking]
- refusalIndicator ==> wasNotGiven
- refusalReason ==> getReasonNotGiven
- subject ==> patient
MedicationPrescription [not breaking]
- dosageInstruction can now take both dosageQuantity and dosageRange
[dosageInstruction.dose field can capture two types dosageQuantity,dosageRange]
To look into later:
Composition:
Confidentiality set to String - A code from the confidentiality vs
...
DrugMapper - MedicationPrescription:
Mapping frequency component along with duration and period (Revisit mapping logic from bahmni treatment to fhir MedicationPrescription. esp duration and frequency)- Needs more analysis and test cases. Just fixed compilation issues.
DosageInstruction needs more analysis.
Procedure
Procedure.Outcome,Procedure.FollowUp
- is a codeableconcept from a valueset rather than plain text.We can improve the ui?
Procedure.DiagnosticReport.result
result is set as just display. Should be set as a reference to observation
Fields that can carry multiple value types
Ex: FamilyMemberHistory.born - Can take period, date,string. Currently we have handled date types.Should we handle all the types?
Need More Investigation:-
- Drug Order Mapper (upload and download flow)
- Chief Complaint Mapper (How to map Chief Complaint Duration?) -> Ignored the tests