Changes in current release version
- Entry level updated,author tags are moved to bundle level meta data. Entry doesnot have an id.Every resource is now mandated to have an id.
- Currently we are populating the resource id to the entry id.
- type ->> NEED TO CREATE A VALUESET IN TR FOR THIS. (name is 'doc-typecodes' with document types from loinc).
- author,
- confidentiality => http://hl7.org/fhir/v3/Confidentiality - code system
Bundle
- Bundle has to have a type -> Document. Validate this?
- base tag is mandated at either bundle level or at individual entry level.
All bundle entry ids must be a uuid,
in DSTU1 we had urn:<uuid>, this should be changed to have only <uuid>
example:DSTU1 DSTU2 <entry id="urn:5f982a33-4454-4b74-9236-b8157aa8effd"> <entry id="5f982a33-4454-4b74-9236-b8157aa8effd"> All reference urls should be either urls starting with http protocol or must be uuid prefixed with 'urn:uuid:'.
- name ==> code.
- refusalIndicator ==> wasNotGiven
- refusalReason ==> getReasonNotGiven
- subject ==> patient
- dosageInstruction can now take both dosageQuantity and dosageRange
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
- MCIPatientServiceImplIT - should save drug orders.
0 Comments