I am developing a ionic app and have to use HL7 v3.
I tried searching for it, but couldn't found anything much on the technical side. so, my question is:
What is Hl7 V3?
How it can be implemented?
Are there any library for creating and parsing HL7 V3 messages available?
Cheers!
V3 is most likely referring to HL7 Version 3. Version 2.5.1 is currently the most widely implemented version, but more and more systems and organizations are upgrading to V3. Implementing is the same process. You can find various HL7 version documentation here: http://www.hl7.org/implement/standards/product_section.cfm?section=1&ref=nav
Related
does anyone know the state of the Paypal .NET SDK? I just wonder, according to https://github.com/paypal/PayPal-NET-SDK/releases, the latest version is a V2.0 Release Candidate, but it is already 2 years old, and it seems like there was never an actual V2.0 release. Has this project died? Should I rather use the Paypal REST API directly?
Don't use any version of the v1 PayPal-NET-SDK (neither 1.x nor 2.0 rc2)
Use the new v2 Checkout-NET-SDK
If it does not (yet) support the API you want to integrate (e.g. the new Subscriptions API would be one example), then use direct HTTPS calls for that REST API
I'm trying to use the Swagger UI, and it says that I should begin by writing an api-doc that describes the exact api for a REST api. The problem is that I have no idea what this means. Is this document written in plain English? Or is there a certain format that will be able to generate the UI?
Thank you!
Swagger is a specification for describing REST APIs. Documentation of the specification can be found here - https://github.com/swagger-api/swagger-spec.
Generally, there are two ways to document your API. If you already have an existing API with code, you can use any of the existing libraries (https://github.com/swagger-api/swagger-spec#additional-libraries) to integrate into your code and generate documentation at run time. Some of those libraries also offer offline generation of such docs.
If you're looking to design an API, or would rather not integrate another library into your application, you can use https://github.com/swagger-api/swagger-editor either locally or with the online version - http://editor.swagger.io.
Once you have the documentation, you can use Swagger UI to visualize and test it.
I am working on a project and I need to use this tow api; jtapi, gjtapi. The problem is
both gjtapi and jtapi project seem dead. Is there a new similar java api?
JTapi is a specification that is implemented by vendors, as CISCO or AVAYA. In my experience, there is no an generic API for JTapi, because each provider customizes their own implementation according at their telephony platform.
If you want a "generic" JTapi you should review this link, that refer to an Asterisk JTapi:
http://asterisk-jtapi.sourceforge.net/
I have been trying to find the answer to this but it doesn't seem to be anywhere. Does anyone know if Moodle is PENS compliant?
As far as I can tell, Moodle is not Package Exchange Notification Services (PENS) compliant.
The specification does not appear to be too hairy, but i have not found any indication that anyone has tried to implement it for Moodle.
Some alternatives you could consider:
A 3rd party content, such as SCORM Cloud (commercial service)
Learning Tools Interoperability (LTI), which is a set of protocols which appear to be similar to PENS, i.e. you designate your LMS as a provider or consumer, and content can be shared. Moodle has consumer support built in. Acting as a provider can be achieved using a plugin.
I am trying to send an ActiveMQ StreamMessage from a C++ (CMS) client to a Java (JMS) client. However, the Java client is unable to correctly read the values from the incoming message - most fields are extracted as null, and the fields that do have values associated with them just seem to contain garbage.
I can send BytesMessages and TextMessages from our C++ client to our Java client just fine, so the BytesMessage is our fallback for now.
However, the misbehaving StreamMessage is making us suspect something is wrong/incompatible between our two clients.
We are using ActiveMQ 5.4.2 on the Java side, and activemq-cpp 3.0.1 on the C++ side.
Are there any known incompatibilities between the JMS and CMS implementations, or are there any other obvious pitfalls I should look for?
I think there were some issues that I fixed somewhere between 3.0.1 and the latest 3.2.4 that fixed some issues with stream message. I'd really recommend that you update to v3.2.4 of CMS as there's been a large number of bugs fixed, along with some great new features.
The CMS issue tracker is here if you want to review to issues fixed since the version you are using:
Edit: Found the issue that fixed it, its here.
-Tim
www.fusesource.com