j4jayant.com Report : Visit Site

Technical data of the j4jayant.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host j4jayant.com. Currently, hosted in United States and its service provider is Google Inc. .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called GSE containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

home about thursday, 30 august 2018 sample immunization records blockchain using hyperledger composer this is basic and sample blockchain implementation of immunization records using hyperledger composer. source code available at: https://github.com/j4jayant/hyperledger-composer-samples/tree/master/immunization-network read more » email this blogthis! share to twitter share to facebook share to pinterest monday, 23 april 2018 blockchain - healthcare implementation use case - part 1 it's been a long time i am following blockchain and my interest continued to increase and increased enough to dive into it. this article is not intended to be a blockchain introduction. there are many good articles available on it. this is first in a series of articles and my focus would be to make healthcare developers understand it independently of cryptocurrency and relate it with healthcare use cases. read more » email this blogthis! share to twitter share to facebook share to pinterest monday, 17 august 2015 mirth fhir technology preview 1 with mongodb mirth has recently released a fhir listener as part of first version of it's fhir technology previw. this lead me to explore fhir after around 2 years. this listener is available to download on mirth site and can be installed like any mirth extension. fhir listener comes with very good tutorial & a example channel . example channel provided with fhit technology preview 1 stores fhir resources in postgresql. i have modified the sample channel to parse & store fhir resources in mongodb. this is simple fhir server with create, update, delete, read & vread in simplest forms. this modified channel can be downloaded from my github . please use mirth 3.2.2. thanks to a discussion on mirth forum between community users vpnath & narupley. few observations about mirth's fhir technology preview 1 supports dstu 1 only. dstu 1 is official dstu but most public fhir servers support dstu 2 and hope to see it in next preview. based on hapi fhir creates a simple fhir server with minimum effort. has few bugs though (these are discussed on forum) generates conformance with no effort. it's based on mirth's existing http listener. fhir server developed on this will perform slow in serving concurrent requests. email this blogthis! share to twitter share to facebook share to pinterest sunday, 22 march 2015 c-cda to json to mongodb using mdht & mirth recently i stumbled across a very good tutorial on how to parse ccds in mirth using mdht (model driven health tools). this tutorial will help you setting up the mirth to use mdht lib. http://www.spheregen.com/parsing-continuity-of-care-ccd-using-mirth-and-mdht/ it was such an easy to implement the tutorial that it inspired me to do a poc with mdht & mirth and i thought of converting consolidated cda documents to json. then i searched if this is already implemented and found two very useful open source libraries. https://github.com/jmandel/json_ccda http://www.bluebuttonjs.com/docs/ i tried bluebutton.js first and it was really easy to implement with javascript in browser that i just copied the json format from it. after successfully converting c-cda to json using mdht in mirth, i then thought of going a step ahead and storing this json in mongodb with same mirth channel and see how mongo queries can be used to do analytics from document repository created out of it. here is how the high level architecture of this poc looks like mirth channel details this mirth channel is configured to listen as a file reader for incoming c-cda xmls once xml is received, channel creates cda document using mdht toolkit )tutorial link shared at beginning of this article) source transformer converts each section to json and stores it in channelmap channel destination is configured as javascript writer destination has a custom code to write the json to mongodb json data stored in mongodb can be used for analytics with mongo queries patient/document matching (duplicate check) is not handled in this poc pre-requisite for using mongodb in mirth is to copy java driver jar file in mirth's custom-lib folder. mirth connect transformer step to convert allergy section xml to json using mdht var document = {} // parse ccda header - header parsing code removed from sample code //allergies section - only allergy section parsing is included in sample code var allergiessection = doc.getallergiessection(); if(allergiessection!= null && ! allergiessection.getallergyproblemacts().isempty() ) { var allergydata = []; var sizeallergyproblemacts = allergiessection.getallergyproblemacts().size(); for(i=0; i < sizeallergyproblemacts; i++) { var allergyjson = {}; var alrgprobact = allergiessection.getallergyproblemacts().get(i); allergyjson.effectivetime = parsedate(alrgprobact.geteffectivetime()); if(! alrgprobact.getentryrelationships().isempty() ) { var sizealrgentryrelationships = alrgprobact.getentryrelationships().size(); for(j=0; j < sizealrgentryrelationships; j++) { var obs = alrgprobact.getentryrelationships().get(j).getobservation(); var templateid = obs.gettemplateids().get(j).getroot(); if(templateid == "2.16.840.1.113883.10.20.22.4.7") { allergyjson.code = new string( obs.getcode().getcode() ); allergyjson.code = new string( obs.getcode().getdisplayname() ); allergyjson.code = new string( obs.getcode().getcodesystem() ); allergyjson.code = new string( obs.getcode().getcodesystemname() ); if(! obs.getvalues().isempty() && obs.getvalues().get(0) instanceof org.openhealthtools.mdht.uml.hl7.datatypes.cd) { var cd = org.openhealthtools.mdht.uml.hl7.datatypes.cd ( obs.getvalues().get(0) ); allergyjson.reaction_type_name = new string( cd.getdisplayname() ); allergyjson.reaction_type_code = new string( cd.getcode() ); allergyjson.reaction_type_code_system = new string( cd.getcodesystem() ); allergyjson.reaction_type_code_system_name = new string( cd.getcodesystemname() ); } } if(! obs.getentryrelationships().isempty() ) { sizealrgobsentryrel = obs.getentryrelationships().size(); for(k=0; k < sizealrgobsentryrel; k++) { var obsentryrelobs = obs.getentryrelationships().get(k).getobservation(); var obsentryrelobstemplateid = obsentryrelobs.gettemplateids().get(0).getroot(); if(obsentryrelobstemplateid == "2.16.840.1.113883.10.20.22.4.28") { if(! obsentryrelobs.getvalues().isempty() && obsentryrelobs.getvalues().get(0) instanceof org.openhealthtools.mdht.uml.hl7.datatypes.cd) { var cd = org.openhealthtools.mdht.uml.hl7.datatypes.cd ( obsentryrelobs.getvalues().get(0) ); allergyjson.status = new string( cd.getdisplayname() ); } } else if(obsentryrelobstemplateid == "2.16.840.1.113883.10.20.22.4.9") { if(! obsentryrelobs.getvalues().isempty() && obsentryrelobs.getvalues().get(0) instanceof org.openhealthtools.mdht.uml.hl7.datatypes.cd) { var cd = org.openhealthtools.mdht.uml.hl7.datatypes.cd ( obsentryrelobs.getvalues().get(0) ); allergyjson.reaction_name = new string( cd.getdisplayname() ); allergyjson.reaction_code = new string( cd.getcode() ); allergyjson.reaction_code_system = new string( cd.getcodesystem() ); } } else if(obsentryrelobstemplateid == "2.16.840.1.113883.10.20.22.4.8") { if(! obsentryrelobs.getvalues().isempty() && obsentryrelobs.getvalues().get(0) instanceof org.openhealthtools.mdht.uml.hl7.datatypes.cd) { var cd = org.openhealthtools.mdht.uml.hl7.datatypes.cd ( obsentryrelobs.getvalues().get(0) ); allergyjson.severity = new string( cd.getdisplayname() ); } } } } if(! obs.getparticipants().isempty() ) { allergyjson.allergen_name = new string( obs.getparticipants().get(0).getparticipantrole().getplayingentity().getcode().getdisplayname() ); allergyjson.allergen_code = new string( obs.getparticipants().get(0).getparticipantrole().getplayingentity().getcode().getcode() ); allergyjson.allergen_code_system = new string( obs.getparticipants().get(0).getparticipantrole().getplayingentity().getcode().getcodesystem() ); allergyjson.allergen_code_system_name =

URL analysis for j4jayant.com

http://www.j4jayant.com/2013/
http://www.j4jayant.com/2015/08/
http://www.j4jayant.com/2013/01/
http://www.j4jayant.com/2018/08/sample-immunization-records-blockchain.html
http://www.j4jayant.com/2013/07/
http://www.j4jayant.com/2013/02/pid-segment-patient-identifiers.html
http://www.j4jayant.com/2013/02/hl7-identifiers-person-patient-account.html
http://www.j4jayant.com/2015/
http://www.j4jayant.com/p/about.html
http://www.j4jayant.com/2013/03/
http://www.j4jayant.com/2018/04/blockchain-healthcare-implementation.html#more
http://www.j4jayant.com/2015/03/
http://www.j4jayant.com/2018/04/blockchain-healthcare-implementation.html
http://www.j4jayant.com/2015/08/mirth-fhir-technology-preview-1-with.html
http://www.j4jayant.com/2018/08/

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: J4JAYANT.COM
Registry Domain ID: 1769181327_DOMAIN_COM-VRSN
Registrar WHOIS Server: Whois.bigrock.com
Registrar URL: http://www.bigrock.com
Updated Date: 2017-11-27T03:08:16Z
Creation Date: 2012-12-27T14:16:11Z
Registry Expiry Date: 2018-12-27T14:16:11Z
Registrar: BigRock Solutions Limited
Registrar IANA ID: 1495
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.2013775952
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: DNS1.BIGROCK.IN
Name Server: DNS2.BIGROCK.IN
Name Server: DNS3.BIGROCK.IN
Name Server: DNS4.BIGROCK.IN
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2018-09-16T15:21:59Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.

  REGISTRAR BigRock Solutions Limited

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =j4jayant.com

  PORT 43

  TYPE domain

DOMAIN

  NAME j4jayant.com

  CHANGED 2017-11-27

  CREATED 2012-12-27

STATUS
clientTransferProhibited https://icann.org/epp#clientTransferProhibited

NSERVER

  DNS1.BIGROCK.IN 162.251.82.123

  DNS2.BIGROCK.IN 162.251.82.120

  DNS3.BIGROCK.IN 162.251.82.247

  DNS4.BIGROCK.IN 162.251.82.124

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .